Singularity Layer MCP Server

io.github.ivaavimusic/singularity

answering

Singularity Layer MCP is answering right now. Last checked 13 min ago. It exposes 38 tools.

MCP for Singularity Layer - discover listings, manage assets, run payment flows, and use agents

Uptime history 40 hours of history

40 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

181 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add singularity --transport http https://mcp.x402layer.cc/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.singularity]
url = "https://mcp.x402layer.cc/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 38

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

endpoint

create_endpoint_with_payment

Create a new agent endpoint after you have obtained a valid X-Payment payload for the creation challenge. Requires a dashboard PAT with mcp:endpoints:write or mcp:*.

delete_endpoint

⚠️ DESTRUCTIVE: Permanently delete an endpoint. Cannot be undone. Only works for agent-created endpoints. PATs are preferred and require mcp:endpoints:write or mcp:*.

get_endpoint_details

Get full details for an endpoint you own, including credit balance, pricing config, and wallet address. PATs are preferred and require mcp:read or mcp:*.

get_endpoint_stats

Get usage analytics for an endpoint: total requests, monthly requests, revenue, and success rate. PATs or endpoint API keys improve accuracy. PATs require mcp:read or mcp:*.

update_endpoint

Update allowlisted endpoint fields such as metadata, pricing, listing flags, imagery, wallet, payment options, slug, and webhook settings. PATs are preferred and require mcp:endpoints:write or mcp:*.

request

request_agent_wallet_challenge

Create a wallet-auth challenge for ERC-8004 agent registration or management. The wallet owner must sign the returned message locally; MCP does not sign with the wallet.

request_endpoint_creation_payment

Return the x402 payment challenge needed to create a new agent endpoint. Requires a dashboard PAT with mcp:endpoints:write or mcp:*.

request_endpoint_credit_purchase_payment

Return the x402 payment challenge for purchasing a public credit pack from an endpoint that exposes /e/:slug?action=purchase.

request_endpoint_topup_payment

Return the x402 payment challenge needed to top up credits for an existing agent endpoint. Accepts either a dashboard PAT with mcp:endpoints:write or mcp:* or a legacy endpoint API key.

request_product_purchase_payment

Return the x402 payment challenge for purchasing a public product. This wraps the existing public /p/:id-or-slug flow and does not require owner credentials.

agent

get_agent

Get details for a specific ERC-8004 or Solana-8004 agent by network and identifier.

get_agent_registry_info

Get public ERC-8004 / Solana-8004 registry information, supported networks, worker routes, and wallet-first notes.

list_my_agent_bindable_endpoints

List platform endpoints owned by the authenticated wallet or linked dashboard user that can be bound to ERC-8004 agents.

campaign

create_campaign

Create a fundraiser campaign owned by the dashboard user behind your MCP personal access token. Requires mcp:campaigns:write or mcp:*.

update_campaign

Update allowlisted fundraiser campaign fields such as title, description, x handle, images, and links. Requires mcp:campaigns:write or mcp:*.

finalize

finalize_agent_registration

Finalize a wallet-first agent registration after the on-chain transaction has been sent from the same wallet.

finalize_agent_update

Finalize a wallet-first update for an existing ERC-8004 or Solana-8004 agent after any required on-chain transaction has been sent from the same wallet.

prepare

prepare_agent_registration

Prepare a wallet-first ERC-8004 or Solana-8004 registration. The caller must later send the on-chain transaction from the same wallet and then call finalize_agent_registration.

prepare_agent_update

Prepare a wallet-first update for an existing ERC-8004 or Solana-8004 agent. If metadata changes require an on-chain URI update, the response describes that action.

purchase

purchase_endpoint_credits_with_payment

Complete a public endpoint credit-pack purchase after you have obtained a valid X-Payment payload for the purchase challenge.

purchase_product_with_payment

Complete a public product purchase after you have obtained a valid X-Payment payload for that product challenge.

webhook

remove_webhook

Remove the webhook URL from an endpoint. PATs are preferred and require mcp:endpoints:write or mcp:*.

set_webhook

Set or update the webhook URL for an endpoint. Returns a signing secret that must be saved. PATs are preferred and require mcp:endpoints:write or mcp:*.

agents

list_agents

List all registered ERC-8004 and Solana-8004 agents.

browse

browse_marketplace

Browse and search the Singularity Marketplace with various filters. Returns listings of endpoints, products, and agentic services.

campaigns

list_my_campaigns

List fundraiser campaigns owned by the dashboard user behind your MCP personal access token. Requires mcp:read or mcp:*.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.x402layer.cc/mcp	streamable-http	answering	251 ms	13 min ago

Singularity Layer MCP — questions

Answers built from our own checks of this server.

What can Singularity Layer MCP do?

It exposes 38 tools, read directly from the server on our last check. Among them: browse_marketplace, create_campaign, create_endpoint_with_payment, delete_endpoint, finalize_agent_registration, finalize_agent_update and 32 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Singularity Layer MCP mostly used for?

Its tools cluster around endpoint, request and agent. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Singularity Layer MCP working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 181 ms. The bar chart above shows every period we have measured.

How do I connect Singularity Layer MCP?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Singularity Layer MCP need an API key?

No. Singularity Layer MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 38 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Singularity Layer MCP?

It answers our handshake in 181 ms on average, which is faster than 67% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.