mcp-registry/io.github.ojaskord/local-model-suitability-mcp · v1.1.34
Also listed as glama/ojaskord/local-model-suitability-mcp
As of 2026-10-21 19:18 UTC, the Ojaskord Local Model Suitability MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 2 minutes.
Check if a task runs locally vs cloud. Save money on calls that don't need cloud inference.
Claude Code
claude mcp add --transport http ojaskord-local-model-suitability-mcp-ser https://local-model-suitability-mcp-production.up.railway.app
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"ojaskord-local-model-suitability-mcp-ser": {
"type": "http",
"url": "https://local-model-suitability-mcp-production.up.railway.app"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
1 of 1 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
Handshake + tools/list takes ~1,584 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.ojaskord%2Flocal-model-suitability-mcp/fixes
{
"name": "check_local_viability",
"description": "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 routa",
"inputSchema": {
"type": "object",
"required": [
"task"
],
"properties": {
"task": {
"type": "string",
"description": "The exact task you are about to send to a cloud model. Be specific — include what the input is and what output you need."
},
"data_sensitivity": {
"enum": [
"PUBLIC",
"INTERNAL",
"CONFIDENTIAL"
],
"type": "string",
"description": "CONFIDENTIAL forces LOCAL verdict regardless of task complexity — data must not leave the machine. Defaults to PUBLIC."
},
"quality_threshold": {
"enum": [
"PRODUCTION",
"PROTOTYPE",
"BEST_EFFORT"
],
"type": "string",
"description": "PRODUCTION = output quality matters and errors are costly. PROTOTYPE = approximate results acceptable. BEST_EFFORT = speed and cost trump quality. Defaults to PRODUCTION."
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.ojaskord/local-model-suitability-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.ojaskord/local-model-suitability-mcp"}) over MCP.
check_local_viability ~352 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.ojaskord%2Flocal-model-suitability-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.ojaskord%2Flocal-model-suitability-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ojaskord%2Flocal-model-suitability-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ojaskord%2Flocal-model-suitability-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.ojaskord%2Flocal-model-suitability-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f1ab1dad30cf8b4c…, first seen 2026-10-17, included at leaf 4283 of 41,194. Version history · verify what your client received.
Compare: most reliable ml servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-21 19:18 UTC, the Ojaskord Local Model Suitability MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 2 minutes.
Ojaskord Local Model Suitability MCP server advertises 1 tool, including check_local_viability.
Point your MCP client at this streamable-http endpoint: https://local-model-suitability-mcp-production.up.railway.app
Glimind scanned all 1 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.