← All servers

Singularity Layer MCP

warnings

mcp.x402layer.cc

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

https://mcp.x402layer.cc/mcpWebsiteNo authMCP 2024-11-05v1.14.0last checked 18 Oct 2026spoke MCP on 100% of 84 checks (30 days)initialize in 204 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The endpoint answers an anonymous handshake, so no credential is needed.

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

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Connectors → Add custom connector, then paste https://mcp.x402layer.cc/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://mcp.x402layer.cc/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The endpoint answers an anonymous handshake, so no credential is needed.

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

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

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

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 18 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 63 tools listable
Credentials demanded in prose	✕list_my_endpoints, list_my_campaigns, create_campaign, list_my_products, get_endpoint_stats, request_product_purchase_payment, submit_agent_feedback These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

What the probe found

warningTools needing credentials are listed without a challenge

7 of the 63 tools listed anonymously say in their own descriptions that they need an account or a key (list_my_endpoints, list_my_campaigns, create_campaign, list_my_products, get_endpoint_stats, request_product_purchase_payment, submit_agent_feedback), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

Tools

browse_marketplacecloud_credit_activitycloud_credit_balancecloud_get_instancecloud_get_podcloud_get_training_runcloud_grid_modelscloud_grid_usagecloud_list_instancescloud_list_planscloud_list_podscloud_list_processorscloud_list_training_runscloud_pod_catalogcloud_pod_usagecloud_processor_runscreate_campaigncreate_dataset_with_paymentcreate_endpoint_with_paymentdelete_endpointfinalize_agent_registrationfinalize_agent_updateget_agentget_agent_registry_infoget_dataset_statusget_endpoint_detailsget_endpoint_statsget_featuredget_listingget_top_ratedlist_agentslist_categorieslist_dataset_pricinglist_my_agent_bindable_endpointslist_my_campaignslist_my_endpointslist_my_productslist_my_registered_agentslist_networksprepare_agent_registrationprepare_agent_updatepurchase_endpoint_credits_with_paymentpurchase_product_with_paymentremove_webhookrequest_agent_wallet_challengerequest_dataset_paymentrequest_endpoint_creation_paymentrequest_endpoint_credit_purchase_paymentrequest_endpoint_topup_paymentrequest_product_purchase_paymentset_webhooksubmit_agent_feedbacktopup_endpoint_with_paymentupdate_campaignupdate_endpointupdate_productvault_delete_snapshotvault_how_to_backupvault_list_agentsvault_list_snapshotsvault_subscribe_provault_usageverify_agent_wallet_challenge

Contract history

24 Sep 2026v1.14.015 compatible

3 Sep 2026v1.9.02 compatible

2 Sep 2026v1.9.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/singularity-layer-mcp/badge.svg)](https://mcpi.app/servers/singularity-layer-mcp)