AI Stupid Level
NPM · @AISTUPIDLEVEL/MCP
LLM benchmark rankings, drift status, incidents and Smart Router previews from AI Stupid Level.
Available components
Last scanned (9 hours ago)
Scores higher than 45% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 4.6.5, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
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 15 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1968 tokens (~178/item across 11 items; 11 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 Management53
- Stability observed for 16 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +4
- Stability: unverified → 0.30 ▲ functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 20 Oct 26 45
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 5 Nov 2026 · Analysed npm/@aistupidlevel/mcp@0.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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
ask_router Ask via Smart Router ~336
Send a prompt through the AI Stupid Level Smart Router and return the answer, together with which model answered, its provider, why the router chose it and the latency. The router calls the model with the provider keys saved in the user's ASL account, so a real call is billed by that provider and counts against the router plan; set sandbox: true for a free mock answer. Needs a router key (ASL_ROUTER_KEY).
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | integer | – | Upper bound on the answer length in tokens. |
| mode | string | – | Routing mode (default auto = the strategy saved in the account): auto-best (highest combined score), auto-coding, auto-reasoning, auto-tooling (top model on that benchmark), auto-task (reads the prom… |
| pin_model | string | – | Pin a specific model id (for example gpt-6-sol) instead of a routing mode. |
| prompt | string | yes | The user message to send. |
| reasoning_effort | string | – | Reasoning effort for models that support it. |
| sandbox | boolean | – | Sandbox: run the real routing as if the account had a key for every provider and return a mock answer. Nothing is called, spent or counted. |
| system | string | – | An optional system message. |
No output schema declared.
No examples provided.
get_drift_status Model drift status ~134
Whether an LLM's measured performance has shifted: AI Stupid Level's drift signature for one model, with its regime (stable, degrading, …), current score against its baseline, the change-point detector per benchmark suite, the last significant change and which axes moved. Use it to answer "has model X got worse?" or "is X being nerfed?".
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | The model: its numeric id, its name (for example claude-opus-5-5 or gpt-6-sol) or its display name. get_leaderboard lists the tracked models with their ids. |
No output schema declared.
No examples provided.
get_global_index Global AI index ~60
AI Stupid Level's global index: one 0-100 number for the tracked models together, now and over the last 24 hours, with its trend and how many models are performing well. Use it for "are AI models worse today?".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_incidents Recent incidents ~109
Recent incidents AI Stupid Level recorded: provider-wide degradations and model-level problems, with severity, the models affected, when each was detected and whether and when it was resolved.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many incidents to show, newest first (default 10). |
| open_only | boolean | – | Only incidents that are not resolved yet (default false). |
| provider | string | – | Only incidents for this provider: openai, anthropic, google, deepseek, kimi or glm. |
No output schema declared.
No examples provided.
get_leaderboard LLM leaderboard ~247
Ranking of the LLM APIs AI Stupid Level tracks (OpenAI, Anthropic, Google, DeepSeek, Kimi, GLM models) by benchmark score, 0-100. Use it to find the best model overall or for coding, reasoning or tool use, to compare models, and to get the model ids the other tools accept. Each row has the score, trend, status, stability and when it was last updated.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many models to show (default 10). |
| period | string | – | Score window: 24h, 7d or 1m (30-day) averages, or latest (the newest run). Omit it to use the key's default: 24h on a free Data API key, latest on a paid one. latest needs a paid key. |
| sort_by | string | – | Which ranking: combined (default, all suites), coding, reasoning, tooling (tool use / agentic tasks), or price (score per list-price dollar). |
| vendor | string | – | Only show models from this vendor: openai, anthropic, google, deepseek, kimi or glm. |
No output schema declared.
No examples provided.
get_model Model details ~105
Details AI Stupid Level holds on one tracked LLM: vendor, version, notes on how it is called and priced, tool-calling support, how long it has been tracked, and its leaderboard row when one has been fetched.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | The model: its numeric id, its name (for example claude-opus-5-5 or gpt-6-sol) or its display name. get_leaderboard lists the tracked models with their ids. |
No output schema declared.
No examples provided.
get_model_history Model score history ~206
Score history of one LLM on AI Stupid Level: each benchmark run in the window with its score, plus the newest run's per-axis results (correctness, code quality, efficiency, …). Use it to see whether a model got better or worse over time.
| Name | Type | Req | Description |
|---|---|---|---|
| max_points | integer | – | How many runs to list, newest first (default 30). The summary always covers every run. |
| model | string | yes | The model: its numeric id, its name (for example claude-opus-5-5 or gpt-6-sol) or its display name. get_leaderboard lists the tracked models with their ids. |
| period | string | – | Score window: 24h, 7d or 1m (30-day) averages, or latest (the newest run). Omit it to use the key's default: 24h on a free Data API key, latest on a paid one. latest needs a paid key. |
No output schema declared.
No examples provided.
get_provider_status Provider status ~71
Current status of each LLM provider's API as AI Stupid Level's health probes see it (OpenAI, Anthropic, Google, DeepSeek, Kimi, GLM): operational or not, probe response time, the last error and when it was checked. For past outages use get_incidents.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_recommendations Model recommendations ~157
AI Stupid Level's current picks: the best model for coding, the most reliable (steadiest score), the fastest, the best value (most points per measured dollar among near-top models), models that cost far more than an equally good alternative, and models to avoid right now. Each pick comes with the reason and the evidence it rests on. Use it for "which model should I use?".
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | Score window: 24h, 7d or 1m (30-day) averages, or latest (the newest run). Omit it to use the key's default: 24h on a free Data API key, latest on a paid one. latest needs a paid key. |
No output schema declared.
No examples provided.
get_usage ASL usage and limits ~61
This month's Smart Router usage for the configured router key (requests used and left, prepaid credits, the key's budget), and the Data API requests left today for the configured data key. Use it when a tool reports a limit, or to check the keys work.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
preview_route Preview Smart Router choice ~289
Which model the AI Stupid Level Smart Router would send a prompt to, and why: the routing strategy, the chosen model and provider with its benchmark score and estimated cost, and the fallback chain. Nothing is sent to a model and nothing is counted. Needs a router key (ASL_ROUTER_KEY).
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | Routing mode (default auto = the strategy saved in the account): auto-best (highest combined score), auto-coding, auto-reasoning, auto-tooling (top model on that benchmark), auto-task (reads the prom… |
| pin_model | string | – | Pin a specific model id (for example gpt-6-sol) instead of a routing mode. |
| prompt | string | yes | The prompt to route (the decision can depend on it, for example with auto-task). |
| sandbox | boolean | – | Sandbox: run the real routing as if the account had a key for every provider and return a mock answer. Nothing is called, spent or counted. |
| system | string | – | An optional system message. |
No output schema declared.
No examples provided.
How do I install the AI Stupid Level MCP server?
AI Stupid Level runs locally as an npm package, launched with npx -y @aistupidlevel/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 · @aistupidlevel/mcp
claude mcp add studioplatforms-aistupidlevel -- npx -y @aistupidlevel/mcp
What is the AI Stupid Level MCP server?
AI Stupid Level is an MCP server listed in the public MCP registry as io.github.StudioPlatforms/aistupidlevel. LLM benchmark rankings, drift status, incidents and Smart Router previews from AI Stupid Level. This page covers its npm package (@aistupidlevel/mcp).
Is the AI Stupid Level MCP server safe to use?
AI Stupid Level scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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 Stupid Level MCP server expose?
AI Stupid Level exposes 11 tools: get_leaderboard, get_model, get_model_history, get_drift_status, get_incidents, and 6 more. Their descriptions and schemas cost roughly 1,775 tokens of context every time the server is loaded.
Is the AI Stupid Level MCP server still maintained?
AI Stupid Level 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.
What licence is the AI Stupid Level MCP server under?
AI Stupid Level declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.