MCP servers observed by Lowdown
io.github.ivaavimusic/singularity MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 78 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-13 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.ivaavimusic/singularity
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.ivaavimusic/singularity?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 2 compared days.
- 2026-11-13: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 63 → 78
What tools does it list?
78 tools on 2026-11-16:
browse_marketplacecloud_credit_activitycloud_credit_balancecloud_deploy_machinecloud_deploy_podcloud_deploy_processorcloud_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_chatcloud_pod_execcloud_pod_filescloud_pod_usagecloud_pod_write_filecloud_processor_runscloud_start_training_runcreate_campaigncreate_dataset_with_paymentcreate_endpoint_with_paymentcreate_invoicecreate_payment_linkdelete_endpointfinalize_agent_registrationfinalize_agent_updateget_agentget_agent_registry_infoget_dataset_statusget_endpoint_detailsget_endpoint_statsget_featuredget_invoiceget_listingget_payment_linkget_top_ratedlist_agentslist_categorieslist_dataset_pricinglist_invoiceslist_my_agent_bindable_endpointslist_my_campaignslist_my_endpointslist_my_productslist_my_registered_agentslist_networkslist_payment_linkslist_paymentsprepare_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
MCP Registry declaration
- Registry name:
io.github.ivaavimusic/singularity - Declared version: 1.16.0
- Status: active
- Declared hosts:
mcp.x402layer.cc
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.ivaavimusic/singularity", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.ivaavimusic/singularity?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).