ModelSpec
REMOTE · API.MODELSPEC.DEV
Find AI models that fit a job from your requirements, sourced benchmarks and real cost.
Available components
Last scanned (3 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 18 Oct 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 Security46
- 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 9 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability54
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2347 tokens (~260/item across 9 items; 9 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 48% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 18 Oct 26 −1
- Tool “compare_models” rewrote its description, which is the text the model reads security
- Tool “decide” rewrote its description, which is the text the model reads security
- Tool “feedback” rewrote its description, which is the text the model reads security
- Tool “list_use_cases” rewrote its description, which is the text the model reads security
- Tool “model_info” rewrote its description, which is the text the model reads security
- Tool “policy_check” rewrote its description, which is the text the model reads security
- Tool “rank” rewrote its description, which is the text the model reads security
- Tool “vocab” rewrote its description, which is the text the model reads security
- Tool coverage: 60% → 48% ▼ functional
- Schema quality: 310 → 260 ▲ functional
- Server version: 2b2e9a38f19012658f2b390cbb3f00eb8a00ae75 → b4a7074f37a3ba940bd86db9d1e2459a25fd40af functional
- New tool “hardware_fit” functional
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- Server version: 0afd269c0e2e4dbb86dd073f4b8669437470fb07 → 2b2e9a38f19012658f2b390cbb3f00eb8a00ae75 functional
- 15 Oct 26 56
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 18 Oct 2026 · Probed https://api.modelspec.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=modelspec.dev | CN=WE1,O=Google Trust Services,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 3e1b7020958371a10e5d39859889fcff |
| SANs: modelspec.dev, *.modelspec.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.modelspec.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| modelspec.dev. | 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://api.modelspec.dev/mcp | Verified | 200 | |
| http (plaintext) | http://api.modelspec.dev/mcp | Inconclusive | 405 |
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 →
compare_models ~147
What facts do 2 to 4 named models have? Returns sourced snapshot facts, offerings and evidence in caller order; unknowns stay null. Needs an API key (Authorization: Bearer). Costs 2 credits a call; $0.0053–$0.02 per credit by plan or pack (https://modelspec.dev/pricing/). It doesn't choose a model and does not rank. Proxies POST https://api.modelspec.dev/v1/compare-models with {models: [...]} at most 16 KB.
| Name | Type | Req | Description |
|---|---|---|---|
| models | array | yes | 2 to 4 distinct catalogue ids, such as openai/gpt-5-6, in caller order |
No output schema declared.
No examples provided.
decide ~713
Which models fit this job? Call decide early. Returns answer, ranked results, may_qualify, reading and recovery hints, decision_id and snapshot. Never add a gate or constraint the user didn't state. Relax only constraints the user stated, one at a time, and say what was relaxed and why. Prefer the answer's own `relax` suggestions. A tie stays a tie. Don't promote a member by knowledge from outside the response. Cite only evidence in the response. Never add benchmark figures from memory. Tied or partial answer: report the tie and caveats, pick no member; a null answer names no pick and says what's missing. A null cost is unknown. Never show it as $0.00 or "free". One vocabulary lookup per unknown facet, then decide. Read `next` before another call. Size `task_tokens` from the user's own task, and say what you assumed. Don't copy the guide's example sizes. Template weights are examples, not requirements. If the evidence basis or board does not match the task, say so: Arena web-dev evidence does not establish chat quality. p_best is the probability of ranking best under the Spec and evidence uncertainty, not the probability of matching the user's task or satisfying its requirements. Read reading when present. Present answer.kind=tied among all answer.members, including with_estate; tie-breakers are conditional. State requirements in reading.not_applied or error.issues that were not applied, including requirements removed after a rejected call. A retry does not verify them. Report estimates as estimates: fits_hardware membership is not measured fit for a specific quantization and context workload. Follow reading.do_not_claim. Never claim a rank the response does not show. Present `summary_for_user` to the user unchanged and keep every `must_mention` item. When `next_move` is present, offer it instead of a pick. Needs an API key (Authorization: Bearer). Costs 1 or 2 credits a call; $0.0053–$0.02 per credit by plan or pack (https://modelspec.dev/pricing/). Not a router:…
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
feedback ~168
Was an answer reliable? Returns recorded/not_recorded for a rating after acting; include decision_id. Free, no key, and no Authorization header is forwarded. No prompts, keys or personal details in note; no questions or support. Storage stays off until covered by the privacy statement. Proxies POST https://api.modelspec.dev/v1/feedback.
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | string | – | The decision_id of the answer this is about. |
| note | string | – | Optional. What was wrong or right. Never a prompt, a key or personal details. |
| rating | string | yes | How the answer held up when you acted on it. |
| template | string | – | Optional. The decision template you used. |
| trying_to_decide | string | – | Optional. What you were trying to decide. |
No output schema declared.
No examples provided.
hardware_fit ~181
Does this workload fit? Returns measured for an exact cited run, estimated with sources, or undetermined. Uses basis full with sourced headroom, or basis lower_bound for unlikely only. Missing headroom cannot establish likely. Estimates never prove fit. Memory is decimal GB per device, never pooled. Needs an API key (Authorization: Bearer). Costs 2 credits a call; $0.0053–$0.02 per credit by plan or pack (https://modelspec.dev/pricing/). It doesn't choose a model. Proxies POST https://api.modelspec.dev/v1/hardware-fit.
| Name | Type | Req | Description |
|---|---|---|---|
| batch | – | – | – |
| context | – | – | – |
| device_count | – | – | – |
| memory | – | – | Optional memory override in decimal GB per device |
| model | – | – | – |
| quantisation | – | – | – |
| runtime | – | – | – |
| sku | – | – | – |
No output schema declared.
No examples provided.
list_use_cases ~47
Which legacy profiles and ranking rules exist? Returns https://modelspec.dev/api/rank/profiles.json with evidence floors and the neutrality commitment. Needs an API key. Use decide for decisions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
model_info ~75
What does one model's card say? Reads https://modelspec.dev/api/models/<model_id>.json. Split mode returns only its display name. Needs an API key. Not current evidence or a ranking; use decide.
| Name | Type | Req | Description |
|---|---|---|---|
| model_id | string | yes | Catalogue id, e.g. openai/gpt-5-6 |
No output schema declared.
No examples provided.
policy_check ~171
Which models and platforms does my policy allow? Returns pass, fail or undetermined per model/platform for licence, origin and data handling; undetermined is not a pass. Needs an API key (Authorization: Bearer). Costs 5 credits a call; $0.0053–$0.02 per credit by plan or pack (https://modelspec.dev/pricing/). It doesn't choose a model; use decide among passing rows. Proxies POST https://api.modelspec.dev/v1/policy-check with these arguments and Authorization.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| models | array | – | – |
| offset | integer | – | – |
| platforms | array | – | – |
| policy | object | yes | – |
| require_no_undetermined | boolean | – | – |
| verdicts | array | – | – |
No output schema declared.
No examples provided.
rank ~212
Legacy v1; use decide. Deprecated fixed-benchmark ranking; scores lag the catalogue and newer models may be unranked. Which models lead a fixed use-case profile? Returns a shortlist with evidence_basis and input provenance, not a quality verdict. Needs an API key (Authorization: Bearer). Costs 1 credit a call; $0.0053–$0.02 per credit by plan or pack (https://modelspec.dev/pricing/). Don't call it as a fallback when decide has no single leader; report its tie. Present `summary_for_user` to the user unchanged and keep every `must_mention` item. When `next_move` is present, offer it instead of a pick. Proxies POST https://api.modelspec.dev/v1/rank with these arguments.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | object | – | – |
| environment | object | – | – |
| limit | integer | – | – |
| use_case | string | yes | Ranking profile id, as published in /api/rank/profiles.json |
No output schema declared.
No examples provided.
vocab ~288
What can a Spec say? Returns ids and task types. Needs an API key. One vocabulary lookup per unknown facet, then decide. Use decide to compare models. Starter includes a minimal Spec. Compact pages: at most 20 rows, no counts; empty pages end results. Search ranks all tokens before subsets; misses offer nearest ids. Split-mode full details exclude model facts and counts.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Full returns all display details; defaults to compact. Cross-section matches remain paged |
| id | string | – | Full details for this exact, case-sensitive id; starter resolves across sections and intersects with search |
| ids | array | – | Full details for these exact, case-sensitive ids; starter resolves across sections and intersects with search |
| limit | integer | – | Page size; defaults to 20. Cross-section lookups page even full details and ids |
| offset | integer | – | Skip this many ranked cross-section matches or compact section rows; defaults to 0 |
| search | string | – | Search every section's ids, labels, definitions, values and synonyms. All tokens rank first; else content tokens match, stopwords omitted. A miss returns nearest ids. A non-starter section scopes the… |
| section | string | – | Defaults to starter; with search or id/ids searches every section except coverage. An explicit non-starter section scopes the lookup |
No output schema declared.
No examples provided.
How do I install the ModelSpec MCP server?
ModelSpec is a hosted endpoint at https://api.modelspec.dev/mcp, 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 · api.modelspec.dev
claude mcp add --transport http turbobeest-modelspec 'https://api.modelspec.dev/mcp'
What is the ModelSpec MCP server?
ModelSpec is an MCP server listed in the public MCP registry as io.github.turbobeest/modelspec. Find AI models that fit a job from your requirements, sourced benchmarks and real cost. This page covers its hosted endpoint (https://api.modelspec.dev/mcp).
Is the ModelSpec MCP server safe to use?
ModelSpec scores 56 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 ModelSpec MCP server expose?
ModelSpec exposes 9 tools: rank, model_info, list_use_cases, policy_check, decide, and 4 more. Their descriptions and schemas cost roughly 2,002 tokens of context every time the server is loaded.
Does the ModelSpec MCP server require authentication?
No. We connected to ModelSpec without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ModelSpec MCP server still maintained?
ModelSpec is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.