Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

modelright

REMOTE · MODELRIGHT.DEV

Live registry of AI model specs, context windows, and per-token pricing.

Available components

+3 this week 69 Trust /100

Last scanned (4 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 17 Oct 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 435 tokens (~72/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
Changelog

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.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 17. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 10. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 7 Oct 26 65

    First indexed and scored.

Diagnostics

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 17 Oct 2026 · Probed https://modelright.dev/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=modelright.dev CN=YE1,O=Let's Encrypt,C=US 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA384 642fc50eb877189c1396f358a392aebd737
SANs: modelright.dev
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 modelright.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
modelright.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://modelright.dev/api/mcp Verified 200
http (plaintext) http://modelright.dev/api/mcp HTTPS enforced 301 https://modelright.dev/api/mcp
MCP tools · 6 exposed · ~435 tokens

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 →

Tool Tokens
compare_models ~49

Side-by-side comparison of 2-10 models by provider/slug: context window, input/output price per 1M tokens, modalities, status.

NameTypeReqDescription
modelsarrayyesModels to compare

No output schema declared.

No examples provided.

get_ingest_status ~50

Data-freshness check: registry totals and the most recent ingest runs (source, model count, status, time).

NameTypeReqDescription
limitinteger–Recent ingest runs to return (default 10)

No output schema declared.

No examples provided.

get_model ~90

Full detail for one model (provider+slug from search_models): specs, current price, status, and recent price/availability snapshots.

NameTypeReqDescription
providerstringyesProvider slug, e.g. 'openai'
slugstringyesModel slug, e.g. 'gpt-4o'
snapshotsinteger–Recent snapshots to include (default 10, 0 to skip)

No output schema declared.

No examples provided.

list_models ~147

List tracked models with pricing and context windows. Filter by provider, modality tag, status, or price/context bounds.

NameTypeReqDescription
limitinteger–Max results (default 100)
maxInputPricePerMnumber–Max input price per 1M tokens (USD)
minContextWindowinteger–Minimum context window
modalitystring–Modality tag filter, e.g. 'text', 'image', 'audio'
providerstring–Provider slug filter, e.g. 'anthropic'
sortstring–Sort order (default name)
statusstring–Status filter, e.g. 'available', 'deprecated'

No output schema declared.

No examples provided.

list_providers ~34

List providers tracked by the registry with their model counts. Use provider slugs in list_models / get_model / compare_models.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_models ~65

Substring search across model name, slug, and provider — the fast path to a model's provider/slug pair for the detail tools.

NameTypeReqDescription
limitinteger–Max results (default 20)
qstringyesSearch text, e.g. 'sonnet'

No output schema declared.

No examples provided.

Install

How do I install the modelright MCP server?

modelright is a hosted endpoint at https://modelright.dev/api/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 · modelright.dev

# add to Claude Code
claude mcp add --transport http dev-modelright-modelright 'https://modelright.dev/api/mcp'
Common questions

What is the modelright MCP server?

modelright is an MCP server listed in the public MCP registry as dev.modelright/modelright. Live registry of AI model specs, context windows, and per-token pricing. This page covers its hosted endpoint (https://modelright.dev/api/mcp).

Is the modelright MCP server safe to use?

modelright scores 69 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 modelright MCP server expose?

modelright exposes 6 tools: list_providers, search_models, list_models, get_model, compare_models, get_ingest_status. Their descriptions and schemas cost roughly 435 tokens of context every time the server is loaded.

Does the modelright MCP server require authentication?

No. We connected to modelright without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the modelright MCP server still maintained?

modelright is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.