MCP.Market

Volante MCP server

by ribato22·io.github.ribato22/volante·v0.10.0·1 stars

Routes to the best predicted fit from configured metadata/evidence after hard-capability filtering.

B75/100grade B
What users say
No reviews yet
Be the first
Safety scan
B75/100

full report

Adoption
Growing

1 stars21 downloads/wk

Reviews

Write one

Nobody has reviewed Volante yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Volante tools (1, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • volante_runwrite action

    Orchestrate GOAL across the configured models. Volante plans a task DAG, filters hard capability mismatches, and routes each sub-task to the best predicted fit using configured metadata and optional evaluation evidence. It runs tasks one-shot or in an agentic tool loop, then synthesizes one final answer. Returns that answer plus status, cost, and route evidence.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

1 medium
  • Code scan97 source files scanned20/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 5 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • mediumeval / new Function usedexec.eval
    volante-0.10.0/eval/tasks.py: …3+5"). You MUST NOT use ' "Python's eval(), exec(), ast.literal_eval(), or any si…
Overall 75/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Volante compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
75/100
higher than 45% of 48,255 servers
Tools
1
the typical server has 7
Tools that change things
100%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
21
more than 8% of 12,191 servers with a package

What its tools let an agent do: 1 change

Install Volante in Claude Code, Cursor or VS Code

claude mcp add volante -- uvx volante
Add to Cursor

What the publisher says

From the Volante repository's README, as published. We do not edit it. Read it on GitHub

Volante

A transparent, user-owned model router that checks its own answers (alpha). Volante routes a goal across the models you configured — enforcing hard capabilities first, ranking the rest on explainable metadata and evaluation evidence — and can then verify the result by RUNNING it: assertions derived from your goal, executed in a sandbox, reported check by check. Inventory, policy, credentials and decision traces stay on your machine. By default it answers in ONE call — across 72 paired runs, planning and synthesising scored -0.047 against that [95% CI -0.135, +0.041] at 8.8x the cost, so the interval bounds its best case near +0.04. --orchestrate opts back into the task DAG for the work that genuinely needs a tool loop, which one call cannot do.

What the measurements say, including the parts that do not flatter it. This project runs a 3-arm eval against itself and publishes the losses. Orchestration does not reliably beat a single strong model: an earlier release of this README claimed +0.289 at p<0.005, it failed to reproduce, and on the goal built to give decomposition headroom a stronger model in the same family scores 0.958 alone. Four predictive gates, a repair pass and a model-escalation policy were all built, measured, and discarded. What survived every test is narrower and real — the router, the reliability work (unparsable output 2 runs in 8 -> 0 in 8), and the verifier. Full numbers, method and corrections: eval/artifacts/README.md.

Selection quality is an evidence-based prediction, not a claim of a universal winner. Volante does not yet ship published representative cross-provider benchmarks or automatic score calibration. Built without an orchestration framework (no LangChain / CrewAI / LiteLLM).

A volante steers the game: the deep-lying midfielder who reads the whole pitch and sends the

ball where it does the most good — then takes it back. One mind, many players.

Highlights

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Volante: common questions

Is Volante MCP server safe?
Mostly: it is graded B (75/100). Read the Volante safety report
How do I install Volante?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Volante need an API key?
Yes. The registry entry asks for ANTHROPIC_API_KEY, MOONSHOT_API_KEY, OLLAMA_API_KEY, OPENAI_COMPAT_KEY and 2 more.
Is Volante maintained?
The last commit was 6 days ago (2026-10-29). The latest release is v0.10.0.
How does Volante compare with other MCP servers?
safety score 75/100 (higher than 45% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 100% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.