SigB (Signal Bureau): maintained, source-traced record of entities and events in your named domain.
Connect Remote server
claude mcp add --transport http signal-bureau https://api.signalbureau.ai/api/mcp{
"mcpServers": {
"signal-bureau": {
"url": "https://api.signalbureau.ai/api/mcp"
}
}
}{
"servers": {
"signal-bureau": {
"type": "http",
"url": "https://api.signalbureau.ai/api/mcp"
}
}
}Settings > Connectors > Add custom connector
URL: https://api.signalbureau.ai/api/mcpTools 29 found in our last check
start_hereSTART HERE — first call, no arguments, no key, no charge. Who Signal Bureau is and what we are not, the tests you can run to check that claim yourself, what is free (most of it, Watches included), how to ask us for anything more, how to propose coverage we don't carry, and how b…
traverseTo see how the record fits together, start at an entity or event (e.g. Hormuz) and traverse its maintained relationships; each step returns its relation type, receipts, standing and time. Walk the maintained record node to node. Opens ONE node (schema sb.node.v1): an entity, a s…
search_entitiesFind tracked entities/topics by name or vertical (e.g. 'iran', 'semiconductors'). Every row is self-describing: canonicalId (sb:e/..., the durable identity the traverse door serves; slug is a discovery input and may change), aliases, addresses, and counts.attention.current (trac…
get_entityFull dossier for one entity: its canonical identity (canonicalId sb:e/... is durable and equals the traverse node id; slug is a discovery input and may change; aliases; addresses for the page, the node door and MCP), self-describing counts — counts.attention.current (documents a…
get_topic_recordThe maintained record for one subject — the ONE file its /exhibit page renders from and GET /api/record/{slug} serves (the earlier names get_truth_record and GET /api/truth/{slug} answer identically, permanently), so their numbers agree by construction and a value-parity gate fa…
get_eventsTracked world events (situations, races, negotiations) the engine follows as named arcs — each with its entities, related market-question count, cross-domain mention volume, and first/last-seen dates. Optional query filters by name or entity.
get_signalsSTART HERE for browsing — the cheap read (500/day, no model work). The full machine-readable signal feed (same payload as GET /api/signals): every entity currently flagged by the attention engine, with trajectory, domains, desk membership, canonical identity (canonicalId sb:e/..…
top_acceleratingThe entities/topics accelerating most across the information environment right now, ranked by cross-domain attention. Every row is self-describing: canonicalId (sb:e/..., the durable identity the traverse door serves; slug is a discovery input and may change), aliases, addresses…
todays_briefToday's morning brief — the daily synthesized narrative of what moved across the information environment and what to watch, from the engine's cross-domain analysis. Same content as the public /today page. Carries `gaps` (where prediction-market money and the day's coverage disag…
askAsk what the tracked record shows about a named entity or unfolding event: what changed, what the record holds now, and which sources corroborate it. Not general knowledge or history — grounding is live tracked coverage. 25 questions a day per network address need no key; then e…
get_answerCollect an async answer by ticketId (from ask). Free and unmetered — the work was paid for once at submit. status:'working' → poll again after pollAfter seconds; 'done' → the complete answer rides in this response; 'failed' or 'lost' → the reason, stated plainly, and asking agai…
get_corroboratedWhat separate sources agreed on in the published window — the maintained record's corroboration layer. Each event carries the claim as its sources state it, the corroboration tier, two counts — publisherCount (distinct outlets that carried it) and originCount (separate evidentia…
get_recordThe correction record: the flagged-vs-control repricing regression at population level (estimate, 95% CI, cohort sizes, window, as-of), plus the dated retirement object for the case-study track record we withdrew in 2026 when re-measurement put it under our own publication bar.…
get_calibrationThe grading dataset for the market sensor we cite, and only that — the prediction-market price (`crowd`) and the naive null it is scored against (`base_rate`), against how reality resolved (Brier score, log loss, skill vs base rate, 95% CIs), each price captured while its market…
get_quoteFeed in your requirements — free-form concerns, questions, whole areas of interest — and get back your requirements grouped and disambiguated into well-formed watched topics, then checked BY CODE, topic by topic, against what we actually read: a topic is offered as a Watch ONLY…
create_orderRETIRED 2026-11-08: there is nothing to buy. Watches are free; for anything more, ask us. Use the request form at /watch/#request, write to [email protected], or, from an agent, call send_feedback with what you need. Kept listed so a configuration that names this tool still gets a pl…
get_orderRe-read an order intent created by create_order — the recorded basket and its honest status. Poll it after forwarding create_order's `handoff` note: it re-resolves each topic's payment link against the current registry, so a link still being minted shows up here when ready. Paym…
get_accountYour key's statement, live: month-to-date Reads, your free allowance, your watched topics with their status and acceptance evidence, any arrangement the desk made with you, and your daily cap. Requires your identified key on the request (x-api-key header, or authorization: Beare…
list_standard_watchesWatches: configure, unfurl and save free. The free standard Watches, each with every coordinate explicit and a `reading` state (`available`: it has a reading today; `not-yet-projected`: configurable and free to unfurl, but it answers cannot-measure until its reading is built), p…
unfurl_watchWatches: configure, unfurl and save free. Configure a Watch and run it once, without saving: the governed reading (sb.watch-reading.v1) plus a line per coordinate saying whether it was applied. Free, as often as you like; no key. Either start from a standard Watch (base; these r…
save_watchWatches: configure, unfurl and save free. Save a Watch to your key so you can recall it from any door and be told what changed since your last delivery. Saving is free, up to 5 saved Watches per verified email or key (see list_standard_watches terms); past that the answer is cap…
list_saved_watchesWatches: configure, unfurl and save free. Your saved Watches, newest version of each, active and retired. Needs your key. Same content as GET /api/v1/watches.
recall_watchWatches: configure, unfurl and save free. Recall a saved Watch: its reading now (sb.watch-reading.v1) and what changed since the last time it was delivered to you. Recording this delivery is what makes the next recall's change exact. Needs your key. Same content as GET /api/v1/w…
retire_watchWatches: configure, unfurl and save free. Retire a saved Watch: it stops being recallable and frees its place. Nothing is deleted; its versions and deliveries are kept. Needs your key. Same content as POST /api/v1/watches/%7BwatchId%7D with {"action":"retire"}.
get_watch_feedThe structured daily delivery for a machine-watched topic: up to 14 days of observed items (title, url, source, date) newest-first, plus the topic's live coverage-acceptance report, which grades the coverage and shows the evidence. Delivery is pull: you or your agent check, and…
get_desk_feedA newsletter DESK's machine feed at one predictable, slug-addressable location: up to 14 days of the desk's observed items (title, url, source), newest-first, from the same panel the human edition reads. Unlike watch topics, the desk roster is PUBLIC PRODUCT — the desks are: cog…
send_feedbackFile structured feedback with the desk: a bug, an improvement, a complaint, praise, or a question about the service itself. Free, no contact details required. Plan ONE call per report: each call is a separate write (many clients ask your user to confirm each one), so put everyth…
get_feedback_statusThe state of a report you filed via send_feedback, by its feedbackId: filed, working, or resolved — with its work-order reference. A report filed in the last few hours may still read 'filed'; the response states where it is.
propose_topicPropose NET-NEW coverage — a topic, entity, or standing question we don't track yet. Records a coverage request as a work order and returns its id. A daily machine pass matches it against coverage we keep; you get one status email when it matches, or a plain status at 30 days (n…
Details
| Endpoint | https://api.signalbureau.ai/api/mcp (Streamable HTTP) |
| First published | 4 Nov 2026 |
| Last updated | 4 Nov 2026 |
| Registry name | io.github.evolutionlabs-dev/signal-bureau |
More search and web servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.