@agentage/catalog-mcp

MCPcommunitylive
v0.0.2UnknownMITUpdated 2mo agonpmGitHub

The npm client for the agentage MCP catalog: a thin stdio MCP proxy that bridges stdio-only clients (Claude Desktop, Cursor, VS Code) to the public catalog.agentage.io/mcp endpoint - search 14k+ MCP servers from any MCP client.

Endpoint healthlive
checked 4 days ago · 536ms
100% of the last 4 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

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

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
232Downloads/wk
2mo agoLast update
Package
AuthorUnknown
LicenseMIT
Version0.0.2
Sourcenpm+mcp-registry
Trust Status
F
10/100Untrusted
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
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)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · not run+0/30
Our scan didn't complete — a retry is queued. Nothing to fix on your side.
Static analysis · clean+0/20
Our scan didn't complete — a retry is queued. Nothing to fix on your side.
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
DependenciesNot audited
Tool surface
Security scanScan failedvunknown · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 15, 2026

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

Tools

Source never read1mo ago

This entry has been scanned, but the run carries no source-extraction result — either it predates tool-surface extraction or it failed before reaching that stage. A rescan is what would fill this in; the blank says nothing about the package.

About

The npm client for the agentage MCP catalog: a thin stdio MCP proxy that bridges stdio-only clients (Claude Desktop, Cursor, VS Code) to the public catalog.agentage.io/mcp endpoint - search 14k+ MCP servers from any MCP client.

Keywords
mcpmcp-servermodel-context-protocolmcp-catalogmcp-registryclaudecursoragentage
Alternatives
Comparing tool surfaces…

No dependency coverage

The last scan of this package failed, so no dependency tree was resolved.