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.

Quick Install

One-click setup

Choose your platform to add the Singularity MCP server. Click to expand setup instructions and config.

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

Registry Packageio.github.ivaavimusic/singularity
Registry TitleSingularity Layer MCP
Statusactive
Runtime Version1.6.0
Registry Package Version1.6.0
PublishedMarch 22, 2026
Websitehttps://studio.x402layer.cc/docs/agentic-access/mcp-server

The runtime server name remains singularity-mcp, while the official registry package is io.github.ivaavimusic/singularity.

Endpoint

# MCP HTTP Endpoint
https://mcp.x402layer.cc/mcp

# Alternative Cloudflare Worker URL
https://sgl-mcp.ivaavimusicproductions.workers.dev/mcp

Client Configuration

Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "singularity": {
      "url": "https://mcp.x402layer.cc/mcp"
    }
  }
}

Cursor IDE

Add to your Cursor MCP settings (.cursor/mcp.json in your project root):

{
  "mcpServers": {
    "singularity": {
      "url": "https://mcp.x402layer.cc/mcp"
    }
  }
}

Antigravity / Codex CLI

Add to your MCP config (~/.codex/mcp.json or your project .codex/mcp.json):

{
  "mcpServers": {
    "singularity": {
      "url": "https://mcp.x402layer.cc/mcp",
      "transport": "http"
    }
  }
}

Windsurf / Other MCP Clients

Configure the HTTP transport endpoint:

# HTTP Transport URL
https://mcp.x402layer.cc/mcp

# Protocol: HTTP (stateless)
# Transport: Streamable HTTP

Discovery Tools (Phase 1 — No Auth)

Browse and discover marketplace listings, agents, and categories. No authentication required.

ToolDescriptionParameters
browse_marketplaceSearch/filter listings with paginationtype, category, chain, mode, search, sort, minRating, limit, offset
get_listingGet detailed info for a specific listingslug
get_featuredGet featured marketplace itemslimit
get_top_ratedGet top-rated listingslimit
get_agentGet ERC-8004 agent informationnetwork, agentId, assetAddress
list_categoriesList all available categoriesnone
list_networksList supported blockchain networksnone
list_agentsList all registered ERC-8004 agentsnetwork, limit, offset

PAT Authentication

Personal access tokens are now the default account-level credential for MCP. Create them in Dashboard → Settings → PAT and use accessToken for owner-wide MCP automation. Legacy endpoint keys remain supported for endpoint-scoped flows.

ScopeUse For
mcp:readOwner inventory, endpoint details, and stats
mcp:endpoints:writeEndpoint updates and webhook management
mcp:products:writeProduct updates
mcp:*Full MCP access

Live validation: on March 22, 2026, production MCP validation 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.

Management Tools (Phase 2 + 2.5 — PAT First)

Manage your x402 endpoints and products through authenticated MCP tools. Use accessToken with a scoped sgl_pat_* token for owner-wide automation. Legacy endpoint keys in the x402_* format remain supported where noted.

ToolDescriptionParametersAuth
get_endpoint_detailsFull endpoint info including credit balanceslug, accessToken or apiKey🔐 mcp:read
get_endpoint_statsUsage analytics (requests, revenue, success rate)slug, accessToken or apiKey (optional)📊 mcp:read if PAT is used
list_my_endpointsList endpoints in owner scope, with safe fallback to endpoint-only scopeaccessToken or apiKey🔐 mcp:read
update_endpointUpdate allowlisted endpoint fields, pricing, listing flags, and webhook settingsslug, accessToken or apiKey, allowlisted fields🔐 mcp:endpoints:write
list_my_productsList products in owner scopeaccessToken or apiKey🔐 mcp:read
update_productUpdate allowlisted product metadata, pricing, branding, and listing stateid or slug, accessToken or apiKey, allowlisted fields🔐 mcp:products:write
set_webhookSet/update webhook URL, returns signing secretslug, webhookUrl, accessToken or apiKey🔐 mcp:endpoints:write
remove_webhookRemove webhook from endpointslug, accessToken or apiKey🔐 mcp:endpoints:write
delete_endpoint⚠️ Permanently delete endpointslug, accessToken or apiKey, confirm🔐 mcp:endpoints:write

