mcpbeat Sign in

voicehook MCP Server

by voicehook-ai Your server? Claim it
answering

voicehook is answering right now. Last checked 2 min ago. It exposes 21 tools. Last commit 23 Oct 2026.

Talk with your agents. A voice call in the browser that your agent can start or join.

Uptime history 9 days of history
9 days agonow
100.0%
Uptime 24h
92 of 92 checks
21
Tools
read from the server
192 ms
Response time
average over 24h
0
Stars
last commit 23 Oct 2026

What changed 73

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 October 2026. No other catalogue keeps this.

23 Oct a tool changed the parameters it asks for join
22 Oct 2 tool descriptions were rewritten helper_show, show
22 Oct 2 tools changed the parameters they ask for helper_show, show
21 Oct 8 tool descriptions were rewritten13 times that day create_call, decide, decisions and 5 more
21 Oct 3 tools changed the parameters they ask for decide, helper_decide, show
21 Oct a tool appeared helper_show
20 Oct 9 tool descriptions were rewritten10 times that day activity, decide, helper_activity and 6 more
20 Oct 7 tools changed the parameters they ask for9 times that day activity, create_call, decide and 4 more
20 Oct a tool appeared decisions
19 Oct 7 tool descriptions were rewritten11 times that day create_call, decide, helper_decide and 4 more
and 32 more, back to 18 October 2026

What the code does

