MCP.Market

mcp-usage MCP server

by Rixtayz·io.github.Rixtayz/mcp-usage·v0.1.1
No reviews yet

Find out which MCP servers you actually use: local, read-only audit of Claude Code transcripts.

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed mcp-usage yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

mcp-usage tools (4)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • recommendations

    Prioritized actions: disconnect unused servers, fix or remove failing ones, authorize or remove pending ones, investigate high error rates, watch heavy results. …

  • server_details

    Full stats for one MCP server, including per-tool calls, errors and result size. …

  • unused_servers

    MCP servers that were connected but never called, failed to connect, or are waiting for authorization. …

  • usage_summary

    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. …

Public scan report

scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it

no findings
  • Code scan31 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How mcp-usage compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
Tools
4
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 4 read

Install mcp-usage in Claude Code, Cursor or VS Code

Runs npx -y @rixtay/mcp-usage on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-usage -- npx -y @rixtay/mcp-usage
Add to Cursor

What the publisher says

From the mcp-usage repository's README, as published. We do not edit it. Read it on GitHub

mcp-usage

A small, focused MCP server and CLI that reads your local Claude Code transcripts and tells you, for every MCP server you have connected, whether it is actually used, sits idle in every session, fails to connect, or has been waiting for authorization for weeks — and what to disconnect.

Built for one job: answer "which of my MCP servers should I keep?" — locally, read-only, without ever exposing a word of your conversations.

Tools

Four tools, all read-only:

Design choices:

  • Exact, not guessed. Claude Code already records, in every session, which MCP tools were available and which servers failed or needed auth. "Available but never used" is a set difference over your own logs, not a heuristic.
  • Private by construction. No network code at all. The output holds server names, tool names, counts, byte totals and timestamps — never prompts, responses, tool inputs, tool outputs, file paths or error messages. The test fixtures plant SECRET_* markers everywhere private content lives in a real transcript, and the tests assert none of them reach the library, the CLI or the MCP output.
  • Fast on big histories. Transcripts are streamed line by line and lines that cannot matter are skipped before JSON.parse: ~360 MB of history (including a 90 MB session) scans in about 3 seconds.
  • Hygiene, not billing. Cost analyzers (ccusage, agent-cost-mcp, …) tell you how many tokens and dollars you spent. This tells you which servers earn their place.
  • Every tool ships a strict input schema and MCP annotations (readOnlyHint, idempotentHint) so hosts can auto-approve them.

Requirements

  • Node.js 22 or newer.
  • Claude Code (CLI, desktop app or IDE extension) with some session history on this machine. Nothing else: no account, no API key, no configuration.

1. Run the report

No install needed, npx fetches the package from npm (@rixtay/mcp-usage, the installed command is mcp-usage):

npx -y @rixtay/mcp-usage

Or from a clone:

git clone https://github.com/Rixtayz/mcp-usage.git
cd mcp-usage
npm install && npm run build
node dist/bin/cli.js

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

mcp-usage: common questions

Is mcp-usage MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the mcp-usage safety report
How do I install mcp-usage?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does mcp-usage need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is mcp-usage maintained?
The last commit was 35 days ago (2026-09-30). The latest release is v0.1.1.
What can I use instead of mcp-usage?
Servers from other publishers that do the same job: QVeris MCP server.
How does mcp-usage compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to mcp-usage

Same job from other publishers: the closest match first, then the best rated.

  • QVeris
    Professional data and tools for AI: find services, review scope, call them, and audit usage.
    A