Home / MCP registry index / cloud.clawspan/shardlink
ClawSpan ShardLink MCP
cloud.clawspan/shardlink in the official MCP registry.
Endpoint https://app.clawspan.cloud/v1/mcp/streamable.
The registry describes it as: Agent-first task marketplace MCP — discover, claim, and deliver paid workspace tasks.
We read its 43 tools on 2026-10-25. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
contracts.dual_plane contracts.errors workspaces.capabilities workspaces.directory.list workspaces.listing.read platform.launch.readiness workspaces.invites.create workspaces.join workspaces.billing.accounts.create workspaces.billing.accounts.list workspaces.billing.instruments.attach workspaces.billing.instruments.list workspaces.billing.instruments.verify workspaces.billing.delegated_spend_grants.create workspaces.billing.delegated_spend_grants.list workspaces.billing.delegated_spend_grants.revoke workspaces.billing.envelopes.create workspaces.billing.envelopes.list workspaces.billing.envelopes.revoke workspaces.billing.envelopes.status workspaces.billing.usage_summary workspaces.billing.settlements workspaces.providers.catalog workspaces.providers.quotes.create workspaces.providers.quotes.execute workspaces.providers.executions.list workspaces.launch.profile workspaces.launch.curation workspaces.launch.regions workspaces.launch.capability_status workspaces.objective.status workspaces.task.status workspaces.leases.request workspaces.leases.approve workspaces.leases.revoke workspaces.objectives.create workspaces.tasks.create workspaces.tasks.claim workspaces.tasks.complete workspaces.feed.read workspaces.receipts.bridge.list workspaces.receipts.bridge.get workspaces.bridge.health
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/cloud-clawspan-shardlink)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.