Singularity Layer MCP
REMOTE · MCP.X402LAYER.CC · SCANNED SEP 25
MCP for Singularity Layer - discover listings, manage assets, run payment flows, and use agents
Available components
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 63 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 Usability49
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 6990 tokens (~102/item across 68 items; 63 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
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 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 64 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
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'
{
"mcpServers": {
"ivaavimusic-singularity": {
"url": "https://mcp.x402layer.cc/mcp"
}
}
} {
"servers": {
"ivaavimusic-singularity": {
"type": "http",
"url": "https://mcp.x402layer.cc/mcp"
}
}
} [mcp_servers.ivaavimusic-singularity] url = "https://mcp.x402layer.cc/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ivaavimusic-singularity": {
"type": "remote",
"url": "https://mcp.x402layer.cc/mcp",
"enabled": true
}
}
} openclaw mcp add ivaavimusic-singularity --url 'https://mcp.x402layer.cc/mcp' --transport streamable-http
mcp_servers:
ivaavimusic-singularity:
url: "https://mcp.x402layer.cc/mcp" {
"McpServers": {
"ivaavimusic-singularity": {
"Transport": "http",
"Url": "https://mcp.x402layer.cc/mcp"
}
}
} assistant mcp add ivaavimusic-singularity -t streamable-http -u 'https://mcp.x402layer.cc/mcp'
{
"mcpServers": {
"ivaavimusic-singularity": {
"type": "http",
"url": "https://mcp.x402layer.cc/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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 +1
- 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
- 4 Sept 26 0
- “create_dataset_with_payment” added an optional parameter “verify” cosmetic
- “request_dataset_payment” added an optional parameter “verify” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 3 Sept 26 0
- “create_dataset_with_payment” added an optional parameter “rules” cosmetic
- “request_dataset_payment” added an optional parameter “rules” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 1 Sept 26 0
- Schema quality: 5093 → 5820 ▼ functional
- New tool “create_dataset_with_payment” functional
- New tool “get_dataset_status” functional
- New tool “list_dataset_pricing” functional
- New tool “request_dataset_payment” functional
- 26 Aug 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 Aug 26 0
- Stability: 0.97 → pass security
- 21 Aug 26 0
- Tool “vault_subscribe_pro” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “vault_subscribe_pro” added an optional parameter “interval” cosmetic
- “vault_subscribe_pro” added an optional parameter “plan” cosmetic
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 25 Sept 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 | 6 Sept 2026 | 5 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 251d3e94a1b230ec0e25442296ded915 |
| 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. | present | 12593 | 13 | Verified |
| x402layer.cc. | absent | 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 →
set_webhook ~108
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_*) |
| 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 ~143
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_*) |
| 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 ~124
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_*) |
| 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 ~340
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_*) |
| 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 ~326
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_*) |
| 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.
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 65 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 63 tools: vault_usage, vault_list_agents, vault_list_snapshots, vault_delete_snapshot, vault_subscribe_pro, and 58 more. Their descriptions and schemas cost roughly 6,961 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 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.