# mcp-usage (npm · @rixtay/mcp-usage)

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

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- npm · `@rixtay/mcp-usage`: 71/100 (this document), [markdown](https://verifymcp.io/servers/rixtayz-mcp-usage/rixtay-mcp-usage.md), [page](https://verifymcp.io/servers/rixtayz-mcp-usage/rixtay-mcp-usage)

## Channel facts

- Registry: `npm`
- Package: `@rixtay/mcp-usage`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 382 tokens (~95/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

## Install

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

### Claude

```bash
claude mcp add rixtayz-mcp-usage -- npx -y @rixtay/mcp-usage
```

### Cursor

```json
{
  "mcpServers": {
    "rixtayz-mcp-usage": {
      "command": "npx",
      "args": [
        "-y",
        "@rixtay/mcp-usage"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "rixtayz-mcp-usage": {
      "command": "npx",
      "args": [
        "-y",
        "@rixtay/mcp-usage"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add rixtayz-mcp-usage -- npx -y @rixtay/mcp-usage
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rixtayz-mcp-usage": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@rixtay/mcp-usage"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add rixtayz-mcp-usage --command npx --arg -y --arg @rixtay/mcp-usage
```

### Hermes

```yaml
mcp_servers:
  rixtayz-mcp-usage:
    command: "npx"
    args: ["-y", "@rixtay/mcp-usage"]
```

### Netclaw

```json
{
  "McpServers": {
    "rixtayz-mcp-usage": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@rixtay/mcp-usage"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add rixtayz-mcp-usage -t stdio -c npx -a -y @rixtay/mcp-usage
```

### Other

```json
{
  "mcpServers": {
    "rixtayz-mcp-usage": {
      "command": "npx",
      "args": [
        "-y",
        "@rixtay/mcp-usage"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-01 (score 71, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-30 (score 56)

First indexed and scored.

## MCP tools (4)

### `usage_summary` (~89 tokens)

MCP 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. Reads local Claude Code transcripts only. Returns server names, tool names, counts and timestamps - never conversation content.

Input parameters:

- `since_days` (integer): Look back this many days (default 30).

### `unused_servers` (~100 tokens)

Unused MCP servers

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.

Input parameters:

- `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).

### `server_details` (~84 tokens)

MCP server details

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.

Input parameters:

- `server` (string, required): Server id or label as shown by usage_summary (case-insensitive).
- `since_days` (integer): Look back this many days (default 30).

### `recommendations` (~109 tokens)

MCP cleanup recommendations

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.

Input parameters:

- `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).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/rixtayz-mcp-usage/rixtay-mcp-usage#diagnostics

## Score history

- 2026-10-04: 71
- 2026-10-03: 71
- 2026-10-02: 71
- 2026-10-01: 71
- 2026-09-30: 56

## Common questions

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

## Links

- npm package: https://www.npmjs.com/package/@rixtay/mcp-usage
- Socket report: https://socket.dev/npm/package/@rixtay/mcp-usage
- Repository: https://github.com/Rixtayz/mcp-usage
- Changelog RSS feed: https://verifymcp.io/servers/rixtayz-mcp-usage/rixtay-mcp-usage.xml
- Changelog JSON feed: https://verifymcp.io/servers/rixtayz-mcp-usage/rixtay-mcp-usage.json
- HTML version of this page: https://verifymcp.io/servers/rixtayz-mcp-usage/rixtay-mcp-usage