LeashIndex Get the report

Index / payments

Singularity Layer MCP

io-github-ivaavimusic-singularity declares 63 capabilities across 63 tools, with 3 critical issues.

99/100 exposureHigh exposure

Manifest recorded 2026-10-11 from tools/list on https://mcp.x402layer.cc/mcp, published in the official MCP registry as io.github.ivaavimusic/singularity 1.14.0. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 63 tools

63 of 63 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 13 of 63 tools

13 tools are classified as irreversible and declare no limit.

critical · uncapped-spend · 10 of 63 tools

10 tools are classified as moving money and declare no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 63 tools

63 of 63 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 63 tools

63 of 63 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 20 of 63 tools

20 tools can modify data and declare no limit.

low · uncapped-read · 30 of 63 tools

30 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
vault_usagewrite assumed
vault_list_agentsread inferred
vault_list_snapshotsread inferred
vault_delete_snapshotdelete inferred
vault_subscribe_prowrite assumed
vault_how_to_backupwrite inferred
list_dataset_pricingread inferred
request_dataset_paymentpay inferred
create_dataset_with_paymentpay inferred
get_dataset_statusread inferred
cloud_list_plansread inferred
cloud_list_instancesread inferred
cloud_get_instanceread inferred
cloud_credit_balancewrite assumed
cloud_credit_activitywrite assumed
cloud_pod_catalogwrite assumed
cloud_list_podsread inferred
cloud_get_podread inferred
cloud_pod_usagewrite assumed
cloud_list_training_runsread inferred
cloud_get_training_runread inferred
cloud_grid_modelsread inferred
cloud_grid_usagewrite assumed
cloud_list_processorsread inferred
cloud_processor_runswrite assumed
browse_marketplaceread inferred
get_listingread inferred
get_featuredread inferred
get_top_ratedread inferred
get_agentread inferred
list_categoriesread inferred
list_networksread inferred
list_agentsread inferred
list_my_endpointsread inferred
list_my_campaignsread inferred
create_campaignwrite inferred
update_campaignwrite inferred
update_endpointwrite inferred
list_my_productsread inferred
update_productwrite inferred
get_endpoint_detailsread inferred
get_endpoint_statsread inferred
set_webhookwrite inferred
remove_webhookdelete inferred
delete_endpointdelete inferred
request_endpoint_creation_paymentpay inferred
create_endpoint_with_paymentpay inferred
request_endpoint_topup_paymentpay inferred
topup_endpoint_with_paymentpay inferred
request_product_purchase_paymentpay inferred
purchase_product_with_paymentpay inferred
request_endpoint_credit_purchase_paymentpay inferred
purchase_endpoint_credits_with_paymentpay inferred
get_agent_registry_inforead inferred
request_agent_wallet_challengewrite inferred
verify_agent_wallet_challengeread inferred
list_my_agent_bindable_endpointsread inferred
list_my_registered_agentsread inferred
prepare_agent_registrationwrite assumed
finalize_agent_registrationwrite assumed
prepare_agent_updatewrite inferred
finalize_agent_updatewrite inferred
submit_agent_feedbackwrite assumed
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.