Local Model Suitability MCP
REMOTE · LOCAL-MODEL-SUITABILITY-MCP-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS
Check if a task runs locally vs cloud. Save money on calls that don't need cloud inference.
Last scanned (2 hours ago)
Scores higher than 66% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Sept 26 0
- Server version: 1.1.32 → 1.1.34 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- Server version: 1.1.31 → 1.1.32 functional
- 20 Aug 26 0
- Server version: 1.1.30 → 1.1.31 functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 5 Nov 2026 · Probed https://local-model-suitability-mcp-production.up.railway.app
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of local-model-suitability-mcp-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://local-model-suitability-mcp-production.up.railway.app | Unreachable | ||
| http (plaintext) | http://local-model-suitability-mcp-production.up.railway.app | HTTPS enforced |
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.
How do I install the Local Model Suitability MCP server?
Local Model Suitability MCP is a hosted endpoint at https://local-model-suitability-mcp-production.up.railway.app/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · local-model-suitability-mcp-production.up.railway.app
claude mcp add --transport http ojaskord-local-model-suitability-mcp 'https://local-model-suitability-mcp-production.up.railway.app/'
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 hosted endpoint (https://local-model-suitability-mcp-production.up.railway.app).
Is the Local Model Suitability MCP server safe to use?
Local Model Suitability MCP scores 76 out of 100 on VerifyMCP. 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.
Does the Local Model Suitability MCP server require authentication?
Its publisher declares no required credentials for Local Model Suitability MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Local Model Suitability MCP server still maintained?
Local Model Suitability MCP is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.