io.github.warpmetrics/mcp

MCPattested
v0.1.0io.github.warpmetricsUnknownUpdated 7mo agonpmGitHub

Connect AI assistants to Warpmetrics — query runs, calls, costs, and outcomes.

Connect AI assistants to your Warpmetrics AI agent telemetry via the Model Context Protocol. Create an API key at warpmetrics.com/app/api-keys The Warpmetrics tools will now be available. Tools are loaded dynamically from the Warpmetrics API and stay automatically in sync. View all available tools: Documentation: warpmetrics.com/docs/mcp "How many runs did I have today?" "Show me the most…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
7mo agoLast update
Package
Authorio.github.warpmetrics
LicenseUnknown
Version0.1.0
Sourcemcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · a7128f9
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface—
Security scan✓ Cleanv0.1.0 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 2 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Connect AI assistants to your Warpmetrics AI agent telemetry via the Model Context Protocol. Create an API key at warpmetrics.com/app/api-keys The Warpmetrics tools will now be available. Tools are loaded dynamically from the Warpmetrics API and stay automatically in sync. View all available tools: Documentation: warpmetrics.com/docs/mcp "How many runs did I have today?" "Show me the most expensive calls" "List recent failed runs" "Show details for run wmrun01abc123" "What's my total LLM spend…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.