Loading the registry…
Local-first, multi-provider tool that captures LLM API spend and exposes it to coding agents via MCP
The publisher performed an authenticated act of publication — proving control of a namespace in the official MCP registry, or appearing in a first-party catalogue an operator curates. That establishes WHO published it. It is not a security finding, and attested artifacts carry Flagged verdicts too.
github: https://github.com/zhaoyue722/llm-usage-mcp, 65 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- llm-usage-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
12 findings · 11.9s
v0.3.74
7 findings · 11.8s
v0.1.0
0 findings · 3.6s
v0.1.0
0 findings · 3.6s
v0.71.0
23 findings · 0.4s
v2.3.8
23 findings · 1.7s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.9s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
3 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Sep 2, 2026 | Flagged43 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
| Aug 8, 2026 | Flagged46 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
| Aug 3, 2026 | Flagged46 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 65 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 7 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
4 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/docs/SKILL.md, /repo/examples/SKILL.md · reported by cisco-skill-scanner
3 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/ci.yml, .github/workflows/refresh-pricing.yml, .github/workflows/release.yml · reported by agent-audit-kit
The model could have called any of these a false positive and did not.
2 AAK-MCP-SDK-CVE-2026-52869-001
Files: pyproject.toml, uv.lock · reported by agent-audit-kit
2 GHSA-4xgf-cpjx-pc3j
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-537c-gmf6-5ccf
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
1 AAK-MCP-NOAUTH-DEFAULT
Files: src/llm_usage/capture/proxy.py · reported by agent-audit-kit
1 CVE-2026-45409
Files: uv.lock · reported by trivy
1 CVE-2026-48522
Files: uv.lock · reported by trivy
1 CVE-2026-48523
5 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: TOOL_ABUSE_UNDECLARED_NETWORK, AAK-SEC-MD-001, MANIFEST_MISSING_LICENSE and 1 more · Files: /repo/repo/CHANGELOG.md, SECURITY.md, /repo/SKILL.md and 1 more · reported by cisco-skill-scanner, agent-audit-kit
2 The model did not answer for these findings.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION · Files: /repo/SKILL.md, /repo/src/llm_usage/core/pricing_data/SKILL.md · reported by cisco-skill-scanner
Artifact contains high-severity vulnerabilities and an unauthenticated proxy.
The artifact includes an unauthenticated proxy in `src/llm_usage/capture/proxy.py`, which could allow unauthorized access. Numerous high-severity vulnerabilities are present in dependencies listed in `uv.lock` and `pyproject.toml`, including issues like CVE-2026-52869 and GHSA-537c-gmf6-5ccf. These vulnerabilities could lead to various impacts depending on the specific flaw, such as remote code execution or information disclosure.
Concern level assessed by the review: High. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
1 CVE-2026-48524
Files: uv.lock · reported by trivy
1 CVE-2026-48525
Files: uv.lock · reported by trivy
1 CVE-2026-48526
Files: uv.lock · reported by trivy
1 CVE-2026-48710
Files: uv.lock · reported by trivy
1 CVE-2026-48817
Files: uv.lock · reported by trivy
1 CVE-2026-48818
Files: uv.lock · reported by trivy
1 CVE-2026-52869
Files: uv.lock · reported by trivy
1 CVE-2026-52870
Files: uv.lock · reported by trivy
1 CVE-2026-53537
Files: uv.lock · reported by trivy
1 CVE-2026-53538
Files: uv.lock · reported by trivy
1 CVE-2026-53539
Files: uv.lock · reported by trivy
1 CVE-2026-53540
Files: uv.lock · reported by trivy
1 CVE-2026-54282
Files: uv.lock · reported by trivy
1 CVE-2026-54283
Files: uv.lock · reported by trivy
1 CVE-2026-59950
Files: uv.lock · reported by trivy
1 CVE-2026-69247
Files: uv.lock · reported by trivy
1 CVE-2026-69248
Files: uv.lock · reported by trivy
1 CVE-2026-69249
Files: uv.lock · reported by trivy
1 DATA_EXFIL_SOCKET_CONNECT
Files: /repo/src/llm_usage/core/diagnostics.py · reported by cisco-skill-scanner
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 GHSA-jq35-7prp-9v3f
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-161
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-175
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-177
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-178
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-179
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2280
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2281
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-248
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-249
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3036
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3037
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3040
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3041
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3481
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3482
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3483
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3552
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3553
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3554
Files: /repo/uv.lock · reported by osv-scanner