Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.yasmanycastillo/model-shunt

PYPI · MODEL-SHUNT · 2 COMPONENTS

Model routing for AI agents: delegate bulk reads & boilerplate to cheap worker models.

+15 this week 84 Trust /100

Last scanned (10 hours ago)

Scores higher than 85% of PyPI servers

Category AI and Machine Learning

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 365 tokens (~121/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 18 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 17 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 16 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 15 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 13 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed pypi/model-shunt@1.2.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~365 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
bulk_read ~132

Reads multiple or large files and answers a targeted question using a cheap, fast worker model (e.g. Gemini Flash, Groq, Ollama). Saves ~90% tokens by returning only structured bullet points.

NameTypeReqDescription
file_pathsarrayyesList of file paths to analyze
modelstring–Optional model override (or 'auto' to select the best available reader model)
providerstring–Optional provider override (gemini, groq, openai, deepseek, anthropic, ollama, openrouter)
questionstringyesThe specific question to answer about the files

No output schema declared.

No examples provided.

code_write ~148

Generates boilerplate code (tests, mocks, stubs, configs) matching the patterns of a reference file. Can write directly to disk without consuming frontier output tokens.

NameTypeReqDescription
modelstring–Optional model override (or 'auto' to select the best available writer model)
providerstring–Optional provider override (gemini, groq, openai, deepseek, anthropic, ollama, openrouter)
reference_pathstringyesPath to reference file whose conventions, style, and structure should be replicated
specstringyesDescription of what code to generate
target_pathstring–Optional path where generated code should be written directly on disk

No output schema declared.

No examples provided.

get_available_models ~85

Discovers active models from the worker provider and recommends the best model for reading (high context / low cost) and writing (code intelligence). Enables calling agents to delegate dynamically to the best model.

NameTypeReqDescription
providerstring–Optional provider to query (gemini, groq, openai, deepseek, anthropic, ollama, openrouter). Defaults to active provider.

No output schema declared.

No examples provided.

Install

How do I install the io.github.yasmanycastillo/model-shunt MCP server?

io.github.yasmanycastillo/model-shunt runs locally as a PyPI package, launched with uvx model-shunt. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · model-shunt

# add to Claude Code
claude mcp add yasmanycastillo-model-shunt -- uvx model-shunt
Common questions

What is the io.github.yasmanycastillo/model-shunt MCP server?

io.github.yasmanycastillo/model-shunt is an MCP server listed in the public MCP registry as io.github.yasmanycastillo/model-shunt. Model routing for AI agents: delegate bulk reads & boilerplate to cheap worker models. This page covers its PyPI package (model-shunt).

Is the io.github.yasmanycastillo/model-shunt MCP server safe to use?

io.github.yasmanycastillo/model-shunt scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.yasmanycastillo/model-shunt MCP server expose?

io.github.yasmanycastillo/model-shunt exposes 3 tools: bulk_read, code_write, get_available_models. Their descriptions and schemas cost roughly 365 tokens of context every time the server is loaded.

Is the io.github.yasmanycastillo/model-shunt MCP server still maintained?

io.github.yasmanycastillo/model-shunt is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.yasmanycastillo/model-shunt MCP server under?

io.github.yasmanycastillo/model-shunt declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.yasmanycastillo/model-shunt MCP server?

VerifyMCP ran 16 checks on io.github.yasmanycastillo/model-shunt, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.