🔒 Security: PATs and legacy endpoint keys are passed per-request and never stored by the MCP server. Production PATs use sgl_pat_*, production endpoint keys use x402_*, legacy sk_* keys remain accepted, and older agent-created endpoints without a linked dashboard user stay intentionally constrained to endpoint-only scope.

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.

ToolDescriptionParametersAuth
request_endpoint_creation_paymentRequest the x402 challenge needed to create a new agent endpointaccessToken, slug, name, originUrl, walletAddress, chain, endpoint config🔐 mcp:endpoints:write
create_endpoint_with_paymentCreate the endpoint after a paying client returns an X-Payment payloadaccessToken, endpoint config, paymentPayload🔐 mcp:endpoints:write
request_endpoint_topup_paymentRequest the x402 challenge to add credits to an existing agent endpointslug, topupAmount, accessToken or apiKey🔐 mcp:endpoints:write or legacy X-API-Key
topup_endpoint_with_paymentComplete an endpoint top-up after the paying client returns an X-Payment payloadslug, topupAmount, paymentPayload, accessToken or apiKey🔐 mcp:endpoints:write or legacy X-API-Key
request_product_purchase_paymentRequest the x402 challenge for a public product purchaseproductIdOrSlug, clientReferenceId, metadatapublic
purchase_product_with_paymentComplete a public product purchase with a valid X-Payment payloadproductIdOrSlug, paymentPayload, clientReferenceId, metadatapublic
request_endpoint_credit_purchase_paymentRequest the x402 challenge for a public endpoint credit-pack purchaseslug, walletAddress, clientReferenceId, metadatapublic
purchase_endpoint_credits_with_paymentComplete a public endpoint credit-pack purchase with a valid X-Payment payloadslug, paymentPayload, walletAddress, clientReferenceId, metadatapublic

Contract boundary: product tools only wrap /p/:slug-or-id and credit tools only wrap /e/:slug?action=purchase. MCP does not proxy arbitrary paid endpoint execution. Some current credit endpoints still include purchase_url and credit_package with an informational Missing x-wallet-address header field because that is the current upstream worker contract.

Available Resources

URIDescription
singularity://featuredFeatured marketplace listings
singularity://top-ratedTop rated listings
singularity://categoriesAvailable categories
singularity://networksSupported blockchain networks
singularity://agentsAll registered ERC-8004 agents
singularity://listing/{slug}Individual listing details
singularity://agent/{network}/{id}Agent details by network and ID

Phase 4 Agent Registry Tools

MCP now exposes the worker wallet-session flows for ERC-8004 and Solana-8004 registration and management. The wallet signs locally, then MCP exchanges that signature for a short-lived session token. MCP does not hold the wallet private key.

ToolDescriptionAuth
get_agent_registry_infoGet public registry info, supported networks, and worker route notespublic
request_agent_wallet_challengeRequest a wallet-auth challenge for registration or managementpublic
verify_agent_wallet_challengeVerify the signed challenge and receive a short-lived session tokenpublic
list_my_agent_bindable_endpointsList endpoints owned by the wallet or linked dashboard user that can be bound to agentswallet session token
list_my_registered_agentsList ERC-8004 or Solana-8004 agents owned by the wallet or linked dashboard userwallet session token
prepare_agent_registrationPrepare a wallet-first registration flowwallet session token
finalize_agent_registrationFinalize registration after the same wallet sends the on-chain transactionwallet session token
prepare_agent_updatePrepare a wallet-first update and any required on-chain URI actionwallet session token
finalize_agent_updateFinalize the update after any required on-chain transactionwallet session token
submit_agent_feedbackSubmit reputation feedback through the worker feedback routeworker feedback API key

