Local Model Suitability MCP
NPM · LOCAL-MODEL-SUITABILITY-MCP · 2 COMPONENTS · SCANNED AUG 3
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 →
Supply Chain Security88
- 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
- 40 of 42 dependencies flagged as unhealthy (40 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 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).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 Management27
- Stability observed for 8 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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · local-model-suitability-mcp
claude mcp add ojaskord-local-model-suitability-mcp -- npx -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": {
"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.
- 2 Aug 26 +16
- Known CVEs: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: 0.86 → 0.07 ▼ functional
- License: pass → unverified ▼ functional
- Dependency health: 0.86 → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Stability: unverified → 0.23 ▲ functional
- Licence: MIT functional
- 31 Jul 26 −12
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 28 Jul 26 +32
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → 0.86 ▲ functional
- Schema quality: unverified → good ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 27 Jul 26 45
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 42 packages
42 packages in the resolved dependency tree · 40 deprecated · 9 stale.
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.
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.