Singularity Layer MCP
MCP for Singularity Layer. Discover listings, manage endpoints and products, run payment-backed endpoint flows, consume public product and credit-pack purchase flows, and use wallet-session agent registry tools through authenticated MCP actions.✅ v1.6.0 Phase 4 agent registry tooling shipped on March 22, 2026. PAT-first auth remains live, and MCP now exposes wallet-session agent registration and management in addition to payment flows.
What is MCP?
The Model Context Protocol (MCP) is a standardized protocol for connecting AI assistants to external systems. It provides a unified way for AI models to access tools, resources, and prompts from external services. The Singularity Layer MCP server exposes the broader platform through this protocol, combining marketplace discovery, endpoint and product management, and ERC-8004 agent access in a single MCP surface.Release & Registry Status
The runtime server name remains
singularity-mcp, while the official registry package is io.github.ivaavimusic/singularity.
Endpoint
Quick Install
Cursor IDE
Add to.cursor/mcp.json in your project root:
Claude Desktop
Add to~/Library/Application Support/Claude/claude_desktop_config.json:
Antigravity / Codex CLI
Add to~/.codex/mcp.json (global) or .codex/mcp.json (project):
Windsurf / Other MCP Clients
PAT Authentication
Personal access tokens are now the default account-level credential for MCP. Create them inDashboard -> Settings -> PAT and use accessToken for owner-wide MCP automation. Legacy endpoint keys remain supported for endpoint-scoped flows.
Live validation on March 22, 2026 confirmed that read-only PATs cannot perform writes, endpoint-write PATs cannot mutate products, product-write PATs cannot mutate endpoints, revoked or expired PATs are rejected cleanly, and PAT-backed endpoint top-up challenges now return a valid 402.
Discovery Tools (Phase 1 - No Auth)
Browse and discover marketplace listings, agents, and categories. No authentication required.Management Tools (Phase 2 + 2.5 - PAT First)
Manage your x402 endpoints and products through authenticated MCP tools. UseaccessToken with a scoped sgl_pat_* token for owner-wide automation. Legacy endpoint keys in the x402_* format remain supported where noted.
Phase 3 Payment Tools
MCP can now request payment challenges and complete endpoint creation, endpoint top-up, public product purchase, and public credit-pack purchase flows. Consumer purchase tools wrap the existing public purchase contracts only and do not act as a generic paid endpoint proxy.Security note: PATs and legacy endpoint keys are passed per-request and never stored by the MCP server. Production PATs usesgl_pat_*, production keys usex402_*, legacysk_*keys remain accepted, and older agent-created endpoints without a linked dashboard user stay intentionally constrained to endpoint-only scope. Contract note: product tools only wrap/p/:slug-or-idand credit purchase tools only wrap/e/:slug?action=purchase. Some current credit endpoints still includepurchase_urlandcredit_packagewith an informationalMissing x-wallet-address headerfield because that is the current upstream worker contract.
Phase 4 Agent Registry Tools
MCP now exposes the worker wallet-session flows for ERC-8004 and Solana-8004 agent registration and management.Wallet auth note: MCP does not hold the wallet private key. The wallet signs locally, then MCP exchanges that signature for a short-lived session token. On-chain registration and URI updates still require normal chain gas from the same wallet. Validation note: production validation on March 22, 2026 covered wallet challenge creation, wallet verification, owned endpoint discovery, owned agent discovery, and EVM registration prepare. Full on-chain finalize still depends on the validation wallet having gas on the target chain.
