Singularity Layer MCP

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

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

What data it sees

Do you need an account

No: the server works without sign-in

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

How to connect

How to connect Singularity Layer MCP to Claude

The server address to paste into Claude settings:

https://mcp.x402layer.cc/mcp

Open Claude (claude.ai or the desktop app).
Go to Settings → Connectors.
Click Add custom connector.
Paste the server address copied below into Remote MCP server URL and click Add.
In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Singularity Layer MCP to ChatGPT

The server address to paste into ChatGPT settings:

https://mcp.x402layer.cc/mcp

Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
Open Settings → Connectors and click Create.
Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Singularity Layer MCP to Cursor

The server address to paste into Cursor settings:

https://mcp.x402layer.cc/mcp

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (48)

Raw names from tools/list. Only developers need these.

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.
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_delete_snapshot	Permanently delete one Agent Vault snapshot and free its storage. Irreversible — confirm with the user before calling.
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_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.
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.
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.
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.
browse_marketplace	Browse and search the Singularity Marketplace with various filters. Returns listings of endpoints, products, and agentic services.
get_listing	Get detailed information about a specific marketplace listing by its slug.
get_featured	Get featured marketplace listings (endpoints and products highlighted by the platform).
get_top_rated	Get top-rated marketplace listings sorted by average rating.
get_agent	Get details for a specific ERC-8004 or Solana-8004 agent by network and identifier.
list_categories	List all available marketplace categories.
list_networks	List all supported blockchain networks.
list_agents	List all registered ERC-8004 and Solana-8004 agents.
list_my_endpoints	List the endpoints accessible to the dashboard owner behind your MCP access token or endpoint API key. PATs are preferred for owner-wide inventory and require mcp:read or mcp:*.
list_my_campaigns	List fundraiser campaigns owned by the dashboard user behind your MCP personal access token. Requires mcp:read or mcp:*.
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:*.
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:*.
list_my_products	List the products owned by the same dashboard user as your MCP access token or endpoint API key. PATs are preferred and require mcp:read or mcp:*.
update_product	Update allowlisted product fields including metadata, pricing, listing state, payment options, wallet, branding, and slug. PATs are preferred and require mcp:products: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:*.
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:*.
remove_webhook	Remove the webhook URL from an endpoint. PATs are preferred and require 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:*.
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:*.
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:*.
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.
topup_endpoint_with_payment	Complete an endpoint credit top-up after you have obtained a valid X-Payment payload. 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.
purchase_product_with_payment	Complete a public product purchase after you have obtained a valid X-Payment payload for that product challenge.
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.
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.
get_agent_registry_info	Get public ERC-8004 / Solana-8004 registry information, supported networks, worker routes, and wallet-first notes.
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.
verify_agent_wallet_challenge	Verify a wallet-signed auth challenge and receive a short-lived session token for agent registry flows.
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.
list_my_registered_agents	List ERC-8004 or Solana-8004 agents owned by the authenticated wallet or linked dashboard user.
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.
finalize_agent_registration	Finalize a wallet-first agent registration after the on-chain transaction has been sent from the same wallet.
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.
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.
submit_agent_feedback	Submit on-chain ERC-8004 or Solana-8004 reputation feedback through the worker feedback route. This requires the separate worker feedback API key, not a wallet session token.