Fulcru

io.github.gsmmediaro由 GitHub 账号 gsmmediaro 发布v2.0.0更新于 Oct 25, 2026

Find where ChatGPT names your competitor, write the page that closes the gap, measure it.

已验证Streamable HTTP可网页运行网页搜索与抓取数据与分析

概览

AI 生成的概览

Fulcru 是一个托管式 MCP 服务器,用于找出 AI 搜索中提及竞争对手而非你品牌的提问,起草弥补差距的页面,并跟踪 AI 可见度变化。

可以做什么
找出 AI 助手提及竞争对手而非你品牌的提问,按差距从大到小排列,并起草一篇弥补该差距的 Markdown 页面。将草稿页面连同网址标记为已发布,并记录用于衡量的基线快照。报告已发布页面带来的 AI 可见度变化,以及概览、竞争对手、来源和提及报告。
适用场景
当你希望助手执行 AI 搜索可见度闭环时使用:排查哪些提问提及竞争对手、产出弥补差距的内容,并衡量发布前后的变化。适合需要持续跟踪各 AI 助手中品牌提及的团队,而非一次性检查。
运行要求
通过 streamable HTTP 访问的远程端点,使用 Authorization 请求头中的 bearer 令牌认证,令牌来自服务商的 Integrations 页面;也支持带动态客户端注册的 OAuth 2.1。持续衡量闭环需要 Fulcru 账户,并需能访问托管服务的网络。
安装前请注意
Authorization 中的 bearer 令牌是账户凭据,请勿放入共享配置或日志。发布操作会将页面标记为上线并记录基线快照,会改变账户状态。差距、页面和可见度数据会发送到托管的 Fulcru 服务,内容和站点网址会离开本机。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Fulcru,将其添加到工作区。
  2. 连接 Authorization token 凭据。它们会被私密存储,绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.gsmmediaro%2Ffulcru/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "fulcru": {
      "type": "http",
      "url": "https://api.fulcru.app/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

fulcru

Get named by AI search engines.

When someone asks ChatGPT "what's the best CRM for a small team", the answer names two or three products. Those get the customer. Everyone else is invisible.

fulcru finds the questions where an AI assistant names a competitor instead of you, writes the page that closes the gap, and measures what publishing it did. It runs as a CLI, an MCP server, and an agent skill, so a human or an agent can run the whole loop.

This repo is the open, self-hostable agent surface. The measurement engine is the hosted Fulcru service; everything here is a thin client that talks to it with your token.

We run it on ourselves and publish the result, whichever way it goes. Today it scores us 0 out of 34 prompts: we sell AI visibility and we score zero on our own product, with the full run and the source data.

bash
npm install -g fulcruexport FULCRU_TOKEN=pk_...        # Settings -> Integrations at fulcru.app

Or run it in Docker, with nothing installed on the host:

bash
docker build -t fulcru .docker run --rm -e FULCRU_TOKEN=pk_... fulcru gaps

No secrets are baked into the image; the token is passed at run time. Verified on node:20-alpine, 2026-07-27.

The loop

bash
$ fulcru gaps  0%  k57jc...  best AI visibility tracker for a SaaS startup -> AI names Profound, Peec AI  0%  k57bw...  how do I know if ChatGPT recommends my brand -> AI names Otterly AI 33%  k57xz...  tools to track brand mentions in Perplexity -> AI names Semrush
Write the top one:  fulcru write k57jc...
$ fulcru write k57jc... > page.md     # the drafted article, grounded in what AI cites$ fulcru publish k57jc... https://mysite.com/blog/ai-visibility-trackersPublished. Baseline: AI names you in 0% of 9 measured answers.
$ fulcru delta    0% ->  44%  +44pts  Best AI Visibility Trackers, Compared

That last line is the whole point.

Commands

CommandWhat it does
fulcru gaps [n]Questions where AI names a competitor and not you, worst first
fulcru write <promptId>Writes the page that closes one gap; Markdown to stdout
fulcru publish <pageId> <url>Marks it live and snapshots the baseline to measure from
fulcru deltaWhat your published pages actually did
fulcru report [section]overview, competitors, sources, mentions, prompts

Add --json to any command for the raw payload.

Built for agents

Output is terse lines, not JSON blobs, because the caller is usually an LLM and its context is the scarce resource. fulcru gaps costs an agent about 50 tokens; the same data as raw API JSON costs about 800. fulcru write sends the Markdown to stdout and everything else to stderr, so fulcru write <id> > page.md gives a clean file.

MCP

Two ways to wire the five Fulcru tools into an agent.

Remote (hosted). Point any MCP client at the hosted endpoint with your token:

json
{  "mcpServers": {    "fulcru": {      "url": "https://little-orca-977.convex.site/mcp",      "headers": { "Authorization": "Bearer pk_..." }    }  }}

Local (stdio). For hosts that prefer a subprocess, this package ships a stdio MCP server that proxies to the hosted endpoint:

json
{  "mcpServers": {    "fulcru": {      "command": "npx",      "args": ["-y", "-p", "fulcru", "fulcru-mcp"],      "env": { "FULCRU_TOKEN": "pk_..." }    }  }}

The -p is not decoration. This package ships two commands, and without it npx runs the one named after the package, which is the CLI: the host gets a usage screen instead of an MCP server.

Tools: fulcru_gaps, fulcru_write_page, fulcru_publish_page, fulcru_delta, fulcru_visibility.

Both speak protocol revision 2026-07-28 and the older handshake-based revisions, and pick per request from what the client sends. A client on the new revision gets server/discover, per-request _meta, and a cacheable tool list; one still sending initialize is served exactly as before. Nothing needs configuring either way.

Skill

The skills/fulcru skill runs the whole playbook using nothing but web access — audit a domain, find the gaps, write the page, re-measure — with no account and no token. Install it into an agent that supports skills:

bash
# Claude / OpenClawnpx skills add gsmmediaro/fulcru
# Hermeshermes skills install gsmmediaro/fulcru

Hermes scans third-party skills before installing and prints the verdict, so you can see what you are agreeing to run. If you would rather track this repo as a source and pick up updates, tap it instead:

bash
hermes skills tap add gsmmediaro/fulcruhermes skills install fulcru

The CLI and MCP above are what you use when you want it measured continuously across every engine, with the before/after delta tracked for you.

Configuration

Env varRequiredDefaultPurpose
FULCRU_TOKENfor the CLI + local MCP—Your account token (Settings -> Integrations)
FULCRU_ENDPOINTnohttps://little-orca-977.convex.site/mcpPoint at a self-hosted or custom-domain endpoint

No secrets are baked into this repo. The token is read from the environment only.

Self-hosting

The skill needs nothing. The CLI and MCP need a Fulcru account for the continuous, measured loop; point FULCRU_ENDPOINT at your own instance if you run one.

A Docker image is provided:

bash
docker build -t fulcru .docker run --rm -e FULCRU_TOKEN=pk_... fulcru gaps

Contributing

Issues and PRs welcome. The tool logic lives in the hosted service; this repo is the CLI, the stdio MCP proxy, and the skill. If AI names a competitor instead of you, open an issue with the question — that is exactly the gap this is built to close.

If this is useful, a ⭐ genuinely helps.

License

AGPL-3.0-or-later. See LICENSE.

来源:README.md,提交 56903ae

工具

0
SourceWeft 尚未读取此服务器的工具。

版本历史

1
  1. v2.0.0最新Sep 16, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分