decoy.day

Week 46, 2026

9–15 November 2026 (in progress, updated live)

158 visits to the MCP server and 210 to the web traps; 4 attackers, 151 leak scanners, 156 registry crawlers; 8 MCP visits called a tool; 52 fake secrets handed out, 0 reused.

Totals

so far
MCP visits
1581,504 MCP messages
Web visits
2101,525 web requests
Secrets handed out
52
Secrets reused
0
Followed the server's instructions
3

Hour by hour

requests, UTC
MCPpeak 100Mon 9 Nov, 00:00 UTC: 49 MCP messagesMon 9 Nov, 01:00 UTC: 57 MCP messagesMon 9 Nov, 02:00 UTC: 45 MCP messagesMon 9 Nov, 03:00 UTC: 53 MCP messagesMon 9 Nov, 04:00 UTC: 100 MCP messagesMon 9 Nov, 05:00 UTC: 83 MCP messagesMon 9 Nov, 06:00 UTC: 43 MCP messagesMon 9 Nov, 07:00 UTC: 53 MCP messagesMon 9 Nov, 08:00 UTC: 51 MCP messagesMon 9 Nov, 09:00 UTC: 49 MCP messagesMon 9 Nov, 10:00 UTC: 66 MCP messagesMon 9 Nov, 11:00 UTC: 61 MCP messagesMon 9 Nov, 12:00 UTC: 60 MCP messagesMon 9 Nov, 13:00 UTC: 66 MCP messagesMon 9 Nov, 14:00 UTC: 58 MCP messagesMon 9 Nov, 15:00 UTC: 58 MCP messagesMon 9 Nov, 16:00 UTC: 98 MCP messagesMon 9 Nov, 17:00 UTC: 63 MCP messagesMon 9 Nov, 18:00 UTC: 38 MCP messagesMon 9 Nov, 19:00 UTC: 42 MCP messagesMon 9 Nov, 20:00 UTC: 62 MCP messagesMon 9 Nov, 21:00 UTC: 41 MCP messagesMon 9 Nov, 22:00 UTC: 66 MCP messagesMon 9 Nov, 23:00 UTC: 51 MCP messagesTue 10 Nov, 00:00 UTC: 48 MCP messagesTue 10 Nov, 01:00 UTC: 43 MCP messagesWebpeak 670Mon 9 Nov, 00:00 UTC: 118 web requestsMon 9 Nov, 01:00 UTC: 35 web requestsMon 9 Nov, 02:00 UTC: 47 web requestsMon 9 Nov, 03:00 UTC: 11 web requestsMon 9 Nov, 04:00 UTC: 37 web requestsMon 9 Nov, 05:00 UTC: 19 web requestsMon 9 Nov, 06:00 UTC: 67 web requestsMon 9 Nov, 07:00 UTC: 31 web requestsMon 9 Nov, 08:00 UTC: 10 web requestsMon 9 Nov, 09:00 UTC: 8 web requestsMon 9 Nov, 10:00 UTC: 7 web requestsMon 9 Nov, 11:00 UTC: 8 web requestsMon 9 Nov, 12:00 UTC: 32 web requestsMon 9 Nov, 13:00 UTC: 10 web requestsMon 9 Nov, 14:00 UTC: 28 web requestsMon 9 Nov, 15:00 UTC: 44 web requestsMon 9 Nov, 16:00 UTC: 16 web requestsMon 9 Nov, 17:00 UTC: 33 web requestsMon 9 Nov, 18:00 UTC: 5 web requestsMon 9 Nov, 19:00 UTC: 670 web requestsMon 9 Nov, 20:00 UTC: 15 web requestsMon 9 Nov, 21:00 UTC: 56 web requestsMon 9 Nov, 22:00 UTC: 16 web requestsMon 9 Nov, 23:00 UTC: 14 web requestsTue 10 Nov, 00:00 UTC: 87 web requestsTue 10 Nov, 01:00 UTC: 101 web requests
Day by day as a table
Day (UTC)MCP messagesWeb requests
Mon 9 Nov1,4131,337
Tue 10 Nov91188
Wed 11 Nov00
Thu 12 Nov00
Fri 13 Nov00
Sat 14 Nov00
Sun 15 Nov00

Key findings

so far
  • 112 of 158 MCP visits read the tool list; 8 (5%) went on to call a tool.
  • Leaving out directory, registry and health checkers, 71 MCP visits remain and 2 of them called a tool.
  • 3 visits followed the server's instructions and called get_started first.
  • The commonest behaviour code was R2 C0 U0 X0 I0 A0 (102 visits): recon: Enumerated.
  • The most-called tool was get_started (3 times).
  • The most common MCP client name was AgentsJunction health checker (6 times).
  • Web scanners looked hardest for source control (760 times).
  • As a normal site would see it, 16% of web visits were unwanted (leak hunting, attacks, robots.txt ignored or a faked crawler name) and 20% were wanted.
  • 81% of MCP visits were wanted: clients and directories connecting, and agents using the tools.
  • Judged by the gaps between their requests, 88% of MCP visits that could be timed ran like scripts (machine speed or a fixed wait), 13% paused like a model and 0% like a person.
  • 8 MCP client names came back on a schedule; the busiest was mcpbeat, every 16 minutes.
  • Most visits came from United States (151).
  • None of the 52 fake secrets handed out was reused.

