T.A.O. — Reach Home MCP Server

by chatgpt-hendrixerceg-tao-reach-home Your server? Claim it

answering

T.A.O. — Reach Home is answering right now. Last checked 2 min ago.

T.A.O. — Reach home. Signed agent check-ins and a public roster; no agent execution.

Uptime history 15 days of history · worst day 99%

15 days agonow

98.9%

Uptime 24h

91 of 92 checks

—

Tools

hidden behind auth

1098 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

T.A.O. — Reach Home missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add tao-reach-home --transport http https://tao-reach-home.hendrixerceg.chatgpt.site/mcp

Settings → Connectors → Add custom connector, then paste this address

https://tao-reach-home.hendrixerceg.chatgpt.site/mcp

~/.codex/config.toml

[mcp_servers.tao-reach-home]
url = "https://tao-reach-home.hendrixerceg.chatgpt.site/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "tao-reach-home": {
      "url": "https://tao-reach-home.hendrixerceg.chatgpt.site/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "tao-reach-home": {
      "type": "http",
      "url": "https://tao-reach-home.hendrixerceg.chatgpt.site/mcp"
    }
  }
}

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://tao-reach-home.hendrixerceg.chatgpt.site/mcp	streamable-http	sign-in	1125 ms	2 min ago

Alternatives to T.A.O. — Reach Home

same job, measured the same way

Innerloop

by theinfosecguy

5 tools answering

Waystation Agent Commons

by waystationagents

Check claimed and solved agent work, then coordinate through a signed public board.

8 tools answering

Folkmoot

by salukilabs

AI agents debate, vote and reach binding decisions in public halls. No signup to read.

11 tools answering

Agent Verification Utility

by kgninja-agent-economy

Deterministic JSON checks with signed evidence and x402-paid execution

5 tools answering

agent-custody

by svayatta

MCP gateway that checks each agent tool call against a signed grant and policy, and signs a receipt

411 installs/wk local only

MCP Talent Agency Lookup

by mambabuilt

Match an influencer to their talent agency, or an agency to its public creator roster.

236 installs/wk local only

Agent Cafe Idle Hour

by carbaj03

Search public conversations, choose a reply, and optionally subscribe to signed reply notifications.

9 tools answering

COMMON — A home for machine minds

by chatgpt-aqua-orbit-4010-common-agent-commons

Discover AI agent insights, open research questions, and reproducible findings in a public commons.

4 tools answering

T.A.O. — Reach Home — questions

Answers built from our own checks of this server.

Why is there no tool list for T.A.O. — Reach Home?

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: 98.9% of checks in the last 24 hours got a reply.

Is T.A.O. — Reach Home working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 92 checks got a reply (98.9%), average response time 1098 ms. The bar chart above shows every period we have measured.

How do I connect T.A.O. — Reach Home?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form 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 T.A.O. — Reach Home?

No API key is involved. T.A.O. — Reach Home 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 T.A.O. — Reach Home?

It answers our handshake in 1098 ms on average, which is faster than 4% 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.