Fmeca vs Voidmob MCP
A side-by-side look at the Fmeca and Voidmob MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
F
FmecaCommunication · Local subprocess (stdio)Deterministic, offline FMECA MCP server: failure modes, criticality matrix, mitigations, readiness56GoodAuth: no auth requiredVerdict: choose Fmeca for communication work as a local process; choose Voidmob MCP for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
FChoose Fmeca when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
session.open, append, state.get.
Choose Voidmob MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
VOIDMOB_API_KEY, VOIDMOB_READ_ONLY, VOIDMOB_MAX_ORDER_CENTS, VOIDMOB_BUDGET_CENTS. - You want tools like
get_account, search_sms_services, rent_number.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | F Fmeca | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 56/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | VOIDMOB_API_KEYVOIDMOB_READ_ONLYVOIDMOB_MAX_ORDER_CENTSVOIDMOB_BUDGET_CENTS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 27 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 12 | 30 |
| Full listing | View Fmeca | View Voidmob MCP |
Tools & capabilities
Fmeca tools 12
session.openStart or resume a session; optionally selects the matrix strategy and records analysis metadata (`title`, `level`, `aspect`, `scope_paths`, `parent`), all fixed for the session's life.appendAdd a failure mode (`add_failure_mode`), add a mitigation (`add_mitigation`), or re-score an existing failure mode (`rescore`). `set_mitigation_status` moves a mitigation through planned, implemented, verified or abandoned (verified needs evidence other than a note). `set_failure_mode_disposition`…state.getRead-only projection of the session: every failure mode with its computed criticality, residual, and standing.risk.nextThe highest-criticality unmitigated failure mode — what to address next.readiness.assessThe readiness gate: is every High/Medium residual reduced and every blocker cleared?report.exportThe full FMECA table for the session.scoring.catalogThe fixed observation vocabulary for a strategy — the ids the caller draws from.analyzeStateless one-shot: hand over an entire analysis, get back the entire computed report. No session, no persistence.session.listEvery analysis in the state dir (the project's `.fmeca/` when there is one), with its metadata, standing counts (excluded failure modes are counted separately), `ready`, `ready_verified` and resolution counts. Filters: `level`, `aspect`, `parent`. A log that fails to replay is listed with its error.vetAdvisory: asks Jev (via OpenRouter, needs `OPENROUTER_API_KEY`) whether observations, mitigations, coverage and readiness hold up, and returns probabilities beside the deterministic gate. Never writes or changes a score; without a key it reports `vet_unavailable`.actions.suggestRead-only. Reads a session (or an inline analysis) under a [risk policy](docs/policies.md) and suggests actions: per-failure-mode risk bands, evidence confidence, dispositions, tagged actions and a sign-off verdict. Never changes the analysis or the log.policy.listRead-only. The built-in policy presets and the project's `.fmeca/policies/` files, each with its name, hash and class. A project file that does not load is listed with its `error`.
Voidmob MCP tools 30
get_accountBalance, rate limits, and account idsearch_sms_servicesList services with pricesrent_numberRent a US number: one-time verification (15 min, refunded if no SMS) or long-term rental; takes `max_price_centsget_rentalRead status, the latest code and received messages; `wait_seconds` waits for the codecancel_rentalCancel a verification (before any SMS) or long-term rental (within 60 min), with a full refundreuse_numberFree or paid reuse of an earlier verification's number (paid: `max_price_cents`)re_rent_rentalRe-rent an expired long-term rental's number for another period; takes `max_price_centstoggle_auto_renewTurn auto-renewal on or off (rentals and dedicated numbers)search_dedicated_countriesCountries, monthly prices, and stockpurchase_dedicated_numberBuy a private all-services monthly number; takes `max_price_centsget_dedicated_numberStatus and received SMS with parsed codessearch_esim_plansFind global data plans- +18 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Fmeca
{
"mcpServers": {
"fmeca": {
"command": "npx",
"args": [
"-y",
"@matthew-cochran/fmeca"
]
}
}
}
Voidmob MCP
{
"mcpServers": {
"voidmob-mcp": {
"command": "npx",
"args": [
"-y",
"@voidmob/mcp"
],
"env": {
"VOIDMOB_API_KEY": "YOUR_VOIDMOB_API_KEY_HERE",
"VOIDMOB_READ_ONLY": "YOUR_VOIDMOB_READ_ONLY_HERE",
"VOIDMOB_MAX_ORDER_CENTS": "YOUR_VOIDMOB_MAX_ORDER_CENTS_HERE",
"VOIDMOB_BUDGET_CENTS": "YOUR_VOIDMOB_BUDGET_CENTS_HERE"
}
}
}
}
Frequently asked questions
Fmeca is categorized under Communication and uses a local stdio subprocess. Voidmob MCP belongs to Communication and uses a local stdio subprocess. Pick Fmeca for communication work and Voidmob MCP for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Fmeca is listed as free. Auth: no auth required. Voidmob MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add fmeca and voidmob-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fmeca has a quality signal of 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Voidmob MCP has 59/100 (Good) with 1 views, 0 installs and 27 GitHub stars.