signal-bureau
SigB (Signal Bureau): maintained, source-traced record of entities and events in your named domain
Reviews
No review yet. Used signal-bureau? Be the first to help others choose.What it does
signal-bureau is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 18h ago (live check)Hosted endpoint
https://api.signalbureau.ai/api/mcpstreamable-http
In Claude Code: claude mcp add --transport http signal-bureau https://api.signalbureau.ai/api/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"signal-bureau": {
"url": "https://api.signalbureau.ai/api/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 18h agoONLINE signal-bureau answered an MCP connection on 16 Nov 2026 and introduced itself as signal-bureau 0.6.0 (MCP protocol 2025-06-18).
29 tools offered to AI assistants
start_here· START 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 protraverse· To 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 nsearch_entities· Find 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, addresget_entity· Full 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 countsget_topic_record· The 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 byget_events· Tracked 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 entitget_signals· START 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,top_accelerating· The 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 intodays_brief· Today'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-maask· Ask 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 dayget_answer· Collect 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' → theget_corroborated· What 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
Show 17 more
get_record· The 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-measurementget_calibration· The 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% CIsget_quote· Feed 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 recreate_order· RETIRED 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 lead@evfm.co, or, from an agent, call send_feedback with what you need. Kept listed so a configuratiget_order· Re-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 beinget_account· Your 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-list_standard_watches· Watches: 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 cannotunfurl_watch· Watches: 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 stasave_watch· Watches: 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_watclist_saved_watches· Watches: 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_watch· Watches: 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. Needsretire_watch· Watches: 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 withget_watch_feed· The 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. Deliveryget_desk_feed· A 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 rostersend_feedback· File 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 usget_feedback_status· The 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_topic· Propose 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 m
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Website | https://sigb.ai/machine/ | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Version | 1.1.2 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Hosted endpoint | https://api.signalbureau.ai/api/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Repository | https://github.com/evolutionlabs-dev/cognitive-investor | DECLARED | SRC-001 Official MCP Registry | 15d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
- VERSION04 Nov 20261.1.1 → 1.1.2
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is signal-bureau still online?
Free alerts · no account▲ 0Do you run signal-bureau? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about signal-bureau
How do I connect signal-bureau?
Use the hosted endpoint https://api.signalbureau.ai/api/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does signal-bureau offer?
When Electra Index connected on 16 Nov 2026, it listed 29 tools: start_here, traverse, search_entities, get_entity, get_topic_record, get_events, get_signals, top_accelerating and more. The full list is in "Live check" above.
Is signal-bureau online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 18h ago.