mcp_info_server

A small Rust server that exposes cooperlees.com's blog posts, pages, and Cooper's resume two ways from one process: as MCP tools (for LLM clients like Claude) and as a plain HTTP route (for curl / sharing a link). Everything it serves is already public content — the endpoint itself is intentionally unauthenticated.

Deployed at https://mcp.cooperlees.com — see Deployment for how it gets there.

What it exposes

MCP tools (POST /mcp, Streamable HTTP transport)

Point any Streamable HTTP-capable MCP client at https://mcp.cooperlees.com/mcp — no auth headers, no OAuth handshake required (see Connecting an LLM TUI below for the exact command per client).

Protocol versions: this server negotiates anything from 2024-11-05 up to the current latest, 2026-07-28. Clients on 2025-06-18/2025-11-25 (today's Claude Code/Desktop, Codex CLI, Gemini CLI, etc.) get the familiar initialize handshake and an Mcp-Session-Id to carry on subsequent calls — unchanged. Clients on 2026-07-28 — the version SEP-2567 removed sessions entirely — are instead served fully statelessly: no handshake, no session ID, every request self-contained via params._meta, plain application/json replies (not SSE) for these single-response tools. A minimal example of the latter, calling tools/list cold with no prior request:

curl https://mcp.cooperlees.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -H 'Mcp-Method: tools/list' \
  -d '{
        "jsonrpc": "2.0", "id": 1, "method": "tools/list",
        "params": {
          "_meta": {
            "io.modelcontextprotocol/protocolVersion": "2026-07-28",
            "io.modelcontextprotocol/clientCapabilities": {}
          }
        }
      }'

Plain HTTP routes

Connecting an LLM TUI

The server is public and unauthenticated, so

... View full README on GitHub