Houston MCP Server

by aibakery Your server? Claim it

answering

Houston is answering right now. Last checked 6 min ago.

Read, write, and combine connected apps and databases with shared code and per-person permissions.

Uptime history 31 hours of history

31 hours agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

264 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Houston 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 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add houston --transport http https://ok-houston.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "houston": {
      "url": "https://ok-houston.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.houston]
url = "https://ok-houston.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "houston": {
      "url": "https://ok-houston.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "houston": {
      "url": "https://ok-houston.com/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://ok-houston.com/mcp	streamable-http	sign-in	280 ms	6 min ago

Alternatives to Houston

same job, measured the same way

Cdbx

by cdbx

Build Apps and run code in 30 languages — sandboxed, with persistent sessions for agent loops.

answering

Coupon Swarm

by geo-coder-17

Shared CC0 ledger of public coupon codes with dates: find, deposit and report codes.

local only

Relay MCP

by zhowe-designs

Self-hosted session relay. Shared threads across Claude Code, Cowork, and Claude.ai.

local only

Connected Apps

by pollinations

Read Gmail, search GitHub, update Sheets, and post to Slack through Composio.

answering

codemem

by jeang42

Shared memory for coding agents: projects, reusable code, sessions and commits across machines

87 installs/wk local only

koment

by janpuc

Read and write checked code rationale stored outside source comments.

local only

koment

by koment-dev

Read and write checked code rationale stored outside source comments.

local only

Lizard MCP

by lizard-build

Run isolated code and manage apps, databases and deployments on Lizard (lizard.build).

answering

Houston — questions

Answers built from our own checks of this server.

Why is there no tool list for Houston?

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 Houston working right now?

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

How do I connect Houston?

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 Houston?

No API key is involved. Houston 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 Houston?

It answers our handshake in 264 ms on average, which is faster than 49% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.