Local Model Suitability MCP
REMOTE · LOCAL-MODEL-SUITABILITY-MCP-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS · SCANNED SEP 21
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 against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 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
- 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 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/'
{
"mcpServers": {
"ojaskord-local-model-suitability-mcp": {
"url": "https://local-model-suitability-mcp-production.up.railway.app/"
}
}
} {
"servers": {
"ojaskord-local-model-suitability-mcp": {
"type": "http",
"url": "https://local-model-suitability-mcp-production.up.railway.app/"
}
}
} [mcp_servers.ojaskord-local-model-suitability-mcp] url = "https://local-model-suitability-mcp-production.up.railway.app/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ojaskord-local-model-suitability-mcp": {
"type": "remote",
"url": "https://local-model-suitability-mcp-production.up.railway.app/",
"enabled": true
}
}
} openclaw mcp add ojaskord-local-model-suitability-mcp --url 'https://local-model-suitability-mcp-production.up.railway.app/' --transport streamable-http
mcp_servers:
ojaskord-local-model-suitability-mcp:
url: "https://local-model-suitability-mcp-production.up.railway.app/" {
"McpServers": {
"ojaskord-local-model-suitability-mcp": {
"Transport": "http",
"Url": "https://local-model-suitability-mcp-production.up.railway.app/"
}
}
} assistant mcp add ojaskord-local-model-suitability-mcp -t streamable-http -u 'https://local-model-suitability-mcp-production.up.railway.app/'
{
"mcpServers": {
"ojaskord-local-model-suitability-mcp": {
"type": "http",
"url": "https://local-model-suitability-mcp-production.up.railway.app/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 8 Sept 26 0
- Server version: 1.1.32 → 1.1.34 functional
- 26 Aug 26 +1
- 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 +1
- 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
- 31 Jul 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
- 30 Jul 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
- 27 Jul 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 21 Sept 2026 · Probed https://local-model-suitability-mcp-production.up.railway.app
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
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 | Verified | 200 | |
| http (plaintext) | http://local-model-suitability-mcp-production.up.railway.app | HTTPS enforced | 301 | https://local-model-suitability-mcp-production.up.railway.app/ |
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 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?
No. We connected to Local Model Suitability MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.