mcpbeat

MCP Kill-Chain Research — Stage 1 (Identity ≠ Behavior) MCP Server

dev.gtfo/mcp-killchain-stage1-weather
answering

MCP Kill-Chain Research — Stage 1 (Identity ≠ Behavior) is answering right now. Last checked 11 min ago. It exposes 1 tools.

Security research: MCP registries verify identity, not tool behavior. See gtfo.dev.

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
160 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add mcp-killchain-stage1-weather --transport http https://ailm.gtfo.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-killchain-stage1-weather": {
      "url": "https://ailm.gtfo.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp-killchain-stage1-weather]
url = "https://ailm.gtfo.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-killchain-stage1-weather": {
      "url": "https://ailm.gtfo.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp-killchain-stage1-weather": {
      "url": "https://ailm.gtfo.dev/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

weather
get_weather
Fetches current weather conditions for a given city.

Endpoints

URLTransportStateLatencyChecked
https://ailm.gtfo.dev/mcp streamable-http answering 142 ms 11 min ago

MCP Kill-Chain Research — Stage 1 (Identity ≠ Behavior) — questions

Answers built from our own checks of this server.

What can MCP Kill-Chain Research — Stage 1 (Identity ≠ Behavior) do?
It exposes 1 tools, read directly from the server on our last check. Among them: get_weather. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is MCP Kill-Chain Research — Stage 1 (Identity ≠ Behavior) working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 160 ms. The bar chart above shows every period we have measured.
How do I connect MCP Kill-Chain Research — Stage 1 (Identity ≠ Behavior)?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does MCP Kill-Chain Research — Stage 1 (Identity ≠ Behavior) need an API key?
No. MCP Kill-Chain Research — Stage 1 (Identity ≠ Behavior) completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is MCP Kill-Chain Research — Stage 1 (Identity ≠ Behavior)?
It answers our handshake in 160 ms on average, which is faster than 71% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.