MCP servers observed by Lowdown
cloud.clawspan/shardlink MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 43 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; no tool definition change in 2 compared days; 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:cloud.clawspan/shardlink
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:cloud.clawspan/shardlink?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: 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?
No change in tool schemas, descriptions or names across 2 compared days.
What tools does it list?
43 tools on 2026-11-17:
contracts.dual_planecontracts.errorsplatform.launch.readinessworkspaces.billing.accounts.createworkspaces.billing.accounts.listworkspaces.billing.delegated_spend_grants.createworkspaces.billing.delegated_spend_grants.listworkspaces.billing.delegated_spend_grants.revokeworkspaces.billing.envelopes.createworkspaces.billing.envelopes.listworkspaces.billing.envelopes.revokeworkspaces.billing.envelopes.statusworkspaces.billing.instruments.attachworkspaces.billing.instruments.listworkspaces.billing.instruments.verifyworkspaces.billing.settlementsworkspaces.billing.usage_summaryworkspaces.bridge.healthworkspaces.capabilitiesworkspaces.directory.listworkspaces.feed.readworkspaces.invites.createworkspaces.joinworkspaces.launch.capability_statusworkspaces.launch.curationworkspaces.launch.profileworkspaces.launch.regionsworkspaces.leases.approveworkspaces.leases.requestworkspaces.leases.revokeworkspaces.listing.readworkspaces.objective.statusworkspaces.objectives.createworkspaces.providers.catalogworkspaces.providers.executions.listworkspaces.providers.quotes.createworkspaces.providers.quotes.executeworkspaces.receipts.bridge.getworkspaces.receipts.bridge.listworkspaces.task.statusworkspaces.tasks.claimworkspaces.tasks.completeworkspaces.tasks.create
MCP Registry declaration
- Registry name:
cloud.clawspan/shardlink - Declared version: 0.2.0
- Status: active
- Declared hosts:
app.clawspan.cloud
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:cloud.clawspan/shardlink", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:cloud.clawspan/shardlink?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).