Submit your MCP server
Submit an existing npm/PyPI MCP server for automated checks and catalog listing. AgentNode verifies the package and ownership signals automatically — independently re-checking your package against the registry. Today, MCP listings still get a review before going live; the long-term goal is self-service publishing once all automated gates pass.
Paste the JSON output of agentnode mcp verify . --test --json. Without it, your submission is filed as an unverified draft (REVIEW_NEEDED) — the review team will usually ask for a CLI-verified (TESTED) report before an approved server can be published.
Prefer the CLI? agentnode mcp verify . → agentnode mcp submit . → agentnode mcp status <id> — see the CLI reference.
Prove ownership via publish-challenge
Prove you control the npm/PyPI package behind your MCP server. Issue a one-time challenge, then add the keyword to your package metadata, publish a new version, and verify. Only someone with publish rights can do that.
Ownership can be verified, but MCP listings still remain review-gated until the sandbox-smoke gate is built.
Prefer the CLI? agentnode mcp ownership challenge --registry npm <package>
How review works
- You submit the manifest. The server independently re-verifies the package against the npm/PyPI registry (existence, version pinning, repository consistency) — your report is advisory, the server result is authoritative.
- The submission lands as pending or action required. A reviewer checks it; package ownership must be verified before anything can be published.
- You track the status here or via
agentnode mcp status <id>. Feedback from the review team appears on your submission. - Only an approved, ownership-verified submission is published to the catalog.