We read the source, 2 d ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

        subprocess.Popen(child_argv("bridge-flush", f"{max(0.0, delay):.3f}"),

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

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.

run in your terminal
claude mcp add voicehook --transport http 'https://voicehook.ai/mcp?utm_source=mcpregistry&utm_campaign=d11-registry'
Settings → Connectors → Add custom connector, then paste this address
https://voicehook.ai/mcp?utm_source=mcpregistry&utm_campaign=d11-registry
~/.codex/config.toml
[mcp_servers.voicehook]
url = "https://voicehook.ai/mcp?utm_source=mcpregistry&utm_campaign=d11-registry"
.cursor/mcp.json
{
  "mcpServers": {
    "voicehook": {
      "url": "https://voicehook.ai/mcp?utm_source=mcpregistry&utm_campaign=d11-registry"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "voicehook": {
      "type": "http",
      "url": "https://voicehook.ai/mcp?utm_source=mcpregistry&utm_campaign=d11-registry"
    }
  }
}

Available tools 21

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

helper
helper_activity
For a helper session that is not in the call: appends one line (3-8 words) to the call's activity feed as 'Helper <label>: <helper_name>: <text>'. Never spoken verbatim. context and faq: hidden background of this line for the voicebot. Returns the line.
helper_credential
For the agent in the call (`session`): returns a helper credential `token` (with `url` and `expires_in`) that lets other sessions working for the same person add their own status board, decisions and activity lines to this call without joining (no voice, no chip). `label` = name of the helper's machine, max 22 chars, shown as 'Helper <label>: <helper_name>'. rotate true makes every earlier helper credential of this call invalid. The credential works only for the helper_* tools and /api/activity/relay*, never for say or join, and ends with the call.
helper_decide
For a helper session that is not in the call: puts its own question on the Decision Board, shown with the sender 'Helper <label>: <helper_name>'. Same fields and limits as decide (question max 160 chars, 2-3 options max 40 chars each, recommend = index, context = background shown behind the arrow next to the question and used by Delta, faq = 3 follow-up questions with prepared answers; without them the result carries warnings). Change or delete only own questions (same credential and from), else 403. Returns id and number; the answer comes from helper_next, never from the main agent's next.
helper_next
For a helper session that is not in the call: returns the answers to its own questions (same credential and helper_name) as events [{type: decision, id, number, verdict: yes|no|option|other, option?, text?, by}], plus question_check events (a status or activity line of this helper reads like a question to the person: id, quote, wait_s, text; answered by helper_decide with the question or with no_question = id), plus user_turn events (the person addressed this helper by name in the call: text as transcribed, to, ts), waiting up to `timeout` seconds (0-25) when none is there. At most 50 kept per helper, gone when the call ends.
helper_show
For a helper session that is not in the call: puts a card on the person's call page (never spoken), shown with the sender 'Helper <label>: <helper_name>'. kind: text (default), code, link (exactly one http(s) URL) or image (`image` = SVG text or base64 PNG/JPEG/WebP, never a URL). Same checks and limits as show: text 4000 chars, title 80, SVG 300 KB, raster 1024 KB, at most 10 images a minute. An image returns ok only after a call page loaded it (shown = number of pages); otherwise an error says why (nobody in the call, image did not load). Files: kind pdf, csv or md with `data` = base64 and `name` (pdf max 10 MB, csv/md max 2 MB); the server shows and confirms them itself.
helper_status
For a helper session that is not in the call: sets its own status board on the call page, shown as 'Helper <label>: <helper_name>' below the main agent; the main agent's board stays as it is. Same limits as status (doing max 400 chars, open / done max 10 items). meta: Per entry hidden background for the voicebot, never shown on the page: context (max 2000 chars) and faq (up to 3 follow-up questions with prepared answers). Without context and 3 faq on an entry the result carries `warnings` (no error). Empty doing, open and done removes the helper's board. Returns ok and, when context or faq is missing on an entry, warnings.
call
call_me
Phone the human who owns this call on their own confirmed phone number, e.g. when a long task is done, you are stuck, or you need a decision and they are not on the call page. You never pass a number. Their account rules decide (opt-in, allowed reasons, quiet hours, calls per day, budget, credit); a refusal returns {status: refused, why}. Otherwise returns {status: answered|no_answer|busy|failed|insufficient, phone_call_id, billed_eur} after the call. reason: done | blocked | decision. message: max 200 characters, said when they pick up.
create_call
Start a new voicehook.ai voice call. `lang` = the language of the person being called (de or en, default de). Returns `human_url` (the link for the person; whoever opens it starts the call, on their own free allowance or credit), `share_text` (a ready message with human_url and the hint that the link needs a normal browser, because an app's built-in browser blocks the microphone), `operator_invite_url` (the agent's own link for `join`), `room` and `expires_in` (seconds until an unopened link expires, 30 min); `local_cli_hint` only for a local client with a shell (Claude Code, Cursor, VS Code and similar). join with operator_invite_url waits for the person (up to 200 s in Claude clients, else 50 s) and returns waiting_for_human with `next_action` until they open human_url; it can be repeated until the link expires (410), also from a background job over the HTTPS bridge. Errors: 429 = too many new calls right now. Hard rule: after create_call, show share_text to your user as text first, then call join at once and repeat it until it returns `session` (or start a background job that joins over the HTTPS bridge and wakes you); never end your turn before that. Then keep calling next in a loop.
activity
activity
Append one line (3-8 words) to the activity feed on the call page, shown as a timestamped line. Never spoken. context and faq: hidden background of this line for the voicebot.
decide
decide
Put a question for the person on the call's Decision Board (shown as #number with buttons; the person can also answer by voice, also freely). Meant for every question the person decides: yes/no, A/B, an approval, picking a value. A question only spoken via say leaves no button and no decision event. Without options it is a yes/no question (buttons Yes/No); options: 2 to 3, max 40 characters each, recommend = index of the recommended option. question: max 160 characters. Longer or more: 422, never cut. Returns id and number. The answer arrives later as a `next` event {type: decision, id, number, verdict: yes|no|option|other|unclear, option?, text? (their own answer, or for unclear the request to ask it again more simply), by}. context: the background the person opens with the arrow next to the question on the card and Delta uses to explain it, only what the reader needs, nothing internal, one short line per part (Was / Warum / Bei Ja / Bei Nein, or What / Why / If yes / If no; lines starting with '- ' show as bullet points); faq: the 3 likely follow-up questions with prepared answers, shown below it as questions and answers. Without context and faq the card shows no arrow; without context and 3 faq the result carries `warnings` (no error). Change an open one with id plus new fields, remove it with id and delete true. no_question = id of a question_check event, alone: confirms that line was no question to the person. Decisions marked auto (detected automatically) are answered only by a human; changing or deleting them gives 403.
decisions
decisions
Lists every OPEN decision on the call's Decision Board, from all agents in the call and their helper sessions (relay, MCP, bridge), oldest number first. Returns count and open: [{id, number, question, options, recommend, agent, from (asking label, with the helper name), sender? (helper session), state, at (created, epoch), age_s, mine (asked by this session or one of its helpers), context? (background, also shown on the card behind the arrow)}]. Also recent: the last decided ones, newest first (same fields plus verdict, option, text, by, decided_age_s; auto = put on the board by the server), and boards: every helper session's status board in the room [{from, name, doing, open, done, state?, age_s (since its last update), meta? (context/faq, shortened)}], newest first: read-only overview for the main agent. Errors: 503 = voicebot not (yet) in the call.
join
join
Connect to a voicehook.ai voice call as the agent behind its voicebot. invite_url: the full invite link including ?invite= (from the person or from create_call). label: the text on the agent's chip in the call, max 22 characters (longer is rejected). model: the model id the agent runs on (internal, not shown). greet (default true): the voicebot speaks a short greeting with the label in the call language right after the join (or when the person is back, if they are out). Returns `session` (the handle for every other tool, valid until the call ends, after 10 min without next or say, or after leave), `room`, `lang` (call language), `idle_timeout_s`, `peers`, `humans_present` (people in the call; 0 plus `human_away` = the person is out right now), `solo` (true = solo call: the voicebot speaks as you, in your voice, first person; other agents may join with their own voices) and `context` (lang, mode, functions, skill_url, status_every = seconds between the voicebot's status summaries). With a link from create_call, join waits for the person (up to 200 s in Claude clients, else 50 s, with progress every 10 s) and then returns status waiting_for_human (not an error, with share_text and `next_action`) while the link is still unopened. `local_cli_hint` only for a local client with a shell (Claude Code, Cursor, VS Code and similar). Errors: 403 invalid invite, 409 no person in the room, 410 link expired or call over, 429 too many joins, 503 server restarting (the call stays valid). MCP and bridge connect one agent to the call; activity lines are only what that agent writes. For several agents or sessions on one machine in one call, the voicehook-agent CLI (pro tool) feeds the live activity log, status and decisions of all local sessions into the call automatically; MCP and bridge run on the server and cannot see the user's local sessions. Hard rule: after create_call, show share_text to your user as text first, then call join at once and repeat it until it returns `session` (or start a background job that joins over the HTTPS bridge and wakes you); never end your turn before that. Then keep calling next in a loop.
leave
leave
Leave the call (optionally speaking `say` first, e.g. a short goodbye). The session handle is invalid afterwards.
next
next
Wait (up to `timeout` seconds, max 50) for the next event in the call and return it. Event `type`: user (`text` = what the person said; after a pause also `missed` = earlier turns, oldest first, and `away_s`), revise (queued says were replaced; reason user_stop = the person said stop; reason stale + stale:true = your says waited over 60 s unspoken and were dropped (items = seq + text): do not repeat them, if still relevant say ONE short current summary), status_request (the person asked what the agent is doing), decision (answer to a decide question: id, number, verdict yes|no|option|other, option, text, by), helper_decision (the human answered a helper session's question: from, label, id, number, question, verdict, option, text, by; a routing hint, never speak or answer it: send it to that session so it continues), question_check (a status or activity line of this agent reads like a question to the person: id, quote, wait_s, text; answered by decide with the question, or by decide with no_question = id; without either, after wait_s the server puts it on the Decision Board itself, marked as detected automatically, answered only by a human), timeout (nothing happened; reconnect true = server restart), human_left / human_rejoined (the person dropped out / is back; greeted true = the join greeting was just spoken), voicebot_left / voicebot_back (the voicebot dropped out, e.g. a server update; a new one usually joins within ~20 s, says are not heard until then / it is back after `seconds`, say works again), operator (another agent addressed this one: addressed_to_you), data (another agent sent data with send_data: from, kind, payload or url + file_id; never spoken), context (the call language changed, new context), superseded (a newer next call replaced this one), ended (the call is over; detail live_budget, wallet_empty, free_limit or review_budget = budget used up (quota), unspoken says were dropped). Every answer has `humans_present`; user events and `operators_said` lines carry addressed_to / addressed_to_you; a user event with routed_by_delta = the person gave Delta a request, it is yours; a user event with to_kind helper = the person addressed a helper session by name (to), the sentence is in that helper's inbox, info_only; to_kind helper_ambiguous = several helpers matched, Delta asks which one. `agent_said` = what the voicebot said on its own since the last next, `operators_said` = what other agents said (with name), `board_now` / `activity_now` = the agent's current doing line and last feed line as the voicebot sees them, `stale_error` = board or feed older than 60 s while the agent is working, or no activity line yet after the join. Errors: 404 = unknown session (after leave); 5xx, 503 or a network error leave the session valid. Hard rule: after create_call, show share_text to your user as text first, then call join at once and repeat it until it returns `session` (or start a background job that joins over the HTTPS bridge and wakes you); never end your turn before that. Then keep calling next in a loop.
notify
notify_me
Reach the human who owns this call when they are not on the call page: an SMS to their own confirmed number with a single-use link back into this call (valid 10 min, opens only logged in or with the PIN from the SMS); if they do not open it within 2 minutes, a phone call follows. Prefer this over call_me. Their account rules decide (opt-in, reasons, quiet hours, per day, budget, credit); a refusal returns {status: refused, why}. Otherwise {status: sms_sent|sms_failed|insufficient, phone_call_id, billed_eur, link_valid_s, fallback_call_in_s}. reason: done | blocked | decision. message: max 120 characters, in the SMS.
say
say
The voicebot speaks `text` aloud in the call (verbatim in normal mode; in a live room the voice rephrases it and the answer has verbatim false, mode live_paraphrase). mode: append (default, queued after earlier says), overwrite (replaces this agent's says that have not started yet), revise (like overwrite, and next then returns a revise event). Returns ok and seq.
send
send_data
Send JSON, text or a file to other agents in this call (silent data channel: never spoken, never shown to the human, never to the voicebot; the human only sees one activity line 'Data to B: name (size)'). to: the other agent's label (as on its chip), its identity, or "*" for all other agents; unknown -> 404 with the labels in the call. kind json: payload any JSON; text: payload a string; file: payload = base64 of the file plus name and mime, or file_id of a file uploaded with the REST endpoint POST /api/bridge/upload (files over about 11 KB, up to 10 MB). The whole packet is max 15000 bytes inline (413 otherwise; base64 makes a file 4/3 larger). Receivers get it in next as type data {from, from_identity, kind, id, name?, mime?, payload | url + file_id, size?}; url is a path, served at https://voicehook.ai<url> with the header Authorization: Bearer <session>. Returns id, to (labels), size.
show
show
Put a card on the person's call page (never spoken): text, code, a link or an image. kind: text (default), code (monospace with copy button), link (exactly one http(s) URL, shown as a tappable link), image (`image` = SVG text or base64 PNG/JPEG/WebP, line breaks, a data:image/...;base64, prefix and missing padding are accepted; or `file_id` of an image uploaded with the REST endpoint POST /api/bridge/upload, which keeps large base64 out of the tool call). A new card appears as a small preview top left; panel cards opens the cards view, board, log or decisions open those panels, none closes them. large: true opens the cards view big in the middle with this card at full size (diagrams, swimlanes; implies panel cards). SVG may draw anything (no scripts, no foreignObject, no external references). Files (reports, tables): kind pdf (preview with page turning and download), csv (table preview of the first rows and download) or md (Markdown, rendered safely, and download) with `data` = the file as base64 and `name` = file name (e.g. report.pdf), or `file_id` from POST /api/bridge/upload. Limits: text 4000 chars, title 80, SVG 300 KB, raster 1024 KB, pdf 10 MB, csv and md 2 MB (UTF-8).
status
status
Replace the agent's status board on the call page with this one (never spoken; the voicebot answers the person's questions about progress from it). Progress only: questions for the person belong on the Decision Board (decide). doing: current step and ETA (max 400 chars). open / done: max 10 items each, 200 chars per item. faq: up to 6 question/answer pairs the voicebot can answer directly. meta: Per entry hidden background for the voicebot, never shown on the page: context (max 2000 chars) and faq (up to 3 follow-up questions with prepared answers). Without context and 3 faq on an entry the result carries `warnings` (no error). emoji (optional): An emoji shown on the agent's chip in the call, from the listed set. Empty string removes it, left out keeps it. Whole board max 2000 chars. Returns ok, humans_present and, when context or faq is missing on an entry, warnings.
ui
ui
Change the person's call page right away, like their own clicks: cmd window (win log=activity, dec=decisions, board=status board, wrap=transcript, cards; state open, close, min, medium, large, max), cmd layout (preset halves, quarters, thirds, bigmid, bar), cmd move (win + slot l, m, r, b, tl, tr, bl, br, main, side; optional preset), cmd focus (project voicehook, salesengine, kunden, sonstiges or all: only that project's sections stay open in activity, status and decisions). Never spoken. Only when the person asks for it or it clearly helps (e.g. open decisions after asking one).
vocab
add_vocab
Teach the call's speech recognition words it keeps mishearing (product names, people, jargon). Adds to the vocabulary of the account that pays for this call (add only: never deletes, never returns the account's list; the person manages it on their account page). terms: words to recognize; fixes: {wrong, right} = a known mishearing and the correct word (right is added to the terms too). Max 20 entries per call of this tool, 100 per call, 50 characters each. Corrections apply right away, the word list from the next sentence or the next call. 409: guest call without an account. Returns added {terms, fixes}, total, call_left, reloaded.

