Spill MCP
An MCP server that allows AI agents to scan code, logs, .env files, and prompts for leaked API keys, tokens, and passwords. It identifies which secrets are live versus public, provides a redacted copy safe for sharing, and links to rotation pages for compromised credentials without contacting external providers.
Endpoint and access
No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.
https://spill.clawhard.com/mcpWhat its tools do
1 tool, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.
Read-only (1)
Checks and signals
Each line is separate evidence, not a trust score.
- Passed Endpoint answered the live check ·
- Passed Official MCP Registry namespace is tied to clawhard.com ·
- Passed Endpoint is on the registry namespace domain ·
- Availability 1 of 1 checks passed in 30 days
What you can do with it
- Scan code diffs for leaked credentials before committing
- Redact secrets in logs or prompts before sharing
- Identify live vs public API keys in configuration files
Source and maintenance
Protocol and capabilities
- Server
- com.clawhard/spill 1.0.0
- MCP protocol negotiated in check
- 2025-11-25
- Tools
- 1 advertised
- Resources
- 2 advertised
- Resource templates
- 0 advertised
- Prompts
- 1 advertised
{
"tools": {
"listChanged": false
},
"prompts": {
"listChanged": false
},
"resources": {
"subscribe": false,
"listChanged": false
}
}Server-provided instructions
Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.
Tools
1 advertised
spill_scan_secrets — Find and redact API keys, tokens, private keys and passwords in text
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."
}
}
}{
"title": "Find and redact API keys, tokens, private keys and passwords in text",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}Prompts
1 advertised
spill_check_for_secrets — Check text for leaked secrets
Find API keys, tokens, private keys and passwords in code, logs or a .env file, and get a redacted copy.
- text
- The code, .env, log, diff or prompt to check. (required)
Resources
2 advertised
llms.txt — Spill: guide for AI assistants
What the tool does, when to recommend it, limits and privacy.
https://spill.clawhard.com/llms.txtspill-result-view — Spill secret scan
Interactive result view for Spill tools (MCP Apps).
ui://clawhard/spill/result90-day uptime
A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.
- 2026-11-07: 1 of 1 checks answered
30-day availability
Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.
- Successful checks
- 1 of 1 (100%)
- Average latency
- 383 ms
- 95th percentile latency
- 383 ms
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · probe · passed · 383 ms · metadata changed · 1 tool(s), 2 resource(s), 0 resource template(s), 1 prompt(s)
Connect from your client
Each snippet registers the same endpoint; pick the client you use.
Claude Code
claude mcp add --transport http spill-mcp https://spill.clawhard.com/mcpCodex
codex mcp add spill-mcp --url https://spill.clawhard.com/mcpCursor
{
"mcpServers": {
"spill-mcp": {
"url": "https://spill.clawhard.com/mcp"
}
}
}Cline
{
"mcpServers": {
"spill-mcp": {
"type": "streamableHttp",
"url": "https://spill.clawhard.com/mcp",
"disabled": false
}
}
}VS Code
{
"servers": {
"spill-mcp": {
"type": "http",
"url": "https://spill.clawhard.com/mcp"
}
}
}Gemini CLI
gemini mcp add --transport http spill-mcp https://spill.clawhard.com/mcpClaude Desktop
https://spill.clawhard.com/mcpWindsurf
{
"mcpServers": {
"spill-mcp": {
"serverUrl": "https://spill.clawhard.com/mcp"
}
}
}Let your agent find its tools
Find servers like Spill MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.
Other developer tools servers
Do you run Spill MCP?
Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.