AI API Radar
REMOTE · AIAPI.DROPWATCHHQ.COM · SCANNED SEP 20
Live LLM API price + status radar across 11 providers, with public per-model price HISTORY.
Available components
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 4 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 391 tokens (~97/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the AI API Radar MCP server?
AI API Radar is a hosted endpoint at https://aiapi.dropwatchhq.com/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 · aiapi.dropwatchhq.com
claude mcp add --transport http com-dropwatchhq-ai-api-radar 'https://aiapi.dropwatchhq.com/mcp'
{
"mcpServers": {
"com-dropwatchhq-ai-api-radar": {
"url": "https://aiapi.dropwatchhq.com/mcp"
}
}
} {
"servers": {
"com-dropwatchhq-ai-api-radar": {
"type": "http",
"url": "https://aiapi.dropwatchhq.com/mcp"
}
}
} [mcp_servers.com-dropwatchhq-ai-api-radar] url = "https://aiapi.dropwatchhq.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-dropwatchhq-ai-api-radar": {
"type": "remote",
"url": "https://aiapi.dropwatchhq.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-dropwatchhq-ai-api-radar --url 'https://aiapi.dropwatchhq.com/mcp' --transport streamable-http
mcp_servers:
com-dropwatchhq-ai-api-radar:
url: "https://aiapi.dropwatchhq.com/mcp" {
"McpServers": {
"com-dropwatchhq-ai-api-radar": {
"Transport": "http",
"Url": "https://aiapi.dropwatchhq.com/mcp"
}
}
} assistant mcp add com-dropwatchhq-ai-api-radar -t streamable-http -u 'https://aiapi.dropwatchhq.com/mcp'
{
"mcpServers": {
"com-dropwatchhq-ai-api-radar": {
"type": "http",
"url": "https://aiapi.dropwatchhq.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
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 20 Sept 2026 · Probed https://aiapi.dropwatchhq.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dropwatchhq.com | CN=WE1,O=Google Trust Services,C=US | 20 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | f43514669787762213b44cf2ce3767da |
| SANs: dropwatchhq.com, aiapi.dropwatchhq.com, *.aiapi.dropwatchhq.com | ||||||
| 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 aiapi.dropwatchhq.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| dropwatchhq.com. | 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://aiapi.dropwatchhq.com/mcp | Verified | 200 | |
| http (plaintext) | http://aiapi.dropwatchhq.com/mcp | Served over HTTP | 200 |
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 →
cheapest_model ~179
Return the cheapest LLM API models that meet a constraint, ranked by blended $/M-token cost. Use this to route an agent to the lowest-cost model with enough context that is currently operational. Filter by minimum context window and provider; weight input vs output cost for your workload.
| Name | Type | Req | Description |
|---|---|---|---|
| in_weight | number | – | Relative weight of input-token price (default 1). |
| limit | number | – | How many to return (default 10). |
| min_context | number | – | Minimum context window (tokens), e.g. 128000. |
| operational_only | boolean | – | Drop providers with a major/critical status indicator. |
| out_weight | number | – | Relative weight of output-token price (default 3, output-heavy). |
| provider | string | – | Restrict to one provider slug (openai, anthropic, google, ...). |
No output schema declared.
No examples provided.
price_change_alerts ~98
Subscribe a webhook to fire when a provider changes prices (or read recent price changes). Pass `webhook` to subscribe (optionally filter by provider and direction 'cut'|'raise'); omit to read recent changes.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | – |
| limit | number | – | – |
| provider | string | – | – |
| webhook | string | – | HTTPS URL to POST price-change events to. Omit to just read recent changes. |
No output schema declared.
No examples provided.
price_history ~74
Return the dated $/M-token price history (input + output) for one model. This is AI API Radar's exclusive time-series — useful for spotting price-war cuts and trend.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | Model slug, e.g. 'anthropic--claude-opus-4-x' or just the id. |
No output schema declared.
No examples provided.
status ~40
Current operational status for one or all AI API providers (from each provider's public status page).
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | – | Provider slug; omit for all providers. |
No output schema declared.
No examples provided.
What is the AI API Radar MCP server?
AI API Radar is an MCP server listed in the public MCP registry as com.dropwatchhq/ai-api-radar. Live LLM API price + status radar across 11 providers, with public per-model price HISTORY. This page covers its hosted endpoint (https://aiapi.dropwatchhq.com/mcp).
Is the AI API Radar MCP server safe to use?
AI API Radar scores 71 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 AI API Radar MCP server expose?
AI API Radar exposes 4 tools: cheapest_model, price_history, status, price_change_alerts. Their descriptions and schemas cost roughly 391 tokens of context every time the server is loaded.
Does the AI API Radar MCP server require authentication?
No. We connected to AI API Radar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AI API Radar MCP server still maintained?
AI API Radar is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.