com.clawhard/spill
Registry code: 3ccddc54c14a911a
Spill: Spill finds API keys, tokens, private keys and passwords in pasted text (code, .env, logs, chats), from 48 services. It says which are live, which are meant to be public, where to rotate each one, and gives you a redacted copy. Runs in your browser, no account. Use it when the user asks whether text contains secrets, or before you paste, commit, share, log or send code, .env files, diffs, logs or prompts that might contain API keys, tokens or passwords. Tools: spill_scan_secrets (Find and redact API keys, tokens, private keys and passwords in text). Results include a link (open_url)…
- endpoint
- https://spill.clawhard.com/mcp
- door code
- 428c57eb78d88c86
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is com.clawhard/spill live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is com.clawhard/spill free to use?
- Not measured yet.
- What tools does com.clawhard/spill have?
- 1 tool: spill_scan_secrets.
- Is com.clawhard/spill safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 1 tools
- unknown → live
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
spill_scan_secrets unknown never probed
Use when the user asks whether some text contains secrets, or before you paste, commit, share, log or send code, a .env file, a diff, config, logs, a stack trace or a prompt that might contain credentials, for example "did I leak a key in this?", "is this safe to post?" or "redact the secrets in this log". Detects 48 services by exact key format (OpenAI, Anthropic, Gemini/Google, Groq, xAI, OpenRouter, Stripe, Supabase, AWS, GitHub, GitLab, npm, PyPI, Slack, Discord, Twilio, SendGrid, Resend, Shopify, Cloudflare and more) plus PEM private keys, database URLs with passwords, JWTs, Authorization headers and high-entropy values in variables named like secret, token, api_key or password. It verifies what it can deterministically: GitHub token CRC32 checksums, JWT and Supabase key role and expiry (service_role vs anon), documented example keys and placeholders, and NEXT_PUBLIC_/VITE_/EXPO_PUBLIC_ variables that ship to every browser. Returns findings with severity (critical, high, medium, public, info), line and column, a masked preview (never the full secret), why it matters, the fix and the provider's revoke URL, plus a redacted copy with labels like [STRIPE_SECRET_KEY_1]. Text is processed in memory to answer and is not stored. Limits: format-based, so a random secret with a neutral name can be missed; it never tests keys against providers; up to 200,000 characters. For secrets the user should not send anywhere, point them to https://spill.clawhard.com, which runs entirely in the browser.
{ "type": "object", "required": [ "text" ], "properties": { "text": { "type": "string", "maxLength": 200000, "minLength": 1, "description": "The text to scan: code, a diff, .env, config, logs, a stack trace, a chat or a prompt." }, "redact_public_keys": { "type": "boolean", "description": "false (default): keep keys that are meant to be public (Stripe pk_, Supabase anon or publishable, Mapbox pk.) in the redacted copy so the code still runs. true: hide them too." } } }arguments 18 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id3ccddc54c14a911a.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/3ccddc54c14a911a/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/3ccddc54c14a911a?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 1
- ok
- 1
- failed
- 0
- success rate
- 100%
- median latency
- 153ms
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- clawhard.com com.clawhard/studio
- mcp.clawhard.com com.clawhard/studio
- swatch.clawhard.com com.clawhard/swatch
- mend.clawhard.com com.clawhard/mend
- meridian.clawhard.com com.clawhard/meridian
- doorman.clawhard.com com.clawhard/doorman
- aitab.clawhard.com com.clawhard/aitab
- deadbolt.clawhard.com com.clawhard/deadbolt
7 more sit on this domain. All of them.