OmniProvider
REMOTE · MCP.OMNIDEV.TECH
Pay-per-call LLM API for agents: model catalog, pricing, unpaid x402/MPP quotes, how-to-pay.
Available components
Last scanned (4 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 375 tokens (~93/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 71% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "omniprovider_get_quote" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 5 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 24 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.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 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.
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 5 Nov 2026 · Probed https://mcp.omnidev.tech/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.omnidev.tech | CN=YE1,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6a02ccfbf8382dadb7d875cc129f4bb7495 |
| SANs: mcp.omnidev.tech | ||||||
| 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 mcp.omnidev.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| omnidev.tech. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.omnidev.tech/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.omnidev.tech/mcp | HTTPS enforced | 301 | https://mcp.omnidev.tech/mcp |
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 →
omniprovider_get_pricing OmniProvider pricing ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| input_tokens | integer | – | – |
| model | string | – | Catalog model id. |
| output_tokens | integer | – | – |
No output schema declared.
No examples provided.
omniprovider_get_quote OmniProvider price quote ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | JSON request body the quote is computed for (messages or prompt; for /v1/chat/completions also model and max_tokens). |
| route | string | yes | Paid route path. /v1/* accepts MPP, /x402/* accepts x402. |
No output schema declared.
No examples provided.
omniprovider_how_to_pay How to pay OmniProvider ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| rail | string | – | Payment rail; all rails when omitted. |
No output schema declared.
No examples provided.
omniprovider_list_models List OmniProvider models ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tier | string | – | Optional filter by catalog tier. |
No output schema declared.
No examples provided.
How do I install the OmniProvider MCP server?
OmniProvider is a hosted endpoint at https://mcp.omnidev.tech/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 · mcp.omnidev.tech
claude mcp add --transport http tech-omnidev-omniprovider 'https://mcp.omnidev.tech/mcp'
What is the OmniProvider MCP server?
OmniProvider is an MCP server listed in the public MCP registry as tech.omnidev/omniprovider. Pay-per-call LLM API for agents: model catalog, pricing, unpaid x402/MPP quotes, how-to-pay. This page covers its hosted endpoint (https://mcp.omnidev.tech/mcp).
Is the OmniProvider MCP server safe to use?
OmniProvider scores 80 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 OmniProvider MCP server expose?
OmniProvider exposes 4 tools: omniprovider_list_models, omniprovider_get_pricing, omniprovider_get_quote, omniprovider_how_to_pay. Their descriptions and schemas cost roughly 324 tokens of context every time the server is loaded.
Does the OmniProvider MCP server require authentication?
No. We connected to OmniProvider without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the OmniProvider MCP server still maintained?
OmniProvider is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.