Skip to content
OmniDev logo

OmniDev MCP server

Which MCP servers are OmniDev's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-28

← Back to OmniDev

Whose server it is
  • Registry nametech.omnidev/omniproviderverified in the MCP registry

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

When we asked itchecked 2026-10-28
  • Stateanswerschecked 2026-10-28
  • Tools4
  • Server calls itselftech.omnidev/omniprovider
  • Server version1.0.0
  • Protocol version2025-06-18

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

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 6 of the 7 days it takes to judge reliability.

Once connected

  • For "Compare per-token prices across the model catalog", the likely first call is omniprovider_list_models.
  • Parameters are untyped or undescribed in 1 of 4 tools: check arguments before calling.

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.

Measured dailydaily checks: 6, the first on 2026-10-28
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
  • Answeredmeasuring6 of the 7 daily checks it takes to print a share
  • Median first answer209 ms
  • Space in an agent's context≈ 544 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 96 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 4

What an agent can do with it

  • not sure · Send chat completion requests paid per call in USDC
  • not sure · Generate cited briefs on demand, paid per request
  • can do · Compare per-token prices across the model catalog

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

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 →

Tools it offers4 tools · read 2026-10-28
  • omniprovider_list_models

    Returns the public catalog: model ids, context windows, maximum output tokens, price per million input and output tokens, accepted payment rails and prepaid packs that can be bought now.

  • omniprovider_get_pricing

    Returns prices: fixed per-call prices of the nano, small and brief routes, and per-token prices of the catalog. With a model and token counts it also returns an estimated cost and the minimum charge per rail.

  • omniprovider_get_quote

    Sends one unpaid request to a paid route and returns the 402 payment requirements (amount, currency, network, payee, protocol). No payment is made and no credential is sent; the response is the quote for that exact request body.

  • omniprovider_how_to_pay

    Returns the payment flow for a rail: endpoint URL, required headers, the client nonce format, and client commands. Payment is produced by the caller's own wallet tooling; this server holds no keys.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "omniprovider": {
      "type": "http",
      "url": "https://mcp.omnidev.tech/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http omnidev https://mcp.omnidev.tech/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.omnidev.tech/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.