Singularity Layer MCP
REMOTE · MCP.X402LAYER.CC
MCP for Singularity Layer - discover listings, manage assets, run payment flows, and use agents
Available components
Last scanned (14 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 81 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability46
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 10240 tokens (~119/item across 86 items; 81 tools + 5 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 99% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "vault_delete_snapshot" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 82 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 81 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 0
- Tool “cloud_pod_exec” rewrote its description, which is the text the model reads security
- Tool “cloud_pod_files” rewrote its description, which is the text the model reads security
- Tool “cloud_pod_write_file” rewrote its description, which is the text the model reads security
- Server version: 1.16.0 → 1.17.0 functional
- New tool “plan_flow_with_credits” functional
- New tool “plan_flow_with_payment” functional
- New tool “request_flow_plan_payment” functional
- 12 Nov 26 0
- Schema quality: 7230 → 9642 ▼ functional
- Server version: 1.14.0 → 1.16.0 functional
- New tool “cloud_deploy_machine” functional
- New tool “cloud_deploy_pod” functional
- New tool “cloud_deploy_processor” functional
- New tool “cloud_pod_chat” functional
- New tool “cloud_pod_exec” functional
- New tool “cloud_pod_files” functional
- New tool “cloud_pod_write_file” functional
- New tool “cloud_start_training_run” functional
- New tool “create_invoice” functional
- New tool “create_payment_link” functional
- New tool “get_invoice” functional
- New tool “get_payment_link” functional
- New tool “list_invoices” functional
- New tool “list_payment_links” functional
- New tool “list_payments” functional
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Schema quality: excellent → good functional
- Stability: pass → 0.97 functional
- “create_campaign” reworded the description of “accessToken” cosmetic
- “create_endpoint_with_payment” reworded the description of “accessToken” cosmetic
- “delete_endpoint” reworded the description of “accessToken” cosmetic
- “get_endpoint_details” reworded the description of “accessToken” cosmetic
- “list_my_campaigns” reworded the description of “accessToken” cosmetic
- “list_my_endpoints” reworded the description of “accessToken” cosmetic
- “list_my_products” reworded the description of “accessToken” cosmetic
- “remove_webhook” reworded the description of “accessToken” cosmetic
- “request_endpoint_creation_payment” reworded the description of “accessToken” cosmetic
- “request_endpoint_topup_payment” reworded the description of “accessToken” cosmetic
- “set_webhook” reworded the description of “accessToken” cosmetic
- “topup_endpoint_with_payment” reworded the description of “accessToken” cosmetic
- “update_campaign” reworded the description of “accessToken” cosmetic
- “update_endpoint” reworded the description of “accessToken” cosmetic
- “update_product” reworded the description of “accessToken” cosmetic
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Schema quality: 6026 → 6990 ▼ functional
- Schema quality: good → excellent functional
- Server version: 1.9.0 → 1.14.0 functional
- New tool “cloud_credit_activity” functional
- New tool “cloud_credit_balance” functional
- New tool “cloud_get_instance” functional
- New tool “cloud_get_pod” functional
- New tool “cloud_get_training_run” functional
- New tool “cloud_grid_models” functional
- New tool “cloud_grid_usage” functional
- New tool “cloud_list_instances” functional
- New tool “cloud_list_plans” functional
- New tool “cloud_list_pods” functional
- New tool “cloud_list_processors” functional
- New tool “cloud_list_training_runs” functional
- New tool “cloud_pod_catalog” functional
- New tool “cloud_pod_usage” functional
- New tool “cloud_processor_runs” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.x402layer.cc/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=x402layer.cc | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 7e225ceec2b4ee5a13cc95b44d38f783 |
| SANs: x402layer.cc, mcp.x402layer.cc | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.x402layer.cc. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| cc. | DS published | 12593 | 13 | Verified |
| x402layer.cc. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.x402layer.cc/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.x402layer.cc/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_my_registered_agents ~60
List ERC-8004 or Solana-8004 agents owned by the authenticated wallet or linked dashboard user.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Optional network filter |
| sessionToken | string | yes | Wallet session token returned by verify_agent_wallet_challenge |
No output schema declared.
No examples provided.
list_networks ~15
List all supported blockchain networks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_payment_links ~77
List your payment links: title, amount in USDC, chains, payout wallets, active, and the pay page URL. Needs an access token with mcp:read.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | yes | Your Studio access token (sgl_pat_*). Can be omitted when the connection sends Authorization: Bearer sgl_pat_* |
No output schema declared.
No examples provided.
list_payments ~214
Recent payments you received on your Endpoints, Products, payment links and invoices, newest first, with filters. Needs an access token with mcp:read. Endpoints cover the latest 50 each.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | yes | Your Studio access token (sgl_pat_*). Can be omitted when the connection sends Authorization: Bearer sgl_pat_* |
| endpoint_slug | string | – | Only this Endpoint |
| limit | integer | – | Default 25 |
| min_amount | number | – | Only payments of at least this amount |
| payer | string | – | Only payments from this wallet address |
| product | string | – | Only this Product or payment link (id or slug) |
| since | string | – | Only payments at or after this date (ISO 8601, for example 2026-11-01) |
| source | string | – | all (default), endpoints, or products (Products, payment links and invoices) |
| status | string | – | Only this status, for example confirmed |
No output schema declared.
No examples provided.
plan_flow_with_credits ~230
Plan a flow of paid x402 services for a goal, paid with $0.02 of platform credits. Credential: a full-access Studio token (sgl_pat_*, mcp:*) or a Singularity Cloud API key with compute:write and spend. Nothing found = not charged. Use the same idempotencyKey to retry without a second charge.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | – | Full-access Studio token (sgl_pat_*) |
| budgetUsd | number | – | Warn when one run of the flow would cost more than this |
| computeApiKey | string | – | Singularity Cloud API key with compute:write and spend |
| goal | string | yes | What you want done, in plain words (3 to 600 characters) |
| idempotencyKey | string | – | Your id for this request; a retry with the same id and goal is never charged twice |
| maxSteps | integer | – | At most this many steps (1 to 5) |
| networks | array | – | Only services payable on these networks, e.g. ["base","solana"] |
No output schema declared.
No examples provided.
plan_flow_with_payment ~168
Plan a flow of paid x402 services for a goal, paid with a signed x402 payment ($0.02, USDC on Base or Solana). Settled only after a plan is produced; nothing found = not charged. If the answer is settlement_pending, do NOT pay again.
| Name | Type | Req | Description |
|---|---|---|---|
| budgetUsd | number | – | Warn when one run of the flow would cost more than this |
| goal | string | yes | What you want done, in plain words (3 to 600 characters) |
| maxSteps | integer | – | At most this many steps (1 to 5) |
| networks | array | – | Only services payable on these networks, e.g. ["base","solana"] |
| paymentPayload | – | yes | The signed X-Payment payload, as JSON or base64 |
No output schema declared.
No examples provided.
prepare_agent_registration ~190
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.
| Name | Type | Req | Description |
|---|---|---|---|
| assetAddress | string | – | Required for Solana registrations |
| customEndpoints | array | – | Custom endpoint URLs to bind |
| description | string | yes | Agent description |
| endpoint | string | – | Primary or fallback endpoint URL |
| endpointIds | array | – | Platform endpoint UUIDs to bind |
| image | string | – | Agent image URL |
| name | string | yes | Agent name |
| network | string | yes | Target network for the agent |
| ownerAddress | string | – | Owner wallet address matching the authenticated session wallet |
| sessionToken | string | yes | Wallet session token with erc8004_register scope |
| tags | array | – | Agent tags |
| version | string | – | Agent version string |
No output schema declared.
No examples provided.
prepare_agent_update ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| payload | object | yes | Raw update payload expected by the worker, including network plus agentId or assetAddress and the requested fields to change |
| sessionToken | string | yes | Wallet session token with erc8004_manage, erc8004_update, or erc8004_register scope |
No output schema declared.
No examples provided.
purchase_endpoint_credits_with_payment ~126
Complete a public endpoint credit-pack purchase after you have obtained a valid X-Payment payload for the purchase challenge.
| Name | Type | Req | Description |
|---|---|---|---|
| clientReferenceId | string | – | Optional client reference ID forwarded to the purchase flow |
| metadata | object | – | Optional metadata object forwarded to the purchase flow |
| paymentPayload | – | yes | Raw X-Payment payload returned by the paying client, as JSON or base64 string |
| slug | string | yes | Endpoint slug for the credit-enabled endpoint |
| walletAddress | string | – | Optional wallet address to receive the purchased credits when the underlying endpoint supports it |
No output schema declared.
No examples provided.
purchase_product_with_payment ~114
Complete a public product purchase after you have obtained a valid X-Payment payload for that product challenge.
| Name | Type | Req | Description |
|---|---|---|---|
| clientReferenceId | string | – | Optional client reference ID forwarded to the purchase flow |
| metadata | object | – | Optional metadata object forwarded to the purchase flow |
| paymentPayload | – | yes | Raw X-Payment payload returned by the paying client, as JSON or base64 string |
| productIdOrSlug | string | yes | Product slug or product ID used in the public /p/:id-or-slug purchase route |
No output schema declared.
No examples provided.
remove_webhook ~99
Remove the webhook URL from an endpoint. PATs are preferred and require mcp:endpoints:write or mcp:*.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | – | Your dashboard MCP personal access token (sgl_pat_*). Can be omitted when the connection sends Authorization: Bearer sgl_pat_* |
| apiKey | string | – | Legacy endpoint API key (x402_*) |
| slug | string | yes | The unique slug identifier for the endpoint |
No output schema declared.
No examples provided.
request_agent_wallet_challenge ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Session scope to request |
| chain | string | yes | Wallet auth chain |
| payload | object | – | Optional payload object to bind into the signed challenge |
| walletAddress | string | yes | Wallet address that will sign the challenge |
No output schema declared.
No examples provided.
request_dataset_payment ~364
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What the model being trained should do, in one plain sentence |
| gridModel | string | – | Model on the decentralized encrypted grid: cheaper, slower, data never leaves the network |
| modelId | string | – | Exact managed model from list_dataset_pricing (decides the tier and price) |
| modelTier | string | – | Managed model speed/quality tier. Omit when using gridModel |
| name | string | – | Name for the dataset |
| network | string | – | Chain you will pay on (default base) |
| rules | array | – | House rules the assistant must NEVER break, e.g. "Never promise a refund". Without them the model invents its own policy, differently each time |
| seedExamples | array | yes | 5 to 20 example conversations showing the behaviour you want |
| systemPrompt | string | – | Standing instruction every generated example should follow |
| targetRows | number | yes | How many examples to generate (50-2000). Price scales with this |
| verify | boolean | – | Check every row with a second model and regenerate any that break the rules. ON by default, priced separately ($0.10 per 100 managed, $0.03 per 100 grid where the grid checks its own work so nothing… |
| webhookUrl | string | – | Public HTTPS URL to notify when the dataset is ready; the POST is signed |
No output schema declared.
No examples provided.
request_endpoint_creation_payment ~283
Return the x402 payment challenge needed to create a new agent endpoint. Requires a dashboard PAT with mcp:endpoints:write or mcp:*.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | yes | Your dashboard MCP personal access token (sgl_pat_*). Can be omitted when the connection sends Authorization: Bearer sgl_pat_* |
| bannerUrl | string | – | Endpoint banner URL |
| category | string | – | Marketplace category |
| chain | string | yes | Primary payout network, usually base, solana, or both |
| currency | string | – | Payout currency, default USDC |
| description | string | – | Endpoint description |
| imageUrl | string | – | Endpoint image URL |
| listOnMarketplace | boolean | – | Whether to list the endpoint publicly |
| mode | string | – | Pricing mode |
| name | string | yes | Human-readable endpoint name |
| originUrl | string | yes | Origin URL of the endpoint backend |
| price | number | – | Price per request or base package price |
| purchaseAmount | number | – | USDC amount to pay on creation, minimum 5 |
| slug | string | yes | Unique slug for the new endpoint |
| walletAddress | string | yes | Primary payout wallet address |
| walletAddressSecondary | string | – | Secondary wallet when chain is both |
| webhookUrl | string|null | – | Optional HTTPS webhook URL |
No output schema declared.
No examples provided.
request_endpoint_credit_purchase_payment ~105
Return the x402 payment challenge for purchasing a public credit pack from an endpoint that exposes /e/:slug?action=purchase.
| Name | Type | Req | Description |
|---|---|---|---|
| clientReferenceId | string | – | Optional client reference ID forwarded to the purchase flow |
| metadata | object | – | Optional metadata object forwarded to the purchase flow |
| slug | string | yes | Endpoint slug for the credit-enabled endpoint |
| walletAddress | string | – | Optional wallet address to receive the purchased credits when the underlying endpoint supports it |
No output schema declared.
No examples provided.
request_endpoint_topup_payment ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | – | Your dashboard MCP personal access token (sgl_pat_*). Can be omitted when the connection sends Authorization: Bearer sgl_pat_* |
| apiKey | string | – | Legacy endpoint API key (x402_*) |
| slug | string | yes | Slug of the endpoint to top up |
| topupAmount | number | yes | USDC amount to add, minimum 1 |
No output schema declared.
No examples provided.
request_flow_plan_payment ~151
Get the x402 payment challenge for the flow planner ($0.02 per plan, USDC on Base or Solana). Free, no auth. Sign one accepts entry with your wallet, then call plan_flow_with_payment. MPP and credits are also accepted (see other_ways_to_pay).
| Name | Type | Req | Description |
|---|---|---|---|
| budgetUsd | number | – | Warn when one run of the flow would cost more than this |
| goal | string | yes | What you want done, in plain words (3 to 600 characters) |
| maxSteps | integer | – | At most this many steps (1 to 5) |
| networks | array | – | Only services payable on these networks, e.g. ["base","solana"] |
No output schema declared.
No examples provided.
request_product_purchase_payment ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| clientReferenceId | string | – | Optional client reference ID forwarded to the purchase flow |
| metadata | object | – | Optional metadata object forwarded to the purchase flow |
| productIdOrSlug | string | yes | Product slug or product ID used in the public /p/:id-or-slug purchase route |
No output schema declared.
No examples provided.
set_webhook ~124
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:*.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | – | Your dashboard MCP personal access token (sgl_pat_*). Can be omitted when the connection sends Authorization: Bearer sgl_pat_* |
| apiKey | string | – | Legacy endpoint API key (x402_*) |
| slug | string | yes | The unique slug identifier for the endpoint |
| webhookUrl | string | yes | HTTPS URL to receive webhook events |
No output schema declared.
No examples provided.
submit_agent_feedback ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | number | – | EVM agent id |
| apiKey | string | yes | Worker feedback API key |
| assetAddress | string | – | Solana asset address |
| comment | string | – | Optional feedback comment |
| endpoint | string | – | Optional endpoint context string |
| network | string | yes | Target network for the feedback |
| rating | number | yes | Rating from 1 to 5 |
| tag1 | string | – | Primary tag, default overall |
| tag2 | string | – | Secondary tag, default agentic |
No output schema declared.
No examples provided.
topup_endpoint_with_payment ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | – | Your dashboard MCP personal access token (sgl_pat_*). Can be omitted when the connection sends Authorization: Bearer sgl_pat_* |
| apiKey | string | – | Legacy endpoint API key (x402_*) |
| paymentPayload | – | yes | Raw X-Payment payload returned by the paying client, as JSON or base64 string |
| slug | string | yes | Slug of the endpoint to top up |
| topupAmount | number | yes | USDC amount to add, minimum 1 |
No output schema declared.
No examples provided.
update_campaign ~140
Update allowlisted fundraiser campaign fields such as title, description, x handle, images, and links. Requires mcp:campaigns:write or mcp:*.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | yes | Your dashboard MCP personal access token (sgl_pat_*). Can be omitted when the connection sends Authorization: Bearer sgl_pat_* |
| description | string | – | Updated campaign description |
| images | array | – | Updated HTTPS image URLs |
| links | – | – | Updated campaign links array |
| slug | string | yes | Campaign slug to update |
| title | string | – | Updated campaign title |
| xHandle | string | – | Updated X handle without @ |
No output schema declared.
No examples provided.
update_endpoint ~356
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:*.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | – | Your dashboard MCP personal access token (sgl_pat_*). Can be omitted when the connection sends Authorization: Bearer sgl_pat_* |
| active | boolean | – | Enable or disable the endpoint |
| apiKey | string | – | Legacy endpoint API key (x402_*) |
| bannerUrl | string | – | Updated banner URL |
| category | string | – | Updated category |
| chain | string | – | Updated chain/network |
| creditPackagePrice | number | – | Package price in USDC |
| creditPackageSize | number | – | Credits per package |
| currency | string | – | Updated currency code |
| description | string | – | Updated description |
| imageUrl | string | – | Updated image URL |
| isListed | boolean | – | Whether the endpoint should be listed |
| listedInMarketplace | boolean | – | Whether the endpoint should appear in marketplace listings |
| logoUrl | string | – | Updated logo URL |
| mode | string | – | Pricing mode |
| name | string | – | Updated endpoint name |
| newSlug | string | – | New slug to assign to the endpoint |
| originUrl | string | – | Updated origin URL |
| paymentOptions | – | – | Updated payment options object |
| price | number | – | Updated endpoint price |
| slug | string | yes | The existing slug of the endpoint you want to update |
| walletAddress | string | – | Updated payout wallet address |
| webhookUrl | string|null | – | Set an HTTPS webhook URL or null to remove it |
No output schema declared.
No examples provided.
update_product ~342
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:*.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | – | Your dashboard MCP personal access token (sgl_pat_*). Can be omitted when the connection sends Authorization: Bearer sgl_pat_* |
| active | boolean | – | Enable or disable the product |
| apiKey | string | – | Legacy endpoint API key (x402_*) |
| bannerUrl | string | – | Updated banner URL |
| category | string | – | Updated product category |
| chain | string | – | Updated chain/network |
| currency | string | – | Updated currency code |
| customButtonBg | string | – | Custom button background color |
| customButtonText | string | – | Custom button text color |
| customFont | string | – | Custom font family |
| customPageBg | string | – | Custom page background color |
| customPageText | string | – | Custom page text color |
| description | string | – | Updated product description |
| id | string | – | Product ID to update |
| isListed | boolean | – | Whether the product should be listed |
| logoUrl | string | – | Updated logo URL |
| name | string | – | Updated product name |
| newSlug | string | – | New slug to assign to the product |
| paymentOptions | – | – | Updated payment options object |
| price | number | – | Updated product price |
| productImageUrl | string | – | Updated product image URL |
| slug | string | – | Product slug to update |
| walletAddress | string | – | Updated payout wallet address |
No output schema declared.
No examples provided.
vault_delete_snapshot ~75
Permanently delete one Agent Vault snapshot and free its storage. Irreversible — confirm with the user before calling.
| Name | Type | Req | Description |
|---|---|---|---|
| computeApiKey | string | yes | Singularity compute API key (dashboard → Settings → API Keys, or minted by `agentvault login`) |
| snapshotId | string | yes | Snapshot id to delete (uuid) |
No output schema declared.
No examples provided.
vault_how_to_backup ~47
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vault_list_agents ~64
List the agents registered in Agent Vault for this wallet (OpenClaw, Hermes, pods, and custom --path lineages).
| Name | Type | Req | Description |
|---|---|---|---|
| computeApiKey | string | yes | Singularity compute API key (dashboard → Settings → API Keys, or minted by `agentvault login`) |
No output schema declared.
No examples provided.
vault_list_snapshots ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | – | Filter to one vault agent id (uuid) |
| computeApiKey | string | yes | Singularity compute API key (dashboard → Settings → API Keys, or minted by `agentvault login`) |
No output schema declared.
No examples provided.
vault_subscribe_pro ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| computeApiKey | string | yes | Singularity compute API key (dashboard → Settings → API Keys, or minted by `agentvault login`) |
| interval | string | – | Billing period; yearly is two months free |
| plan | string | – | Plan to move to; "free" cancels at period end |
No output schema declared.
No examples provided.
vault_usage ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| computeApiKey | string | yes | Singularity compute API key (dashboard → Settings → API Keys, or minted by `agentvault login`) |
No output schema declared.
No examples provided.
verify_agent_wallet_challenge ~129
Verify a wallet-signed auth challenge and receive a short-lived session token for agent registry flows.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Session scope originally requested |
| chain | string | yes | Wallet auth chain |
| nonce | string | yes | Nonce returned by request_agent_wallet_challenge |
| payload | object | – | Optional payload object that was part of the original challenge |
| signature | string | yes | Wallet signature over the challenge message |
| signatureEncoding | string | – | hex for EVM, base64 for Solana |
| walletAddress | string | yes | Wallet address that signed the challenge |
No output schema declared.
No examples provided.
How do I install the Singularity Layer MCP server?
Singularity Layer MCP is a hosted endpoint at https://mcp.x402layer.cc/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.x402layer.cc
claude mcp add --transport http ivaavimusic-singularity 'https://mcp.x402layer.cc/mcp'
What is the Singularity Layer MCP server?
Singularity Layer MCP is listed in the public MCP registry as io.github.ivaavimusic/singularity. MCP for Singularity Layer - discover listings, manage assets, run payment flows, and use agents. This page covers its hosted endpoint (https://mcp.x402layer.cc/mcp).
Is the Singularity Layer MCP server safe to use?
Singularity Layer MCP scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Singularity Layer MCP server expose?
Singularity Layer MCP exposes 81 tools: vault_usage, vault_list_agents, vault_list_snapshots, vault_delete_snapshot, vault_subscribe_pro, and 76 more. Their descriptions and schemas cost roughly 10,211 tokens of context every time the server is loaded.
Does the Singularity Layer MCP server require authentication?
No. We connected to Singularity Layer MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Singularity Layer MCP server still maintained?
Singularity Layer MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Singularity Layer MCP server?
VerifyMCP ran 11 checks on Singularity Layer MCP, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Singularity Layer MCP: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.