Mundane vs Jevcore MCP
A side-by-side look at the Mundane and Jevcore MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mundane for developer tools work as a local process; choose Jevcore MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Mundane when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MUNDANE_API_BASE, MUNDANE_API_KEY. - You want tools like
list_capabilities, search_workers, find_workers_by_skill.
Choose Jevcore MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
jev_ask, jev_rank, jev_check.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 52/100 · Good | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Free |
| Required env vars | MUNDANE_API_BASEMUNDANE_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 102 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 38 | 3 |
| Full listing | View Mundane | View Jevcore MCP |
Tools & capabilities
Mundane tools 38
list_capabilitiesList task capabilities this agent may dispatch, with per-capabilitysearch_workersFind verified workers near a point matching capability, rating, and pricefind_workers_by_skillFind verified workers with a skill wherever they are, ranked for your goal; areas onlyget_workerReturn one worker's public profile and reputation. `ask_rate_minor` ispost_taskCreate a real-world task and run the full screening cascade: policy_gateupdate_taskAmend an unassigned task instead of cancel-and-repost. Supply only themake_offerOffer a task to a worker. `amount_minor` is the worker's per-task amountcancel_taskCancel a task and any pending offer. An accepted task may charge thecreate_task_chainCreate and screen a chain of 2-5 steps with the handoff windows between themoffer_chain_linkOffer one step to a worker who is open to chains; escrow held as for any offerget_chain_statusEach step, each handoff and what the chain is waiting onreschedule_chain_handoffA new window for a handoff that failed or could not be agreed- +26 more on the listing page
Jevcore MCP tools 3
jev_askAsk TypeSafe Jev one or more typed questions about a single piece of state. Jev does not generate text: it returns a selected option and calibrated probabilities. Use it for judgments the rest of the work branches on — routing, classifying, scoring, triaging. Do NOT use it to write prose, explain, summarize, or generate code. Question types: "noul" is yes/no and returns the probability of true; "choice" picks one of the criteria keys you declare; "score" places the state on an ordered scale whose levels you declare in ascending order. A noul may also declare "boundary" — what true means and what false means — which is worth supplying whenever the line between them is not obvious. Batch related questions into one call: they are answered against the same state in one round-trip. A score question answers with a numeric "score" that may fall between levels, a "legend" mapping each level index to its description, and probabilities per level. This tool returns probabilities, not decisions — apply your own confidence threshold before acting, and treat a low-confidence answer as unknown rather than picking for it.jev_rankRank a list of candidates by how well each satisfies one stated criterion. Returns every candidate with an independent relevance probability, sorted. Use it to order search hits, triage a backlog, or find the one item that answers a question. The probabilities are independent per-candidate judgments, NOT a distribution that sums to 1. A flat set of scores means "none of these stands out", not a fine-grained ordering. What you send is capped, and the two caps behave differently. The candidate list is truncated at 16,000 characters, and the reply carries `truncated: true` when that happens — check for it, because a cut list is still ranked and the scores then describe what Jev actually read rather than what you sent. The generated questions are refused at 4,000 characters instead: exceeding that gives you an error asking for fewer or smaller items, never a silent best-N, so retrying the same call cannot help. Because the criterion is repeated into every candidate's question, that second cap is what bounds the candidate count — measured, an ordinary criterion fits 20 candidates and a 400-character criterion fits 7, while candidate length does not change the count at all and only starts truncating the list past roughly 1,600 characters per candidate.jev_checkCheck whether a piece of evidence supports a specific claim. Returns "supported", "contradicted", "conflicted", "insufficient", or "unknown", with the underlying probabilities. The distinction between "not supported" and "contradicted" is the reason to use this rather than reading the evidence yourself. It judges one claim against the evidence you give it. It does not search for evidence, and it cannot detect that you omitted the decisive passage.
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.
Mundane
{
"mcpServers": {
"mundane": {
"command": "uvx",
"args": [
"mundane-mcp"
],
"env": {
"MUNDANE_API_BASE": "YOUR_MUNDANE_API_BASE_HERE",
"MUNDANE_API_KEY": "YOUR_MUNDANE_API_KEY_HERE"
}
}
}
}
Jevcore MCP
{
"mcpServers": {
"jevcore-mcp": {
"command": "npx",
"args": [
"-y",
"jevcore-mcp"
]
}
}
}
Frequently asked questions
Mundane is categorized under Developer Tools and uses a local stdio subprocess. Jevcore MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Mundane for developer tools work and Jevcore MCP for developer tools.
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.
Mundane has no declared pricing — check the project's own site. Jevcore MCP is listed as free. 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 mundane and jevcore-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mundane has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Jevcore MCP has 67/100 (Great) with 1 views, 0 installs and 102 GitHub stars.