modelright MCP server

• Registry namedev.modelright/modelrightverified in the MCP registry

The registry name sits under modelright.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools6
• Server calls itselfmodelright
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 32 ms.

• Its tools do every use case we checked: compare AI model specs and prices side by side; check context window sizes across providers.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• What an agent can do with it2 of 2 use cases
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer127 ms
• Space in an agent's context≈ 820 tokensthe definitions of all its tools (6), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 6 of 6

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• list_providers

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

• search_models

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

• list_models

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

• get_model

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

• compare_models

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

• get_ingest_status

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