INDIVIDUAL MCP TOOL

forge_get_package

Fetch the full trust profile for a package: Forge verification status, revocation, publisher identity, cached full scan results (tarball obfuscation, provenance, transitive deps, prompt injection), and (optionally) a live CVE scan via OSV plus npm lifecycle-script analysis.

forgeregistry.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://forgeregistry.com/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for forge_get_package and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

A tool name or description suggests retrieving external content.

Parent server

forgeregistry.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.forge]
url = "https://forgeregistry.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "forge": {
      "type": "http",
      "url": "https://forgeregistry.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: forge
Remote MCP URL: https://forgeregistry.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "forge": {
      "url": "https://forgeregistry.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "forge": {
      "type": "http",
      "url": "https://forgeregistry.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "forge",
  "transport": "streamable-http",
  "url": "https://forgeregistry.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

forge_search — Find MCP servers, A2A agents, and AI skills in the Forge trust registry.
forge_alternatives — Find MCP servers that could REPLACE a given entry — other servers observed to expose the same tools, ranked so a better-trusted one surfaces first.
forge_get_skill — Fetch an AI skill from the Forge registry: full prompt text, metadata, compatible clients, and version.
forge_inspect — Statically extract the MCP tool names a package declares, from its npm tarball source — the package is NEVER executed.
forge_install_plan — Get everything needed to install one registry entry in ONE call: ready-to-paste client config for each supported client, the credentials it will ask for (as placeholders), the trust score, and every warning that bears on installing it.
forge_submit_package — Point the Forge registry at an MCP server, A2A agent, or skill that isn't indexed yet.
forge_changes — Ask the Forge registry what has CHANGED for a list of packages since a given date: new npm maintainers, a new install script, obfuscated code that was not there before, a tool surface that grew a privileged capability, newly-applicable CVEs, lost build provenance, or a revoked publisher.