Local Model Suitability MCP
NPM · LOCAL-MODEL-SUITABILITY-MCP · 2 COMPONENTS · SCANNED SEP 20
Check if a task runs locally vs cloud. Save money on calls that don't need cloud inference.
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 10 of 42 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 255 tokens (~255/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Local Model Suitability MCP server?
Local Model Suitability MCP runs locally as an npm package, launched with npx -y local-model-suitability-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · local-model-suitability-mcp
claude mcp add ojaskord-local-model-suitability-mcp -- npx -y local-model-suitability-mcp
{
"mcpServers": {
"ojaskord-local-model-suitability-mcp": {
"command": "npx",
"args": [
"-y",
"local-model-suitability-mcp"
]
}
}
} {
"servers": {
"ojaskord-local-model-suitability-mcp": {
"command": "npx",
"args": [
"-y",
"local-model-suitability-mcp"
]
}
}
} codex mcp add ojaskord-local-model-suitability-mcp -- npx -y local-model-suitability-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ojaskord-local-model-suitability-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"local-model-suitability-mcp"
],
"enabled": true
}
}
} openclaw mcp add ojaskord-local-model-suitability-mcp --command npx --arg -y --arg local-model-suitability-mcp
mcp_servers:
ojaskord-local-model-suitability-mcp:
command: "npx"
args: ["-y", "local-model-suitability-mcp"] {
"McpServers": {
"ojaskord-local-model-suitability-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"local-model-suitability-mcp"
]
}
}
} assistant mcp add ojaskord-local-model-suitability-mcp -t stdio -c npx -a -y local-model-suitability-mcp
{
"mcpServers": {
"ojaskord-local-model-suitability-mcp": {
"command": "npx",
"args": [
"-y",
"local-model-suitability-mcp"
]
}
}
} 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.
- 20 Sept 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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 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.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/local-model-suitability-mcp@1.1.23
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 42 packages
| Packages resolved | 42 |
|---|---|
| Deprecated | 1 |
| Stale | 9 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_local_viability ~255
Checks whether a task can be handled by a local model instead of a cloud API. Call this BEFORE your agent routes any task to a cloud model — at the moment a task is ready to be sent and the model has not yet been selected. Use this when your agent is about to make a cloud inference call and wants to determine whether a local model could handle it at lower cost. Returns LOCAL/CLOUD/EITHER verdict with recommended model. If verdict is LOCAL, skip the cloud call entirely — saves cost on every routable inference call. Pass data_sensitivity=CONFIDENTIAL to force LOCAL verdict for tasks that must not leave the machine. Do not route to cloud without checking local viability first.
| Name | Type | Req | Description |
|---|---|---|---|
| data_sensitivity | string | – | CONFIDENTIAL forces LOCAL verdict regardless of task complexity — data must not leave the machine. Defaults to PUBLIC. |
| quality_threshold | string | – | PRODUCTION = output quality matters and errors are costly. PROTOTYPE = approximate results acceptable. BEST_EFFORT = speed and cost trump quality. Defaults to PRODUCTION. |
| task | string | yes | The exact task you are about to send to a cloud model. Be specific — include what the input is and what output you need. |
| Name | Type | Req | Description |
|---|---|---|---|
| _disclaimer | string | yes | – |
| analysis_type | string | – | – |
| checked_at | string | yes | – |
| cloud_justified_reason | string|null | – | Non-null only when verdict is CLOUD |
| confidence | string | yes | – |
| data_sensitivity | string | – | – |
| data_sensitivity_override | boolean | – | Present only when data_sensitivity=CONFIDENTIAL forced a LOCAL verdict |
| estimated_cost_saving | string | – | – |
| reason | string | yes | – |
| recommended_local_models | array | – | Present when verdict is LOCAL or EITHER |
| task_quality_threshold | string | – | – |
| verdict | string | yes | – |
No examples provided.
What is the Local Model Suitability MCP server?
Local Model Suitability MCP is listed in the public MCP registry as io.github.OjasKord/local-model-suitability-mcp. Check if a task runs locally vs cloud. Save money on calls that don't need cloud inference. This page covers its npm package (local-model-suitability-mcp).
Is the Local Model Suitability MCP server safe to use?
Local Model Suitability MCP scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 Local Model Suitability MCP server expose?
Local Model Suitability MCP exposes 1 tool: check_local_viability. Their descriptions and schemas cost roughly 255 tokens of context every time the server is loaded.
Is the Local Model Suitability MCP server still maintained?
Local Model Suitability MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Local Model Suitability MCP server under?
Local Model Suitability MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.