原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Signal Bureau

作者:evolutionlabs-dev版本 1.1.2i★ –i在云端运行
注册名称io.github.evolutionlabs-dev/signal-bureau

安装方法

概览

作者提供的说明(英文原文)

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

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

安装

选择你使用的 AI 应用,然后复制设置。

通过 2/3 项检查 · 你的提问会经过开发者的服务器(api.signalbureau.ai)

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1+ Add2https://…3Add4
  2. 点击“+ Add” → “Add custom connector”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称Signal Bureau
    Remote MCP server URL · 地址https://api.signalbureau.ai/api/mcp

    Authentication 保持 Claude 检测到的设置,然后点击 Add

  3. 在聊天中开启

    +ConnectorsSignal Bureau

  4. 试一试

    用 Signal Bureau 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Signal Bureau,或回答中出现 Signal Bureau 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

仅企业版 ChatGPT 可连接

适用于网页版 ChatGPT Business、Enterprise 或 Edu,需由工作区管理员或所有者添加 · 使用 Free、Plus 或 Pro:你的 ChatGPT 方案暂时无法自行连接 MCP

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称Signal Bureau
    Connection · 地址https://api.signalbureau.ai/api/mcp
  3. 在聊天中选择 Signal Bureau

    开启新聊天,输入前先从插件列表中选择 Signal Bureau

  4. 试一试

    用 Signal Bureau 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 Signal Bureau,或回答中出现 Signal Bureau 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http signal-bureau https://api.signalbureau.ai/api/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 Signal Bureau 在列表中并显示已连接

  4. 试一试

    用 Signal Bureau 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Signal Bureau,或回答中出现 Signal Bureau 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Signal Bureau 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Signal Bureau,或回答中出现 Signal Bureau 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Signal Bureau 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Signal Bureau,或回答中出现 Signal Bureau 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://api.signalbureau.ai/api/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Signal Bureau 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

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

Cursor (~/.cursor/mcp.json)

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

VS Code (mcp.json)

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

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
不在 npm/PyPI 上
许可证i
未注明许可证
连接方式
在云端运行
传输方式
streamable-http
最新版本i
1.1.2
分类i
其他
发布到注册中心i
2026年11月4日
代码最后更新i
–
作者
evolutionlabs-dev
网站
sigb.ai
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • 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), what is paid (Watches and Reads) at live published prices, how to propose coverage we don't carry, an

  • traverse

    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 si

  • search_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, addresses, and counts.attention.current (track

  • get_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 counts — counts.attention.current (documents an

  • get_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 by construction and a value-parity gate fai

  • get_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 entity.

  • get_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, canonical identity (canonicalId sb:e/...

  • 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 input and may change), aliases, addresses,

  • todays_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-market money and the day's coverage disagr

  • ask

    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 ea

  • get_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' → the reason, stated plainly, and asking again

  • get_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 it) and originCount (separate evidentiar

  • 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-measurement put it under our own publication bar. A

  • get_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% CIs), each price captured while its market

  • get_quote

    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

  • create_order

    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, nothi

  • get_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 being minted shows up here when ready. Payme

  • get_account

    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: Bea

  • list_standard_watches

    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 re

  • unfurl_watch

    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 Wa

  • save_watch

    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 te

  • list_saved_watches

    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.

  • recall_watch

    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 conten

  • retire_watch

    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":"retir

  • get_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 (it does not gate billing — billing starts when t

  • get_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 roster is PUBLIC PRODUCT — the desks are: cogn

  • send_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 user to confirm each one), so put everythi

  • get_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 matches, or a plain status at 30 days (no

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月11日

  • ! 注意

    作者与仓库一致

    发布者(evolutionlabs-dev)不是仓库所有者(evolutionlabs-dev);可能是其他人代为上架的

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • ✓ 通过

    端点有响应

    在 416 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 29 个工具描述,未发现针对 AI 的隐藏指令

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

使用 Google 登录后发帖

用户评价

还没有评价

用 Google 登录后写评价

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 19138 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 19138 个服务器的 86% 更新
  • 基础检查结果等于或优于此分类中其他 19138 个服务器的 41%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Signal Bureau 安全吗?

它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(1.1.2)于7天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于支持远程 MCP 的应用,例如 ChatGPT Business 及以上方案。

有什么可以替代它?

同一分类中有:World Monitor, Claude Flow, Tldraw

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.

作者:koala73广泛使用★ 9万6天前更新

在云端运行✓ worldmonitor.app

Claude Flow

AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.

作者:ruvnet广泛使用↓ 1.4万/周★ 8.1万14个月前更新

在你的电脑上运行

Tldraw

Draw and visually collaborate with your agents on tldraw's canvas.

作者:tldraw广泛使用★ 5.1万8个月前更新

在云端运行

作者的 README

仓库中没有找到 README