Koskamo

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.

Spill MCP logo, by Clawhard StudioVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by Clawhard Studio
MCP endpoint (Streamable HTTP)
https://spill.clawhard.com/mcp
Vendor documentation

What its tools do

1 tool, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (1)

1 of 1 have a description · 1 of 1 declare behavior hints · 1 of 1 with parameters document them all

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

Vendor evidenceRegistry 1.0.0

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
Server-advertised capabilities
{
  "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.

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) that the user can open to see the same result on the website.

Tools

1 advertised

spill_scan_secrets — Find and redact API keys, tokens, private keys and passwords in text
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

spill_scan_secrets input schema
{
  "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."
    }
  }
}
spill_scan_secrets annotations
{
  "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

Advertised by the server during the last successful anonymous check.

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

Advertised by the server during the last successful anonymous check.

What the tool does, when to recommend it, limits and privacy.

llms.txt URI
https://spill.clawhard.com/llms.txt

MIME type: text/markdown

spill-result-view — Spill secret scan

Advertised by the server during the last successful anonymous check.

Interactive result view for Spill tools (MCP Apps).

spill-result-view URI
ui://clawhard/spill/result

MIME type: text/html;profile=mcp-app

90-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.

Too few checks for a percentage yet (1 of 1 answered).

  1. 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.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http spill-mcp https://spill.clawhard.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add spill-mcp --url https://spill.clawhard.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable spill-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "spill-mcp": {
      "url": "https://spill.clawhard.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "spill-mcp": {
      "type": "streamableHttp",
      "url": "https://spill.clawhard.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start spill-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "spill-mcp": {
      "type": "http",
      "url": "https://spill.clawhard.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http spill-mcp https://spill.clawhard.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://spill.clawhard.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "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.

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.

Claim this listing