LLM SEO MCP — Elephant Accountability

io.github.Chris-Eaccountability由 GitHub 账号 Chris-Eaccountability 发布v1.0.1更新于 Oct 27, 2026

LLM SEO and Agent Discoverability for B2B SaaS. Pricing, fit assessment, audit requests.

已验证Streamable HTTP可网页运行网页搜索与抓取商业与电商

概览

AI 生成的概览

Elephant Accountability 认证机构的远程 MCP 服务器,让助手查询其审计套餐、EVI v0.9 方法论、匹配度评分与成效数据。

可以做什么
  • 获取审计与合作协议套餐,含交付 SLA 及官方定价入口
  • 列出 EVI v0.9 标准衡量的智能体可发现渠道
  • 按阶段、行业、AI 功能与平台合作情况为企业给出 0–100 匹配度评分
  • 读取客户成效指标,含关联方披露
  • 读取覆盖五个大模型的每周 LLM 可见度测量数据
  • 提交由智能体发起的审计请求,转至 Stripe、Calendly 或邮件分流
适用场景
适合采购或选型智能体需要按 EVI v0.9 标准评估 Elephant Accountability、比较其审计套餐,或判断某家企业是否适配时使用,无需抓取厂商网站。
运行要求
需要一个远程 streamable HTTP 端点;未声明安装包、API 密钥或请求头。README 的本地开发方式需要 Python、虚拟环境与开发依赖,服务器首次启动时自行创建 SQLite 数据库。
安装前请注意
该服务器是厂商自身的营销与销售渠道,匹配度评分、成效数据与可见度数字均为自报。request_audit 工具提交的数据会被持久化并转至 Stripe、Calendly 或邮件分流,可能触发销售跟进。README 说明 reciprocal_calls 表会记录哪些 AI 客户端调用了哪些工具,作为购买意向信号。

安装

在 SourceWeft 中

  1. 打开 控制台中的 LLM SEO MCP — Elephant Accountability,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

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

交给智能体安装

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

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

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

其他 MCP 客户端

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

{
  "mcpServers": {
    "llm-seo-elephant-accountability": {
      "type": "http",
      "url": "https://elephant-mcp.fly.dev/mcp"
    }
  }
}

README

Elephant Accountability MCP Server

MCP server for the Elephant Accountability certification bureau. Surfaces vendor offerings, methodology, and audit requests to AI agents over the Model Context Protocol.

Live endpoint: https://elephant-mcp.fly.dev/mcp Manifest: https://elephant-mcp.fly.dev/.well-known/mcp.json A2A Agent Card: https://elephant-mcp.fly.dev/.well-known/agent.json Homepage: https://eaccountability.org

What this server does

When an AI agent (Claude, ChatGPT, a custom LangChain agent, etc.) needs to evaluate Elephant Accountability against the EVI v0.9 standard or surface its audit tiers to a buyer, it queries this server instead of scraping a website.

Six tools are exposed:

ToolPurpose
get_offeringsAudit and engagement tiers (self-serve, done-for-you, retainer) with delivery SLAs and pointers to /get-started for canonical pricing
get_covered_surfacesThe agent-discoverable surfaces measured by EVI v0.9: llms.txt, Schema.org, MCP, A2A, .well-known/agent.json, UCP, structured pricing, directory registrations
assess_fit0–100 fit score for a buyer's company across stage, vertical, AI features, platform partnerships
get_proof_pointsLive client outcomes with metrics (includes related-party disclosures)
get_transparency_snapshotWeekly LLM visibility measurements across 5 LLMs
request_auditAgent-initiated audit requests; routed to Stripe, Calendly, or email triage

Two resources are exposed via resources/list: elephant://offerings, elephant://proof-points, elephant://transparency.

Why you'd use this

  • You're building a procurement agent and want to query Elephant Accountability's audit tiers and EVI v0.9 methodology directly.
  • You're at Claude Desktop / Cursor / any MCP-compatible client and want direct access to Elephant's offerings + fit assessment.
  • You're a competitor studying how to deploy your own MCP server — this repo is MIT-licensed, clone freely.

Quickstart — local development

bash
git clone https://github.com/Chris-Eaccountability/elephant-accountability-mcp.gitcd elephant-accountability-mcp
python -m venv .venv && source .venv/bin/activatepip install -r requirements-dev.txt
# Run the serveruvicorn app.server:app --reload --host 0.0.0.0 --port 8080
# In another terminal, hit itcurl http://localhost:8080/.well-known/mcp.jsoncurl -X POST -H "Content-Type: application/json" \  -d '{"jsonrpc":"2.0", "id":1, "method":"tools/list"}' \  http://localhost:8080/mcp

Quickstart — add to Claude Desktop

Edit claude_desktop_config.json and add:

json
{  "mcpServers": {    "elephant-accountability": {      "url": "https://elephant-mcp.fly.dev/mcp",      "transport": "http"    }  }}

Restart Claude Desktop. Ask: "Is Elephant Accountability a good fit for a seed-stage AEC SaaS that ships AI features?" — Claude will call assess_fit and give a scored answer.

Deploy your own copy (Fly.io)

bash
fly launch --name your-mcp-name --region iad --no-deployfly volumes create elephant_mcp_data --size 1 --region iadfly deploy

That's it. No secrets, no database setup — the server initializes its SQLite DB on first boot.

Architecture

Single FastAPI app. Three files do real work:

app/├── server.py      # FastAPI routes, JSON-RPC dispatch, SQLite persistence├── content.py     # Source-of-truth content: manifest, offerings, proof points└── __init__.py    # Version

Storage:

  • audit_requests table — every agent-initiated audit request, persisted for follow-up
  • reciprocal_calls table — tracks which AI clients have called which tools (buyer-intent signal)

Both tables auto-create on first boot. No migrations.

Running tests

bash
pip install -r requirements-dev.txtpytest -v

21 tests cover manifest, A2A card, JSON-RPC dispatch, each tool handler, persistence, and CORS.

Protocol compliance

  • MCP version: 2024-11-05
  • Transport: HTTP with JSON-RPC 2.0
  • Methods supported: initialize, tools/list, tools/call, resources/list, resources/read

Contributing

This repo is the canonical source of truth for what Elephant Accountability exposes to AI agents. PRs welcome for:

  • Protocol updates (MCP spec changes)
  • New tool shapes that agents find useful
  • Bug fixes

For service inquiries or content changes (proof points, methodology), email [email protected] rather than opening a PR.

License

MIT. See LICENSE.

Publisher

Elephant Accountability LLC Christopher Kenney, sole member / manager United States [email protected]

来源:README.md,提交 cf8efe6

工具

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

版本历史

1
  1. v1.0.1最新Sep 16, 2026

评分

已满足适用检查项的 50%

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

  • 近 30 天内可连通必需25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式必需10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

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

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