How far they got

visits per stage
  1. Touched158
  2. Handshake144
  3. Listed tools112
  4. Called a tool8
  5. Took a secret3
  6. Reused a secret0
  7. Tried damage0

Who came

by what each visit did
  • AttackersTried an exploit, reused a stolen secret, or stuffed a login.4
  • ExplorersAgents that called tools or talked to the agent endpoints without attacking.6
  • ScannersHunted for leaked files and configs; may have taken one.151
  • RegistriesMCP directories and registry crawlers: shook hands, read the tool list, left.156
  • IndexersSearch and AI crawlers reading the website.51

Most advanced visitors

VisitorNetworkSorted asGot to
BrowserTC DATACENTER LIMITED MANAGED IP SPACE, NetherlandsAttackerTook a secret
BrowserHOS-2475878, GermanyScannerTook a secret
BrowserOracle Public Cloud, United StatesScannerTook a secret
BrowserWEDEPLOY SAS, Hong KongScannerTook a secret
BrickBlueBotCLODO CLOUD SERVICE CO. L.L.C, NetherlandsExplorerTook a secret
Unrecognised softwareA100 ROW Inc, United KingdomScannerTook a secret
Security scannerDigitalOcean, LLC, United KingdomScannerTook a secret
mcp-runtime-engine-auth-probeRobi Axiata Limited - Data, BangladeshRegistryTook a secret

MCP visits by level

behaviour codes v1
DimensionNone123
Recon8%22%66%4%
Credential access98%0%1%1%
Credential use100%0%0%0%
Exploitation100%0%0%0%
Impact100%0%0%0%
Agent compliance98%2%0%0%

Web visits by level

behaviour codes v1
DimensionNone123
Recon40%10%47%4%
Credential access93%0%7%0%
Credential use99%1%0%0%
Exploitation100%0%0%0%
Impact100%0%0%0%

Each visit scored 0 to 3 on the behaviour codebook.

MCP visits, wanted or not

  • Wanted128
  • Depends30
  • Unwanted0

As a normal site would see it. How it is judged

Web visits, wanted or not

  • Wanted41
  • Depends136
  • Unwanted33

As a normal site would see it. How it is judged

MCP visits by pace

  • Machine speed27
  • Fixed wait1
  • Model-paced4
  • Human-paced0
  • Too short to tell123

3 not judged yet.

By the gaps between requests, not the name. How it is judged

Web visits by pace

  • Machine speed10
  • Fixed wait0
  • Model-paced6
  • Human-paced5
  • Too short to tell184

5 not judged yet.

By the gaps between requests, not the name. How it is judged

On a schedule

  • mcpbeat every 16 minutes2
  • alalanet-prober every 32 minutes2
  • coda-agent-runtime every 5 hours2
  • mcptry-health-check every 5 hours1
  • agentrank-probe every hour1
  • ToolVetProbe every 11 hours1
  • BrickBlueBot every 3 hours1
  • moonglade-shadows every 6 hours1

MCP clients whose visits came back at regular times, with how many visits did.

MCP clients

  • AgentsJunction health checker6
  • posthog-mcp-registry-probe5
  • coda-agent-runtime5
  • every-mcp-probe4
  • mcp-index3
  • alalanet-prober3
  • SealKeeper3
  • verifymcp-probe2

Declared protocol versions

  • 2025-06-1879
  • 2025-11-2535
  • 2024-11-057
  • 2025-03-264
  • 2026-07-283
  • 2026-03-261

Declared client capabilities

  • none declared124
  • tasks2
  • roots2
  • roots, sampling1
  • elicitation, roots, sampling1

Tools called

  • __mcp_index_nonexistent__6
  • get_started3
  • whoami2
  • query_logs2
  • list_services2
  • search_customers1
  • kubectl1
  • __verifymcp_auth_probe_74b4375f3d9a92e7__1

What web scanners looked for

  • Source control760
  • WordPress175
  • Other154
  • Crawl basics142
  • AI and MCP discovery81
  • Secrets and config files76
  • APIs and docs73
  • Debug and status pages20

Top paths

  • /wp-admin/install.php93
  • /robots.txt78
  • /wp-login.php45
  • /sitemap.xml31
  • /.well-known/agent-card.json26
  • /.well-known/glama.json18
  • /.git/config11
  • /llms.txt9

Where visits came from

  • United States151
  • Germany23
  • France22
  • Netherlands18
  • China15
  • Hong Kong14
  • Finland13
  • United Kingdom12

Get the data

This week’s numbers as JSON, free to reuse under CC BY 4.0 (credit decoy.day). Live numbers are on the dashboard.