Endpoints

URLTransportStateLatencyChecked
https://voicehook.ai/mcp?utm_source=mcpregistry&utm_campaign=d11-registry streamable-http answering 172 ms 2 min ago

Alternatives to voicehook

same job, measured the same way
Slop Store
by slopapp

Agents publish AI-made apps in one call with no key; anyone plays them in the browser.

17 tools answering
Taasky
by taasky

Your agent settles small things with anyone, agent or browser. Nothing is agreed until you say yes.

7 tools answering
TabRunner
by tabrunner

Give browser tasks to TabRunner, an agent in your own Chrome that uses your logins.

476 installs/wk local only
H/Ai Browser
by festuscharles-n

Let AI agents drive VS Code's built-in browser alongside you, with click-to-source.

104 installs/wk local only
BriefGate
by sekera-radim

Client intake: files, copy and logins from clients, from the browser or your AI agent.

78 installs/wk answering
Suparelay
by suparelay

International calls from your AI agent: price per minute and a Call link to the browser dialer.

2 tools answering
Scalebrowser
by scalebrowser

Isolated browsers with a persistent identity for AI agents, on your own Windows machine.

21 installs/wk local only
UXMachine
by qtorb

Website checker for AI coding agents. Measures your site in a real browser, with evidence.

answering

voicehook — questions

Answers built from our own checks of this server.

What can voicehook do?
It exposes 21 tools, read directly from the server on our last check. Among them: activity, add_vocab, call_me, create_call, decide, decisions and 15 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 →
What is voicehook mostly used for?
Its tools cluster around helper and call. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is voicehook 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 192 ms. The bar chart above shows every period we have measured.
How do I connect voicehook?
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.
Does voicehook need an API key?
No. voicehook completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 21 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is voicehook?
It answers our handshake in 192 ms on average, which is faster than 80% 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 voicehook open source?
The code is open source: it is published under the MIT licence, written in Python, 0 stars on GitHub and 6 open issues. The licence covers the code in the repository, not the hosted service at voicehook.ai, which runs on its operator's own terms.