mcp-usage
NPM · @RIXTAY/MCP-USAGE · SCANNED OCT 4
Find out which MCP servers you actually use: local, read-only audit of Claude Code transcripts.
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
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 382 tokens (~95/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the mcp-usage server?
mcp-usage runs locally as an npm package, launched with npx -y @rixtay/mcp-usage. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rixtay/mcp-usage
claude mcp add rixtayz-mcp-usage -- npx -y @rixtay/mcp-usage
{
"mcpServers": {
"rixtayz-mcp-usage": {
"command": "npx",
"args": [
"-y",
"@rixtay/mcp-usage"
]
}
}
} {
"servers": {
"rixtayz-mcp-usage": {
"command": "npx",
"args": [
"-y",
"@rixtay/mcp-usage"
]
}
}
} codex mcp add rixtayz-mcp-usage -- npx -y @rixtay/mcp-usage
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rixtayz-mcp-usage": {
"type": "local",
"command": [
"npx",
"-y",
"@rixtay/mcp-usage"
],
"enabled": true
}
}
} openclaw mcp add rixtayz-mcp-usage --command npx --arg -y --arg @rixtay/mcp-usage
mcp_servers:
rixtayz-mcp-usage:
command: "npx"
args: ["-y", "@rixtay/mcp-usage"] {
"McpServers": {
"rixtayz-mcp-usage": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@rixtay/mcp-usage"
]
}
}
} assistant mcp add rixtayz-mcp-usage -t stdio -c npx -a -y @rixtay/mcp-usage
{
"mcpServers": {
"rixtayz-mcp-usage": {
"command": "npx",
"args": [
"-y",
"@rixtay/mcp-usage"
]
}
}
} 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.
- 1 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Sept 26 56
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 4 Oct 2026 · Analysed npm/@rixtay/mcp-usage@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 →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| 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 →
recommendations MCP cleanup recommendations ~109
Prioritized actions: disconnect unused servers, fix or remove failing ones, authorize or remove pending ones, investigate high error rates, watch heavy results. Reads local Claude Code transcripts only. Returns server names, tool names, counts and timestamps - never conversation content.
| Name | Type | Req | Description |
|---|---|---|---|
| min_sessions | integer | – | Sessions a server must have been available in before it is flagged as unused (default 5 for recommendations, 1 for unused_servers). |
| since_days | integer | – | Look back this many days (default 30). |
No output schema declared.
No examples provided.
server_details MCP server details ~84
Full stats for one MCP server, including per-tool calls, errors and result size. Reads local Claude Code transcripts only. Returns server names, tool names, counts and timestamps - never conversation content.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | Server id or label as shown by usage_summary (case-insensitive). |
| since_days | integer | – | Look back this many days (default 30). |
No output schema declared.
No examples provided.
unused_servers Unused MCP servers ~100
MCP servers that were connected but never called, failed to connect, or are waiting for authorization. Reads local Claude Code transcripts only. Returns server names, tool names, counts and timestamps - never conversation content.
| Name | Type | Req | Description |
|---|---|---|---|
| min_sessions | integer | – | Sessions a server must have been available in before it is flagged as unused (default 5 for recommendations, 1 for unused_servers). |
| since_days | integer | – | Look back this many days (default 30). |
No output schema declared.
No examples provided.
usage_summary MCP usage summary ~89
Per-server usage of every MCP server seen in recent Claude Code sessions: status (used / unused / failed / needs-auth), tools available, sessions, calls, error rate, estimated result tokens, last use. Reads local Claude Code transcripts only. Returns server names, tool names, counts and timestamps - never conversation content.
| Name | Type | Req | Description |
|---|---|---|---|
| since_days | integer | – | Look back this many days (default 30). |
No output schema declared.
No examples provided.
What is the mcp-usage server?
mcp-usage is listed in the public MCP registry as io.github.Rixtayz/mcp-usage. Find out which MCP servers you actually use: local, read-only audit of Claude Code transcripts. This page covers its npm package (@rixtay/mcp-usage).
Is the mcp-usage server safe to use?
mcp-usage scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 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 mcp-usage server expose?
mcp-usage exposes 4 tools: usage_summary, unused_servers, server_details, recommendations. Their descriptions and schemas cost roughly 382 tokens of context every time the server is loaded.
Is the mcp-usage server still maintained?
mcp-usage is still listed as active in the MCP registry. We last reached this channel on 4 October 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 mcp-usage server under?
mcp-usage declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.