Announcing Beacon: Self-improving memory for coding agents
← All MCP servers
MCP server

LLM Usage

mcp:zhaoyue722/llm-usage-mcp

Local-first, multi-provider tool that captures LLM API spend and exposes it to coding agents via MCP

Verdict
No issues found

Nothing found that works against the person who installs it.

Analyzed Oct 29, 2026, 00:13 UTC at 96d17cc

Dispute security verdict

If you believe this verdict is incorrect, submit a dispute and we'll review it.

0
findings
—
highest severity
0
threat classes
127
files scanned
1,622/1,622
checks satisfied
0
package advisories

Why this verdict

  • benign: 1622 checks satisfied, nothing works against the installer of mcp-server:. (2 notes, 0 third-party flags)

Security findings 0

No security findings

Nothing found that works against the person who installs it.

Notes 2

Capabilities, vulnerabilities and disclosed behavior worth knowing. Nothing here works against the person who installs it, so notes never change the verdict.

Data exfiltration

mediumNoteConfirmed on reviewmedium confidence

The capture proxy is a local reverse proxy that the user deliberately points their coding agent at, so the user's model API traffic passes through it to the provider the user configured.

ANTHROPIC_BASE_URL=http://127.0.0.1:5525
Reviewer's reasoning

The proxy is a loopback-only server that the user deliberately points their agent at via a documented base URL, and it forwards to the provider the user configured. The docstring instructs the user to set this variable, which is an instruction addressed to the user for a declared core capability, so it is a note.

Credential access

mediumNoteConfirmed on reviewmedium confidence

The MCP server's Settings class reads provider API keys from the process environment and a local .env file to call the wrapped provider APIs, which is the declared purpose and is disclosed in code.

env_file=".env",
vector:code
Reviewer's reasoning

Settings reads the wrapped provider's API keys from the environment and a local .env file, which is the declared purpose for calling those provider APIs and is documented in code. Reading the user's own API key for the wrapped service is a note, not a concealed or redirected credential path.