Live validation: on March 22, 2026, production validation confirmed wallet challenge creation, wallet verification, owned endpoint discovery, owned agent discovery, and EVM registration prepare with owned endpoint binding. Full on-chain finalize still depends on the validation wallet having gas on the target chain.

Usage Examples

Browse Marketplace

// Tool call: browse_marketplace
{
  "name": "browse_marketplace",
  "arguments": {
    "category": "ai",
    "sort": "rating",
    "limit": 10
  }
}

Get Endpoint Details (Phase 2)

// Tool call: get_endpoint_details
{
    "name": "get_endpoint_details",
  "arguments": {
    "slug": "my-api-endpoint",
    "accessToken": "sgl_pat_your_token_here"
  }
}

Set Webhook (Phase 2)

// Tool call: set_webhook
{
    "name": "set_webhook",
  "arguments": {
    "slug": "my-api-endpoint",
    "webhookUrl": "https://my-server.com/webhook",
    "accessToken": "sgl_pat_your_token_here"
  }
}

// Response includes signing secret (save it!)
{
  "success": true,
  "webhook": {
    "url": "https://my-server.com/webhook",
    "signing_secret": "whsec_abc123...",
    "note": "Save this secret — it will not be shown again"
  }
}

Get ERC-8004 Agent

// Tool call: get_agent (EVM)
{
  "name": "get_agent",
  "arguments": {
    "network": "base",
    "agentId": 1
  }
}

// Tool call: get_agent (Solana)
{
  "name": "get_agent",
  "arguments": {
    "network": "solana",
    "assetAddress": "AssetAddress123..."
  }
}

Direct API Testing

# Test MCP initialize
curl -X POST https://mcp.x402layer.cc/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"initialize","params":{},"id":1}'

# List all tools (should return 25)
curl -X POST https://mcp.x402layer.cc/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"tools/list","id":2}'

# Browse marketplace
curl -X POST https://mcp.x402layer.cc/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"browse_marketplace","arguments":{"limit":5}},"id":3}'

Categories

ai
data
finance
utility
social
gaming
education
study

Supported Networks

NetworkChain TypeFilter Value
BaseEVMbase
EthereumEVMethereum
PolygonEVMpolygon
BNB Smart ChainEVMbsc
MonadEVMmonad
SolanaSolanasolana

Server Metadata

Runtime Namesingularity-mcp
Registry Packageio.github.ivaavimusic/singularity
Registry TitleSingularity Layer MCP
Version1.6.0 runtime / 1.6.0 registry package
Registry Statusactive
Protocol Version2024-11-05
TransportHTTP (stateless)
DeploymentCloudflare Workers
Total Tools35 (8 discovery + 9 management + 8 payment + 10 agent registry)

Roadmap

Phase 1 - Marketplace Discovery ✅

8 read-only tools for browsing listings, agents, categories, and networks.

Phase 2 - Platform Management ✅

5 authenticated tools for endpoint details, stats, webhooks, and deletion.

Phase 2.5 - Extended Management ✅

Owner-scoped endpoint and product inventory, plus allowlisted endpoint and product updates.

Phase 2.6 - PAT-First Alignment ✅

PAT-first docs, scoped PAT validation, and explicit scope guidance for owner-level MCP automation.

Phase 3A - Endpoint Payment Flows ✅

Payment-backed endpoint creation and top-up tools are now live, and PAT-backed top-up challenges are validated in production.

Phase 3B - Consumer Payment Flows ✅

Public product purchases and endpoint credit-pack purchases are now exposed through MCP without broadening owner auth or turning MCP into a generic paid endpoint proxy.

Phase 4 - Agent Registry ✅

Wallet-session ERC-8004 and Solana-8004 registration, management, and feedback tooling are now live through MCP.

Resources