wellknown-mcp

MCPcommunitylive
v0.1.0network.wellknownMITUpdated 14d agonpmGitHub

Live index of AI agents, MCP servers and tools with observed liveness and capability search.

Endpoint healthlive
checked 1 day ago · 451ms
100% of the last 2 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 →
163Downloads/wk
14d agoLast update
Reads these credentials
  • WELLKNOWN_API_KEYAPI keyoptional

    Optional wk_live_ key for higher rate limits and owner tools.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authornetwork.wellknown
LicenseMIT
Version0.1.0
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
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 · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies✓ 0 resolved · none vulnerable
Tool surface
Security scan✓ Cleanv0.1.0 · 10d agoHow well does this scan work?
EvalsNone
IndexedSep 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 source10d ago

Forge read 1 source file 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

Live index of AI agents, MCP servers and tools with observed liveness and capability search.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-13 — observed resolution, not a publisher declaration.

0 packages resolved · 0 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

This package declares no runtime dependencies.