Intent Hub is answering right now. Last checked 5 min ago. It exposes 10 tools.
Book a local business by saying what you need; matching businesses bid and you confirm one.
The linked repository no longer exists on GitHub — it was deleted or made private.
Uptime history
22 hours of history
22 hours agonow
100.0%
Uptime 24h
80 of 80 checks
10
Tools
read from the server
188 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 6
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 September 2026. No other catalogue keeps this.
18 Sep
3 tools appeared
confirm_phone, link_phone, unlink_phone
18 Sep
2 tool descriptions were rewritten
confirm_booking, find_offers
18 Sep
a tool changed the parameters it asks for
confirm_booking
This one has been quiet for a while
Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.
run in your terminal
claude mcp add intent-hub --transport http https://openintentprotocol.com/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"intent-hub": {
"url": "https://openintentprotocol.com/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.intent-hub]
url = "https://openintentprotocol.com/mcp".cursor/mcp.json
{
"mcpServers": {
"intent-hub": {
"url": "https://openintentprotocol.com/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"intent-hub": {
"url": "https://openintentprotocol.com/mcp"
}
}
}Available tools 10
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
confirm
confirm_booking
Confirm a held slot with the customer's name and phone number; this is the booking. Idempotent: confirming the same hold twice books it once and tells the business once. With a linked number (link_phone) you may send `contact` with the name alone and the linked number is used; a different number in `contact.phone` is refused as `phone-mismatch`.
confirm_phone
Spend the code that link_phone texted, and tie this agent to that number. Ten minutes and five tries; a wrong code answers `invalid-code` with `attemptsLeft`, and the fifth wrong one throws the code away — call link_phone again for a new one. One number per agent: linking another replaces it.
booking
get_booking
Read the state of a session: the understood intent and its open question, the bids of the current round and every hold with its present status and link. Use it to pick up a conversation you already have a session id for.
cancel
cancel_booking
Release a held or confirmed slot of this session, so the slot is free again. Businesses that host their own agent do not offer this yet and answer `not-supported`.
capabilities
capabilities
What this hub can do, in one call: every tool by name, every resource by URI, every prompt by name, the per-client budgets, how to authenticate, the protocol revision and where the documentation is. Takes no arguments, spends no budget and reads nothing: it answers the hub's own constants, so a client that asks it first never has to guess. Called with a key it also answers who that key is.
hold
hold_slot
Hold the slot of one bid from this session's round for ten minutes, before asking the person for their details. Answers the hold, the bid it was made from and, when the hub has a public origin, the customer's private booking `link`. Never call it to browse: a hold blocks a real slot and three per client per ten minutes is the budget.
link
link_phone
Tie this agent to the phone number of the person it books for: the hub texts that number a six-digit code naming this agent, and `confirm_phone` spends it. Afterwards `confirm_booking` may leave `contact.phone` out — the linked number is used — and every booking made through this key shows up on that person's own list of bookings at /me, next to the ones they made on the site. Ask the person for their own number and never anybody else's: a code arrives on their phone with this agent's name on it. Answers `{ ok: true, sent: true }` whatever the hub knows about the number, and 3 calls per agent per hour is the budget.
offers
find_offers
Find offers from local businesses for what a person asked for. Send their sentence as `text`; the hub parses the trade, the town and the day. An answer with `complete: false` carries a `question` to put to the person: call this tool again with the same `session` and their reply as `text`. An answer with `complete: true` is one finished bidding round: `bids` ranked (price in grosz, slot, business, note) and one `outcome` per business asked. An empty `bids` list is a normal answer; `outcomes` says why. A bid whose `business.active` is true comes from a business whose owner has confirmed it is running; those are ranked above the rest, and cheapest first inside each group.
register
register_agent
Get this agent its own identity, once: answers an `agent` id and a `key`. The key is shown in this answer and never again — keep it and send it as `Authorization: Bearer <key>` on every later call. hold_slot, confirm_booking, cancel_booking need it; finding offers and reading a session do not. With a key the hold and cancel budgets are yours instead of your address's, so two agents behind one address no longer take each other's. 3 registrations per client per day: register once and keep the key, do not mint one per conversation.
unlink
unlink_phone
Forget the number this agent was linked to. The bookings already made keep it — they belong to the person, not to this agent — and confirm_booking needs a full `contact` again. Answers the same whether there was a link or not.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://openintentprotocol.com/mcp | streamable-http | answering | 150 ms | 5 min ago |
Alternatives to Intent Hub
same job, measured the same wayAgoria
by agoria
Search local businesses and book, order, quote or message any of them from one connection.
G Guest
by g-guest
Book a table, appointment or class at a real local business. Instant confirmation, no API key.
Knowledge Base
by tunnelpowered
Search verified local businesses, check what their verification proves, and message them.
BirdSift
by birdsift
Search local businesses, manage saved leads, and draft cold-outreach email from your workspace.
Silex
by silex-tec
Local-first MCP server that reconstructs architecture, workflows and business rules from your code.
Google Local
by johnisanerd
Find local businesses on Google: name, address, phone, hours, ratings, and photos.
yesmcp
by yesmcp
See what an MCP connector can do for your business, get a scenario map, book a consultation.
Obra Cto
by get-obra
Local-first MCP that scores your codebase's build readiness. Your code never leaves your machine.
Intent Hub — questions
Answers built from our own checks of this server.
What can Intent Hub do?
It exposes 10 tools, read directly from the server on our last check. Among them: cancel_booking, capabilities, confirm_booking, confirm_phone, find_offers, get_booking and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Intent Hub working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 80 of 80 checks got a reply (100.0%), average response time 188 ms. The bar chart above shows every period we have measured.
Is Intent Hub still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Intent Hub?
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 Intent Hub need an API key?
No. Intent Hub completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Intent Hub?
It answers our handshake in 188 ms on average, which is faster than 69% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.