AI Model Status
NPM · AI-MODEL-STATUS-MCP
Live uptime, latency, prices and weekly usage of AI models from public data. No API key.
Available components
Last scanned (14 hours ago)
Scores higher than 46% of npm servers
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 731 tokens (~182/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 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.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Package version: 1.0.0 → 1.1.1 functional
- 11 Nov 26 54
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 21 Nov 2026 · Analysed npm/ai-model-status-mcp@1.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
compare_models Compare models (price, latency, uptime) ~143
Side-by-side comparison of 2-6 AI models on Ezkielyna: list price per 1M input/output tokens in USD with approximate IDR (or price per image/second/request for media models), key group, time to first token p50/p90, output speed, success rate 24 h and uptime 7 d / 30 d. Prices are this one gateway's list prices, not a market survey. Free, no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| models | array | yes | Model ids, e.g. ["deepseek-v4.1-flash", "gpt-6-luna", "claude-haiku-5-5"]. |
No output schema declared.
No examples provided.
lowest_price_models Lowest listed prices on Ezkielyna ~159
Models with the lowest listed price on Ezkielyna for a task: chat, coding (models that also work with Claude Code / Codex / OpenCode style agents), image (price per image) or tts (price per 1M characters). Shows uptime next to each price and by default leaves out models whose 7-day uptime is below 90%. Only covers this one gateway, not a market-wide price comparison. Free, no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| min_uptime_7d | number | – | Leave out models whose known 7-day uptime is below this. Models without status data are kept and marked. |
| task | string | yes | What the model is for. |
| top | integer | – | How many models to list. |
No output schema declared.
No examples provided.
model_status Model status (uptime, latency, speed) ~249
Live status of AI models on Ezkielyna, one independent API gateway: success rate (24 h), uptime (7 d / 30 d), time to first token (p50/p90), output speed and request counts. Give "model" for one model, or leave it empty for the top N sorted by uptime, latency (fastest first token), speed (tokens/s) or requests (busiest). Free, no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Optional family filter as used by the status file: deepseek, gpt, claude, gemini, glm, qwen, kimi, minimax, image, video, audio, other. |
| min_requests_7d | integer | – | For sort_by=uptime: ignore models with fewer answers in 7 days (a 100% uptime from 3 requests means little). |
| model | string | – | Model id, e.g. deepseek-v4.1-flash or claude-sonnet-5.5. Leave empty for a top-N list. |
| sort_by | string | – | Ranking for the top-N list. |
| top | integer | – | How many models to list. |
No output schema declared.
No examples provided.
usage_leaderboard Weekly usage leaderboard ~103
Most-used AI models on Ezkielyna over the last 7 days (requests, share %, tokens, distinct users) and the change versus the week before. Only models used by at least 3 people are ranked. Users are mostly Indonesian developers with coding agents, so this is one gateway's sample, not national market share. Data CC BY 4.0. Free, no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| top | integer | – | How many models to list. |
No output schema declared.
No examples provided.
How do I install the AI Model Status MCP server?
AI Model Status runs locally as an npm package, launched with npx -y ai-model-status-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · ai-model-status-mcp
claude mcp add ezkielynagroup-ai-model-status-mcp -- npx -y ai-model-status-mcp
What is the AI Model Status MCP server?
AI Model Status is an MCP server listed in the public MCP registry as io.github.EzkielynaGroup/ai-model-status-mcp. Live uptime, latency, prices and weekly usage of AI models from public data. No API key. This page covers its npm package (ai-model-status-mcp).
Is the AI Model Status MCP server safe to use?
AI Model Status scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 Model Status MCP server expose?
AI Model Status exposes 4 tools: model_status, compare_models, usage_leaderboard, lowest_price_models. Their descriptions and schemas cost roughly 654 tokens of context every time the server is loaded.
Is the AI Model Status MCP server still maintained?
AI Model Status is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the AI Model Status MCP server under?
AI Model Status declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the AI Model Status MCP server?
VerifyMCP ran 16 checks on AI Model Status, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.