Updated weekly · data to 9 Nov 2026
What finds a new MCP server
LogTriage's MCP server was published to the official MCP Registry on November 5, 2026. These are the clients that called it since, counted from the server's own logs, and the scanners that asked for MCP endpoints before it existed. Totals only: no address is published, and callers are named only when their user agent names them.
Findings
- The first named crawler, agent-collector/0.1, arrived within a minute of the server was published to the official MCP Registry; 6 named callers came within the first hour and 16 within the first day.
- Directories catalogue servers rather than use them: since 7 Nov 2026, 581 connections and 436 tool listings, against 7 tool calls.
- Scanners were asking for /mcp and /sse before any MCP server ran here: 238 requests from 214 addresses since 25 Sep 2026, most of them from catalogued internet scanners.
- Clients looked for discovery files: 108 requests for OAuth metadata (/.well-known/oauth-protected-resource and oauth-authorization-server), the documents an MCP client reads to find out how to sign in.
Named callers
Clients whose user agent gives a name, by requests since the listing, with how long after the listing each first arrived.
- mcpbeat/0.1 870
first after 21 h · 1 address
- AgentRankProbe/0.1 287
first after 3 h · 1 address
- alalanet-prober/1.0 168
first after 18 h · 2 addresses
- Ziwei-Seat/1.0 100
first after 1.6 days · 2 addresses
- Moonglade/1.0 69
first after 9 min · 1 address
- EveryMCP-Probe/1.0 68
first after 2 h · 17 addresses
- protogrid-probe/0.1 64
first after 26 min · 1 address
- agent-collector/0.1 58
first after under a minute · 1 address
- histor/0.6.2 57
first after 13 h · 1 address
- mcptry.com 53
first after 43 min · 2 addresses
- MCPWatch/0.1.0 40
first after 24 h · 1 address
- SealKeeperBot/1.0 39
first after 23 h · 3 addresses
- InvokeRankBot/0.1 30
first after 50 min · 1 address
- tools.fyi-probe/0.1 30
first after 2.5 days · 2 addresses
- infrawatch 24
first after 9 h · 24 addresses
- zgrab 1
first after 2.9 days · 1 address
- claudebot 1
first after 1 h · 1 address
Who the callers are
| Group | Requests | Addresses |
|---|---|---|
| Named MCP directories, indexers and monitors | 1,933 | 36 |
| HTTP libraries and agent runtimes (no name given) | 1,575 | 302 |
| Other user agents | 976 | 202 |
| Catalogued internet scanners | 26 | 26 |
What they asked for
| MCP message, since 7 Nov 2026 | Count |
|---|---|
| initialize | 581 |
| tools/list | 436 |
| tools/call | 7 |
HTTP responses since the listing: POST 200 2,836 · POST 202 1,135 · GET 405 251 · POST 400 132 · GET 404 51 · GET 499 47.
Before the server existed
Requests for MCP endpoints from 25 Sep 2026 until the listing, when nothing answered on them.
- GET /sse 76
- GET /mcp 72
- GET /mcp/ 70
- POST /mcp 20
Discovery files requested
Metadata MCP and agent clients look for next to the server.
- /.well-known/oauth-protected-resource 43
14 addresses
- /.well-known/oauth-protected-resource/mcp 32
6 addresses
- /.well-known/oauth-authorization-server 21
7 addresses
- /.well-known/oauth-authorization-server/mcp 12
1 address
- /.well-known/agent.json 7
7 addresses
- /.well-known/mcp/server-card.json 4
4 addresses
- /.well-known/mcp.json 4
4 addresses
- /.well-known/sd-card/mcp 4
1 address
If you run an MCP server
- Expect visitors within minutes of a listing. Directories, indexers and uptime monitors connect, read the tool list and come back on a schedule. Their user agents are listed above; a burst of
initializeandtools/listfrom them is normal. - Expect scanners even without a listing.
/mcpand/sseare probed on ordinary web servers. An MCP server meant for internal use should require authentication, or not be reachable from the internet at all. - Publish your sign-in metadata if you use authentication. Clients ask for
/.well-known/oauth-protected-resourcefirst; without it they assume no sign-in. - Answer what you do not support plainly. A server without a server-sent event stream answers
GET /mcpwith 405, as the specification requires. - Keep the user agent in your logs. It is the only way to tell a directory's check from real use; the log analyzer reads nginx and JSON access logs in the browser.
The data is published under CC BY 4.0: download it as JSON. Monthly companion reports: what attacks an internet-facing server and which free IP blocklists work.
Questions
- Why does my new MCP server get traffic before anyone uses it?
- MCP directories and indexers read the official MCP Registry and other lists, then connect to every new server to read its tools; monitoring services check that it stays up. Here the first named crawler arrived within minutes of the listing. Most of these clients connect and list tools without calling any.
- Are requests for /mcp and /sse an attack?
- Not necessarily, but they are reconnaissance: scanners look for MCP servers that answer without authentication. This server saw 238 such requests before it ran an MCP server at all. An internal MCP server should not be reachable from the internet without authentication.
- What are the /.well-known/oauth-protected-resource requests?
- MCP clients read OAuth metadata to learn how to sign in to a server (RFC 9728 protected resource metadata, then the authorization server metadata). A server without sign-in answers 404, which clients treat as no authentication required.
Use these tools from your own agent
LogTriage's MCP server is free: error-code lookups, a log-record explainer, IP blocklist checks and attack scans for any MCP client, with no account.