mcp-registry-spec-sdk

MCPcommunity
v0.4.0Cameron PakMITUpdated 5mo agonpmGitHub

A minimal, typed client for the official Model Context Protocol (MCP) Registry API.

A minimal, typed client for the official Model Context Protocol (MCP) Registry API. - npm: npm install mcp-registry-spec-sdk - pnpm: pnpm add mcp-registry-spec-sdk - yarn: yarn add mcp-registry-spec-sdk Requires Node.js 18+. API Versions: - v0.1 (default): Stable version, only additive backward-compatible changes - v0: Development version, may evolve with breaking changes The client is namespaced…

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.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5mo agoLast update
Package
AuthorCameron Pak
LicenseMIT
Version0.4.0
Sourcenpm
npmmcp-registry-spec-sdk
GitHubcameronapak/mcp-registry-sdk
SBOMCycloneDX 1.6 ↓
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✓ 1 resolved · none vulnerable
Tool surface—
Security scan✓ Cleanv0.4.0 · 1mo agoHow well does this scan work?
EvalsNone
IndexedMay 24, 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 source1mo 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

A minimal, typed client for the official Model Context Protocol (MCP) Registry API. - npm: npm install mcp-registry-spec-sdk - pnpm: pnpm add mcp-registry-spec-sdk - yarn: yarn add mcp-registry-spec-sdk Requires Node.js 18+. API Versions: - v0.1 (default): Stable version, only additive backward-compatible changes - v0: Development version, may evolve with breaking changes The client is namespaced by feature: - auth — Token exchange helpers - health — Health check - ping — Connectivity check

Keywords
mcpmodelcontextprotocolregistrysdkaianthropic
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.