@forge-registry/cli

MCP@jokin-bereciartu
v0.2.0jokin-bereciartuMITUpdated 3mo agonpmGitHub

Verify, install, and publish MCP servers, A2A agents, and AI skills via the Forge trust registry.

Verify, install, and publish MCP servers, A2A agents, and AI skills. Checks a package before you install it: Forge registry — is it listed? verified? who published it? OSV scan — known CVEs for the exact version from the OSV database Script analysis — lifecycle scripts (, , etc.) checked for suspicious patterns ------|-------------| | Output raw JSON (useful for scripting) | Exit codes: =…

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.

@jokin-bereciartu
Identity-verified publisher GitHub@jokin-bereciartu
Verified Jun 13, 2026
3mo agoLast update
Package
Authorjokin-bereciartu
LicenseMIT
Version0.2.0
Sourcenpm
npm@forge-registry/cli
GitHubforgeregistry/website
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Publisher identity verified+20/20
✓Ed25519 publish signature+5/5
—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
→ 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
Publisher@jokin-bereciartu
Signature✓ Signed · Ed25519
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface8 tools · none privileged
Security scan✓ Cleanv0.3.1 · 1mo 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

8 tools · none privileged
Statically extracted from the published packagev0.3.1 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

forge_searchFind MCP servers, A2A agents, and AI skills in the Forge trust registry.

Find MCP servers, A2A agents, and AI skills in the Forge trust registry.

No input schema was published for this tool.

forge_get_packageFetch the full trust profile for a package: Forge verification status, revocation,

Fetch the full trust profile for a package: Forge verification status, revocation,

No input schema was published for this tool.

forge_auditAudit every MCP server configured in a project (.mcp.json, .cursor/mcp.json,

Audit every MCP server configured in a project (.mcp.json, .cursor/mcp.json,

No input schema was published for this tool.

forge_get_skillFetch an AI skill from the Forge registry: full prompt text, metadata,

Fetch an AI skill from the Forge registry: full prompt text, metadata,

No input schema was published for this tool.

forge_add_skillInstall an AI skill from the Forge registry into the project's client config.

Install an AI skill from the Forge registry into the project's client config.

No input schema was published for this tool.

forge_inspectStatically extract the MCP tool names a package declares, from its npm

Statically extract the MCP tool names a package declares, from its npm

No input schema was published for this tool.

forge_submit_packagePoint the Forge registry at an MCP server, A2A agent, or skill that isn't

Point the Forge registry at an MCP server, A2A agent, or skill that isn't

No input schema was published for this tool.

forge_publishRegister or claim a package in the Forge public registry.

Register or claim a package in the Forge public registry.

No input schema was published for this tool.

8 of 8 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Verify, install, and publish MCP servers, A2A agents, and AI skills. Checks a package before you install it: Forge registry — is it listed? verified? who published it? OSV scan — known CVEs for the exact version from the OSV database Script analysis — lifecycle scripts (, , etc.) checked for suspicious patterns ------|-------------| | Output raw JSON (useful for scripting) | Exit codes: = clean/verified, = critical vulnerabilities found Trust-aware wrapper around : 2. Blocks on critical/high…

Keywords
forgemcpa2acliai-toolssecurityverify
Alternatives
Comparing tool surfaces…

Tools exposed

8 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

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

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

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

62 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+50 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in security