mcpbeat

Inlay MCP Server

io.github.cartoonitunes/inlay
not responding

Inlay is listed as active in the registry but did not answer our last check. Last commit 17 Feb 2026.

Make any website discoverable by AI agents via MCP, llms.txt, and structured data.

Uptime history 43 hours of history · worst hour 0%
43 hours agonow
1.1%
Uptime 24h
1 of 91 checks
Tools
hidden behind auth
92 ms
Response time
average over 24h
1
Stars
last commit 17 Feb 2026

Connect this server

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

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

Endpoints

URLTransportStateLatencyChecked
https://inlay.dev/api/mcp/{site_key} sse answering 93 ms 10 min ago

Inlay — questions

Answers built from our own checks of this server.

Is Inlay working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 1 of 91 checks got a reply (1.1%), average response time 92 ms. The bar chart above shows every period we have measured.
The registry lists Inlay as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Inlay?
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 Inlay need an API key?
No. Inlay completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.
How fast is Inlay?
It answers our handshake in 92 ms on average, which is faster than 86% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Inlay open source?
Yes — it is published under the MIT licence, written in Shell and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.