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 setupChoose 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 Package | io.github.ivaavimusic/singularity |
| Registry Title | Singularity Layer MCP |
| Status | active |
| Runtime Version | 1.6.0 |
| Registry Package Version | 1.6.0 |
| Published | March 22, 2026 |
| Website | https://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/mcpClient 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 HTTPDiscovery Tools (Phase 1 — No Auth)
Browse and discover marketplace listings, agents, and categories. No authentication required.
| Tool | Description | Parameters |
|---|---|---|
| browse_marketplace | Search/filter listings with pagination | type, category, chain, mode, search, sort, minRating, limit, offset |
| get_listing | Get detailed info for a specific listing | slug |
| get_featured | Get featured marketplace items | limit |
| get_top_rated | Get top-rated listings | limit |
| get_agent | Get ERC-8004 agent information | network, agentId, assetAddress |
| list_categories | List all available categories | none |
| list_networks | List supported blockchain networks | none |
| list_agents | List all registered ERC-8004 agents | network, 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.
| Scope | Use For |
|---|---|
| mcp:read | Owner inventory, endpoint details, and stats |
| mcp:endpoints:write | Endpoint updates and webhook management |
| mcp:products:write | Product 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.
| Tool | Description | Parameters | Auth |
|---|---|---|---|
| get_endpoint_details | Full endpoint info including credit balance | slug, accessToken or apiKey | 🔐 mcp:read |
| get_endpoint_stats | Usage analytics (requests, revenue, success rate) | slug, accessToken or apiKey (optional) | 📊 mcp:read if PAT is used |
| list_my_endpoints | List endpoints in owner scope, with safe fallback to endpoint-only scope | accessToken or apiKey | 🔐 mcp:read |
| update_endpoint | Update allowlisted endpoint fields, pricing, listing flags, and webhook settings | slug, accessToken or apiKey, allowlisted fields | 🔐 mcp:endpoints:write |
| list_my_products | List products in owner scope | accessToken or apiKey | 🔐 mcp:read |
| update_product | Update allowlisted product metadata, pricing, branding, and listing state | id or slug, accessToken or apiKey, allowlisted fields | 🔐 mcp:products:write |
| set_webhook | Set/update webhook URL, returns signing secret | slug, webhookUrl, accessToken or apiKey | 🔐 mcp:endpoints:write |
| remove_webhook | Remove webhook from endpoint | slug, accessToken or apiKey | 🔐 mcp:endpoints:write |
| delete_endpoint | ⚠️ Permanently delete endpoint | slug, 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.
| Tool | Description | Parameters | Auth |
|---|---|---|---|
| request_endpoint_creation_payment | Request the x402 challenge needed to create a new agent endpoint | accessToken, slug, name, originUrl, walletAddress, chain, endpoint config | 🔐 mcp:endpoints:write |
| create_endpoint_with_payment | Create the endpoint after a paying client returns an X-Payment payload | accessToken, endpoint config, paymentPayload | 🔐 mcp:endpoints:write |
| request_endpoint_topup_payment | Request the x402 challenge to add credits to an existing agent endpoint | slug, topupAmount, accessToken or apiKey | 🔐 mcp:endpoints:write or legacy X-API-Key |
| topup_endpoint_with_payment | Complete an endpoint top-up after the paying client returns an X-Payment payload | slug, topupAmount, paymentPayload, accessToken or apiKey | 🔐 mcp:endpoints:write or legacy X-API-Key |
| request_product_purchase_payment | Request the x402 challenge for a public product purchase | productIdOrSlug, clientReferenceId, metadata | public |
| purchase_product_with_payment | Complete a public product purchase with a valid X-Payment payload | productIdOrSlug, paymentPayload, clientReferenceId, metadata | public |
| request_endpoint_credit_purchase_payment | Request the x402 challenge for a public endpoint credit-pack purchase | slug, walletAddress, clientReferenceId, metadata | public |
| purchase_endpoint_credits_with_payment | Complete a public endpoint credit-pack purchase with a valid X-Payment payload | slug, paymentPayload, walletAddress, clientReferenceId, metadata | public |
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
| URI | Description |
|---|---|
| singularity://featured | Featured marketplace listings |
| singularity://top-rated | Top rated listings |
| singularity://categories | Available categories |
| singularity://networks | Supported blockchain networks |
| singularity://agents | All 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.
| Tool | Description | Auth |
|---|---|---|
| get_agent_registry_info | Get public registry info, supported networks, and worker route notes | public |
| request_agent_wallet_challenge | Request a wallet-auth challenge for registration or management | public |
| verify_agent_wallet_challenge | Verify the signed challenge and receive a short-lived session token | public |
| list_my_agent_bindable_endpoints | List endpoints owned by the wallet or linked dashboard user that can be bound to agents | wallet session token |
| list_my_registered_agents | List ERC-8004 or Solana-8004 agents owned by the wallet or linked dashboard user | wallet session token |
| prepare_agent_registration | Prepare a wallet-first registration flow | wallet session token |
| finalize_agent_registration | Finalize registration after the same wallet sends the on-chain transaction | wallet session token |
| prepare_agent_update | Prepare a wallet-first update and any required on-chain URI action | wallet session token |
| finalize_agent_update | Finalize the update after any required on-chain transaction | wallet session token |
| submit_agent_feedback | Submit reputation feedback through the worker feedback route | worker 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
Supported Networks
| Network | Chain Type | Filter Value |
|---|---|---|
| Base | EVM | base |
| Ethereum | EVM | ethereum |
| Polygon | EVM | polygon |
| BNB Smart Chain | EVM | bsc |
| Monad | EVM | monad |
| Solana | Solana | solana |
Server Metadata
| Runtime Name | singularity-mcp |
| Registry Package | io.github.ivaavimusic/singularity |
| Registry Title | Singularity Layer MCP |
| Version | 1.6.0 runtime / 1.6.0 registry package |
| Registry Status | active |
| Protocol Version | 2024-11-05 |
| Transport | HTTP (stateless) |
| Deployment | Cloudflare Workers |
| Total Tools | 35 (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.