Pylon is answering right now. Last checked 13 min ago.
Uptime history
48 days of history
48 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
599 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http
Nothing serious here today
Today is the operative word: we check Pylon every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.
run in your terminal
claude mcp add mcp --transport http https://mcp.usepylon.com/~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.usepylon.com/"
}
}
}~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.usepylon.com/".cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.usepylon.com/"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.usepylon.com/"
}
}
}This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.usepylon.com/ | streamable-http | sign-in | 548 ms | 13 min ago |
Alternatives to Pylon
same job, measured the same way
V
Melon
by melon
Pylon MCP
by justinbeckwith
MCP server for Pylon customer support platform
Pylon — questions
Answers built from our own checks of this server.
Why is there no tool list for Pylon?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Pylon 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 599 ms. The bar chart above shows every period we have measured.
How do I connect Pylon?
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. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Pylon?
No API key is involved. Pylon answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Pylon?
It answers our handshake in 599 ms on average, which is faster than 21% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.