Singularity Layer MCP server

Singularity Layer is an MCP server with 48 tools an agent can call, among them browse_marketplace, create_campaign, create_dataset_with_payment. It answers at https://mcp.x402layer.cc/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.

Status

Answering

Tools

Reliability

6 of 6 checks

Response time

156 ms

Transport

streamable HTTP

Last checked

22 October 2026

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

Description as the publisher wrote it.

The 48 tools Singularity Layer offers

Tool	What it does
`browse_marketplace`	Browse and search the Singularity Marketplace with various filters. Returns listings of endpoints, products, and agentic services. Inputs: type, category, chain, mode, search, sort
`create_campaign`	Create a fundraiser campaign owned by the dashboard user behind your MCP personal access token. Requires mcp:campaigns:write or mcp:*. Inputs: accessToken, title, targetAmount, walletAddress, description, xHandle
`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 Inputs: description, seedExamples, targetRows, network, modelTier, modelId
`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:*. Inputs: accessToken, slug, name, originUrl, walletAddress, chain
`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:*. Inputs: slug, accessToken, apiKey, confirm
`finalize_agent_registration`	Finalize a wallet-first agent registration after the on-chain transaction has been sent from the same wallet. Inputs: sessionToken, payload
`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. Inputs: sessionToken, payload
`get_agent`	Get details for a specific ERC-8004 or Solana-8004 agent by network and identifier. Inputs: network, agentId, assetAddress
`get_agent_registry_info`	Get public ERC-8004 / Solana-8004 registry information, supported networks, worker routes, and wallet-first notes.
`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 gener Inputs: datasetId, claimToken
`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:*. Inputs: slug, accessToken, apiKey
`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:*. Inputs: slug, accessToken, apiKey
`get_featured`	Get featured marketplace listings (endpoints and products highlighted by the platform). Inputs: limit
`get_listing`	Get detailed information about a specific marketplace listing by its slug. Inputs: slug
`get_top_rated`	Get top-rated marketplace listings sorted by average rating. Inputs: limit
`list_agents`	List all registered ERC-8004 and Solana-8004 agents. Inputs: network, limit, offset
`list_categories`	List all available marketplace categories.
`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 p
`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. Inputs: sessionToken, listedOnly
`list_my_campaigns`	List fundraiser campaigns owned by the dashboard user behind your MCP personal access token. Requires mcp:read or mcp:*. Inputs: accessToken, slug
`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:*. Inputs: accessToken, apiKey
`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:*. Inputs: accessToken, apiKey
`list_my_registered_agents`	List ERC-8004 or Solana-8004 agents owned by the authenticated wallet or linked dashboard user. Inputs: sessionToken, network
`list_networks`	List all supported blockchain networks.
`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. Inputs: sessionToken, name, description, network, endpoint, image
`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. Inputs: sessionToken, payload
`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. Inputs: slug, paymentPayload, walletAddress, clientReferenceId, metadata
`purchase_product_with_payment`	Complete a public product purchase after you have obtained a valid X-Payment payload for that product challenge. Inputs: productIdOrSlug, paymentPayload, clientReferenceId, metadata
`remove_webhook`	Remove the webhook URL from an endpoint. PATs are preferred and require mcp:endpoints:write or mcp:*. Inputs: slug, accessToken, apiKey
`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. Inputs: chain, walletAddress, action, payload
`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 p Inputs: description, seedExamples, targetRows, network, modelTier, modelId
`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:*. Inputs: accessToken, slug, name, originUrl, walletAddress, chain
`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. Inputs: slug, walletAddress, clientReferenceId, metadata
`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. Inputs: slug, topupAmount, accessToken, apiKey
`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. Inputs: productIdOrSlug, clientReferenceId, metadata
`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:*. Inputs: slug, webhookUrl, accessToken, apiKey
`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. Inputs: apiKey, network, rating, agentId, assetAddress, comment
`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. Inputs: slug, topupAmount, paymentPayload, accessToken, apiKey
`update_campaign`	Update allowlisted fundraiser campaign fields such as title, description, x handle, images, and links. Requires mcp:campaigns:write or mcp:*. Inputs: accessToken, slug, title, description, xHandle, images
`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:*. Inputs: slug, accessToken, apiKey, name, description, category

8 more tools

update_product, vault_delete_snapshot, vault_how_to_backup, vault_list_agents, vault_list_snapshots, vault_subscribe_pro, vault_usage, verify_agent_wallet_challenge

Add Singularity Layer to your AI client

Every block below points at https://mcp.x402layer.cc/mcp. Pick your client and copy.

Claude Code: one command in your terminal

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

Claude Desktop: claude_desktop_config.json

{
  "mcpServers": {
    "singularity-layer": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.x402layer.cc/mcp"]
    }
  }
}

Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project

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

VS Code and GitHub Copilot: .vscode/mcp.json

{
  "servers": {
    "singularity-layer": {
      "type": "http",
      "url": "https://mcp.x402layer.cc/mcp"
    }
  }
}

Zed: Zed settings.json

{
  "context_servers": {
    "singularity-layer": {
      "url": "https://mcp.x402layer.cc/mcp"
    }
  }
}

Windsurf: ~/.codeium/mcp_config.json

{
  "mcpServers": {
    "singularity-layer": {
      "serverUrl": "https://mcp.x402layer.cc/mcp"
    }
  }
}

JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON

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

Continue: .continue/mcpServers/neuronto.yaml

name: Singularity Layer
version: 0.0.1
schema: v1
mcpServers:
  - name: Singularity Layer
    type: streamable-http
    url: https://mcp.x402layer.cc/mcp

Gemini CLI: ~/.gemini/settings.json

{
  "mcpServers": {
    "singularity-layer": {
      "httpUrl": "https://mcp.x402layer.cc/mcp"
    }
  }
}

Codex CLI: MCP server config

{
  "mcpServers": {
    "singularity-layer": {
      "type": "http",
      "url": "https://mcp.x402layer.cc/mcp"
    }
  }
}

Warp: MCP servers, + Add, paste JSON

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

Goose: a one-click extension link

goose://extension?url=https%3A%2F%2Fmcp.x402layer.cc%2Fmcp&type=streamable_http&id=singularity-layer&name=Singularity%20Layer

Is Singularity Layer up right now?

It answered our last check on 22 October 2026 in 156 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Singularity Layer

AssetLog0 tools RUAGENTIC Directory2 tools Agentalog — Agent Auto Log12 tools Inflow0 tools ActuallyCare0 tools travelMCP Directory3 tools

Questions about Singularity Layer

How many tools does Singularity Layer have?

48, as returned by the server's own tools/list on 14 September 2026: browse_marketplace, create_campaign, create_dataset_with_payment, create_endpoint_with_payment, delete_endpoint, finalize_agent_registration, finalize_agent_update, get_agent, and 40 more.

Is Singularity Layer down?

It answered our last check on 22 October 2026 in 156 ms. Over 6 checks since 11 September 2026 it answered 6.

How do I add Singularity Layer to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.x402layer.cc/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Singularity Layer need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.ivaavimusic. Endpoint host: mcp.x402layer.cc. ARD identifier: urn:air:io.github.ivaavimusic:mcp:singularity. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.