io.github.MetriLLM/metrillm
NPM · METRILLM-MCP · SCANNED SEP 20
Benchmark local LLM models — speed, quality & hardware fitness verdict from any MCP client
Available components
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 Security98
- 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
- 40 of 137 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to MetriLLM/metrillm). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 187 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 373 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 Management90
- Stability observed for 27 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 4 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
How do I install the io.github.MetriLLM/metrillm MCP server?
io.github.MetriLLM/metrillm runs locally as an npm package, launched with npx -y metrillm-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 · metrillm-mcp
claude mcp add metrillm-metrillm -- npx -y metrillm-mcp
{
"mcpServers": {
"metrillm-metrillm": {
"command": "npx",
"args": [
"-y",
"metrillm-mcp"
]
}
}
} {
"servers": {
"metrillm-metrillm": {
"command": "npx",
"args": [
"-y",
"metrillm-mcp"
]
}
}
} codex mcp add metrillm-metrillm -- npx -y metrillm-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"metrillm-metrillm": {
"type": "local",
"command": [
"npx",
"-y",
"metrillm-mcp"
],
"enabled": true
}
}
} openclaw mcp add metrillm-metrillm --command npx --arg -y --arg metrillm-mcp
mcp_servers:
metrillm-metrillm:
command: "npx"
args: ["-y", "metrillm-mcp"] {
"McpServers": {
"metrillm-metrillm": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"metrillm-mcp"
]
}
}
} assistant mcp add metrillm-metrillm -t stdio -c npx -a -y metrillm-mcp
{
"mcpServers": {
"metrillm-metrillm": {
"command": "npx",
"args": [
"-y",
"metrillm-mcp"
]
}
}
} 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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
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 · Analysed npm/metrillm-mcp@0.2.6
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | MetriLLM/metrillm |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/MetriLLM/metrillm/.github/workflows/release.yml@refs/tags/v0.2.6 |
| Rekor log index | 1109821839 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:22d38759c6bb5219279d56f1f5a8814881fad840d166304464329fe77ded592d22fa1532125c2c53ed4fa4898364573c3a2878a683010445e1cddfa8b |
Background: How many MCP packages publish verified provenance →
Dependencies 137 packages
| Packages resolved | 137 |
|---|---|
| Stale | 40 |
| 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 →
get_results ~70
Retrieve previously saved benchmark results from ~/.metrillm/results/. Optionally filter by model name. Returns an array of full benchmark result objects.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | Filter results by model name (substring match) |
| runtime | string | – | Inference runtime to use (ollama | lm-studio). |
No output schema declared.
No examples provided.
list_models ~60
List all LLM models available locally on the inference runtime (e.g. Ollama). Returns model name, size, parameter count, quantization, and family.
| Name | Type | Req | Description |
|---|---|---|---|
| runtime | string | – | Inference runtime to use (ollama | lm-studio). |
No output schema declared.
No examples provided.
run_benchmark ~150
Run an MetriLLM benchmark on a local model. Measures performance (tokens/s, TTFT, memory) and optionally quality (reasoning, math, coding, instruction following, structured output, multilingual). Returns a detailed fitness verdict. Warning: benchmarks take 30s to 5+ minutes depending on model size.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | Model name to benchmark (e.g. 'llama3.2:3b', 'qwen2.5:7b') |
| perfOnly | boolean | – | If true, skip quality benchmarks and only measure speed/memory/TTFT |
| runtime | string | – | Inference runtime to use (ollama | lm-studio). |
No output schema declared.
No examples provided.
share_result ~93
Upload a benchmark result to the public MetriLLM leaderboard. Uses official upload defaults; METRILLM_* environment variables can override for self-hosted deployments. The resultFile must be an absolute path to a JSON file in ~/.metrillm/results/.
| Name | Type | Req | Description |
|---|---|---|---|
| resultFile | string | yes | Absolute path to a benchmark result JSON file (from ~/.metrillm/results/). Must be inside ~/.metrillm/results/. |
No output schema declared.
No examples provided.
What is the io.github.MetriLLM/metrillm MCP server?
io.github.MetriLLM/metrillm is an MCP server listed in the public MCP registry as io.github.MetriLLM/metrillm. Benchmark local LLM models, speed, quality & hardware fitness verdict from any MCP client. This page covers its npm package (metrillm-mcp).
Is the io.github.MetriLLM/metrillm MCP server safe to use?
io.github.MetriLLM/metrillm scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.MetriLLM/metrillm MCP server expose?
io.github.MetriLLM/metrillm exposes 4 tools: list_models, run_benchmark, get_results, share_result. Their descriptions and schemas cost roughly 373 tokens of context every time the server is loaded.
Is the io.github.MetriLLM/metrillm MCP server still maintained?
io.github.MetriLLM/metrillm 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.
What licence is the io.github.MetriLLM/metrillm MCP server under?
io.github.MetriLLM/metrillm declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.