Singularity Layer MCP Server

by ivaavimusic Your server? Claim it

answering

Singularity Layer MCP is answering right now. Last checked 14 min ago. It exposes 48 tools.

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

Uptime history 48 days of history

48 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

198 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 18

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 August 2026. No other catalogue keeps this.

3 Sep 2 tools changed the parameters they ask for create_dataset_with_payment, request_dataset_payment

2 Sep 2 tools changed the parameters they ask for create_dataset_with_payment, request_dataset_payment

31 Aug 4 tools appeared create_dataset_with_payment, get_dataset_status, list_dataset_pricing and 1 more

20 Aug a tool description was rewritten2 times that day vault_subscribe_pro

20 Aug a tool changed the parameters it asks for vault_subscribe_pro

18 Aug 6 tools appeared vault_delete_snapshot, vault_how_to_backup, vault_list_agents and 3 more

18 Aug a tool changed version

and 1 more, back to 18 August 2026

Nothing serious here today

Today is the operative word: we check Singularity Layer MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 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 48

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

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_dataset_payment

Step 1 of buying a training dataset: submit the job and get back an x402 payment challenge with the exact price. Nothing is charged and nothing is generated yet. Pass the SAME arguments to create_dataset_with_payment: the server binds the payment to this exact job and refuses a mismatch.

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.

vault

vault_delete_snapshot

Permanently delete one Agent Vault snapshot and free its storage. Irreversible — confirm with the user before calling.

vault_how_to_backup

How to actually CREATE or RESTORE an encrypted backup. Encryption is zero-knowledge and must run on the machine where the agent lives — this returns the exact CLI/SDK steps.

vault_list_agents

List the agents registered in Agent Vault for this wallet (OpenClaw, Hermes, pods, and custom --path lineages).

vault_list_snapshots

List completed Agent Vault snapshots (encrypted backups) for this wallet, optionally filtered to one agent. Use this to check WHEN an agent was last backed up.

vault_subscribe_pro

Change the wallet’s Agent Vault plan, charged from platform credits. pro = 10 GB + the last 10 snapshots of each agent ($3/month, $30/year); max = 50 GB + unlimited snapshots ($5/month, $50/year); free = cancel at period end. Yearly is two months free. Upgrades are charged immediately and prorated against the unused period; downgrades and cancellations take effect at period end. A plan change never deletes snapshots. ALWAYS confirm the plan and the charge with the user before calling.

vault_usage

Agent Vault storage usage and plan for the wallet behind a compute API key: bytes used/reserved, free vs pro plan, caps, and Vault Pro pricing.

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:*.

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.

dataset

create_dataset_with_payment

Step 2 of buying a training dataset: submit the job again with the signed X-Payment payload and the quote id. Returns in seconds with a dataset id and a claim token; generation then runs in the background. SAVE THE CLAIM TOKEN — it is shown once and is the only way to read the job or download the result.

get_dataset_status

How a purchased dataset is coming along, and the download link once it is ready. Returns rows done vs target while generating, a presigned JSONL download URL (valid 5 minutes, re-issued each call) when complete, or the refund state if generation failed.

list_dataset_pricing

What a generated training dataset costs and which models can generate it: per-100-example rates for each managed tier plus the decentralized grid, the maximum size, and the model catalog with published per-million-token rates. No auth, no payment. Call this before quoting a job.

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	120 ms	14 min ago

Alternatives to Singularity Layer MCP

same job, measured the same way

Swarmpay

by ginokino

Payment layer for AI agents. Send USDC, manage escrows on Base blockchain.

74 installs/wk local only

M2mcent

by evozim

x402 payment wrapper for AI Agents and MCP Servers. USDC settlements on Base L2.

82 installs/wk local only

Secant Agent Research Pack

by jnilrac

Paid MCP web research for agents: search, extraction, citations, and x402 payment discovery.

5 tools answering

X402 Data Gateway

by epistemedeus

Paid x402 and MPP tools for agent discovery, payment safety, data, and DeFi.

24 tools answering

Minia2a MCP

by minia2a

MCP server for minia2a.uk — discover and call 1,600+ x402 pay-per-call APIs with USDC payments.

local only

HPP x402 MCP Bridge

by hpp-io

MCP bridge for autonomous x402 payments in HPP USDC.e — discover and pay for services per call.

93 installs/wk local only

US Brand Intelligence

by timzinin-api

Pay-per-call US brand evidence and signal workflows with free MCP discovery and x402 payments.

21 tools answering

Agent Pay

by joepangallo

Payment gateway for AI agents with tool discovery, provisioning, metering, and reliability tools.

56 installs/wk local only

Singularity Layer MCP — questions

Answers built from our own checks of this server.

What can Singularity Layer MCP do?

It exposes 48 tools, read directly from the server on our last check. Among them: browse_marketplace, create_campaign, create_dataset_with_payment, create_endpoint_with_payment, delete_endpoint, finalize_agent_registration and 42 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 request, vault and endpoint. 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 198 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 48 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 198 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.