MCP server

Signal Bureau

io.github.evolutionlabs-dev/signal-bureau

Checked 25 Oct 2026, 20:29 UTC · Connected to it and listed its tools

SigB (Signal Bureau): maintained, source-traced record of entities and events in your named domain.

Website Source

At a glance

Type

MCP server

Publisher

Not verified

Status

Working at last check

Tools

29

Token cost

About 10,908 tokens per request

Sets up in

Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok

Last checked

25 Oct 2026, 20:29 UTC

Connect it to your agent

Add to CursorAdd to VS CodeVS Code Insiders

Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.

Claude Code

claude mcp add --transport http signal-bureau https://api.signalbureau.ai/api/mcp

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL.

Codex (config.toml)

[mcp_servers.signal-bureau]
url = "https://api.signalbureau.ai/api/mcp"

Gemini CLI

{"mcpServers":{"signal-bureau":{"httpUrl":"https://api.signalbureau.ai/api/mcp"}}}

Cursor

{"mcpServers":{"signal-bureau":{"url":"https://api.signalbureau.ai/api/mcp"}}}

VS Code

{"servers":{"signal-bureau":{"type":"http","url":"https://api.signalbureau.ai/api/mcp"}}}

Antigravity

agy mcp add signal-bureau https://api.signalbureau.ai/api/mcp

ChatGPT

Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.

OpenAI API (Responses tools)

{"type":"mcp","server_label":"signal-bureau","server_url":"https://api.signalbureau.ai/api/mcp","require_approval":"always"}

Grok (xAI API tools)

{"type":"mcp","server_label":"signal-bureau","server_url":"https://api.signalbureau.ai/api/mcp"}

Tools

• ask ~360 tokens
  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 day per network address need no key; then each costs one Read on
• create_order Moves money · ~991 tokens
  Assemble a basket and get exact prices plus Stripe checkout links. Checkout runs on Stripe's hosted page, completed by whoever holds the payment credentials. Pass dryRun:true to REHEARSE: same validation, same price math, clearly labeled, no order recorded, no links issued, nothing billed — integrat
• get_account ~163 tokens
  Your meter-account statement, live: month-to-date metered Reads counted at the published tariff, your watched topics with billing/billing status and their acceptance evidence, and your daily cap. Requires your identified key on the request (x-api-key header, or authorization: Bearer sb_live_...). Wi
• get_answer ~138 tokens
  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' → the reason, stated plainly, and asking again is the remedy.
• get_calibration ~200 tokens
  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% CIs), each price captured while its market was OPEN and graded
• get_corroborated ~486 tokens
  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 it) and originCount (separate evidentiary origins: a wire re
• get_desk_feed ~685 tokens
  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 roster is PUBLIC PRODUCT — the desks are: cognitive-investor, tax-
• get_entity ~260 tokens
  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 counts — counts.attention.current (documents and coverage verticals
• get_events ~139 tokens
  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 entity.
• get_feedback_status ~124 tokens
  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.
• get_order ~182 tokens
  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 being minted shows up here when ready. Payment status for checko
• get_quote ~556 tokens
  Feed in your requirements — free-form concerns, questions, whole areas of interest — and get back an enumerated quote: your requirements intelligently grouped and disambiguated into well-formed watched topics, then checked BY CODE, topic by topic, against what we actually read: a topic is priced ($2
• get_record ~173 tokens
  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-measurement put it under our own publication bar. Appended, never edite
• get_signals ~393 tokens
  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, canonical identity (canonicalId sb:e/..., durable; slug may
• get_topic_record ~1062 tokens
  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 by construction and a value-parity gate fails the build if they
• get_watch_feed ~356 tokens
  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 (it does not gate billing — billing starts when the Watch starts, and
• list_saved_watches ~78 tokens
  Watches: configure and unfurl free; saving is the paid step. Your saved Watches, newest version of each, active and retired. Needs your key. Same content as GET /api/v1/watches.
• list_standard_watches ~162 tokens
  Watches: configure and unfurl free; saving is the paid step. 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), plu
• propose_topic ~292 tokens
  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 matches, or a plain status at 30 days (not yet covered, with
• recall_watch ~175 tokens
  Watches: configure and unfurl free; saving is the paid step. 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/wat
• retire_watch ~136 tokens
  Watches: configure and unfurl free; saving is the paid step. Retire a saved Watch: it stops being recallable and frees its paid slot. Nothing is deleted; its versions and deliveries are kept. Needs your key. Same content as POST /api/v1/watches/%7BwatchId%7D with {"action":"retire"}.
• save_watch ~793 tokens
  Watches: configure and unfurl free; saving is the paid step. 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 the paid step, at the published Watch rate per saved Watch per month (see list_standard_watches terms); with no free p
• search_entities ~187 tokens
  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, addresses, and counts.attention.current (tracked coverage on the d
• send_feedback Sends messages · ~1054 tokens
  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 user to confirm each one), so put everything in one. Caps, sta
• start_here ~124 tokens
  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), what is paid (Watches and Reads) at live published prices, how to propose coverage we don't carry, and how buying works.
• todays_brief ~153 tokens
  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-market money and the day's coverage disagree) and `watch` (wha
• top_accelerating ~204 tokens
  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 input and may change), aliases, addresses, and counts.attentio
• traverse ~680 tokens
  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 node (schema sb.node.v1): an entity, a situation, a corrobora
• unfurl_watch ~602 tokens
  Watches: configure and unfurl free; saving is the paid step. 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 rea

Browse

• GitHub tools
• Stripe tools
• Website monitoring
• Email
• Payments
• Email marketing

Related MCP servers

• Dependency Trust
  Trust-check any dependency for agents: OpenSSF Scorecard, licenses, CVEs, deps. 7 ecosystems.
• Crank Protocol
  Non-custodial DeFi tools for AI agents on Solana: swaps, perps, lending, staking, equities.
• The Mirror System — AI Citability
  Request a Brand Discovery Record: the human-approved facts AI cites. One tool, then a person.
• Entity Enricher
  Multi-LLM entity enrichment: schemas, single/batch enrichment, fusion, model benchmarks.
• Senzing
  Entity resolution — data mapping, SDK code generation, docs search, and error troubleshooting
• Stratalize Crypto & DeFi
  Retired. Use com.stratalize/stratalize.
• Bureau (about)
  About Bureau, the self-hosted office for AI agents: overview, FAQ search, roadmap, install.
• Zoning Signal
  Planning and zoning records: 25 jurisdictions in Lake, Orange, Osceola, Polk, Seminole counties, FL

Badge for your README

[![AptLynx](https://aptlynx.net/badge/io.github.evolutionlabs-dev/signal-bureau.svg)](https://aptlynx.net/servers/io.github.evolutionlabs-dev/signal-bureau)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents