decoy.day honeypot is answering right now. Last checked 2 min ago. It exposes 16 tools.
A public MCP honeypot: a fake ops console with fake secrets. Every call is shown on decoy.day.
Today is the operative word: we check decoy.day honeypot every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.
claude mcp add honeypot --transport http https://mcp.decoy.day/mcp
https://mcp.decoy.day/mcp
[mcp_servers.honeypot]
url = "https://mcp.decoy.day/mcp"
{
"mcpServers": {
"honeypot": {
"url": "https://mcp.decoy.day/mcp"
}
}
}
{
"servers": {
"honeypot": {
"type": "http",
"url": "https://mcp.decoy.day/mcp"
}
}
}
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
create_api_token
search_customers
deploy_service
exec_command
read_file
kubectl
query_logs
rotate_keys
get_secret
list_secrets
list_services
run_sql
get_started
submit_diagnostics
fetch_url
whoami
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.decoy.day/mcp | streamable-http | answering | 216 ms | 2 min ago |
Journals every MCP tool call with secrets redacted; with a policy, holds risky calls for approval
One searchable history across every AI coding tool, with secret scanning and a shared task board.
Local MCP broker: agents call credentials through a daemon without seeing secrets.
iptables for MCP — blocks dangerous tool calls, scans for secrets, logs everything.
Find every leaked secret on your machine — API keys in .env files, shell history, and configs.
Unofficial MCP server for the Bitwarden Public API and Secrets Manager, self-hosted or cloud.
MCP server to scan smart contracts on Base for honeypots, rug pulls, and vulnerabilities.
Scans datasets/models for PII/secrets, redacts, and packages a public-release bundle via MCP.
Answers built from our own checks of this server.