
LLM SEO MCP — Elephant Accountability
io.github.Chris-EaccountabilityPublished by GitHub account Chris-Eaccountabilityv1.0.1Updated Oct 27, 2026
LLM SEO and Agent Discoverability for B2B SaaS. Pricing, fit assessment, audit requests.
Overview
Remote MCP server for the Elephant Accountability certification bureau, letting assistants look up its audit tiers, EVI v0.9 methodology, fit scores and proof…
- What you can do
- Retrieve audit and engagement tiers with delivery SLAs and pointers to canonical pricing
- List the agent-discoverable surfaces measured by the EVI v0.9 standard
- Score a buyer's company 0–100 on fit across stage, vertical, AI features and platform partnerships
- Read live client outcomes with metrics and related-party disclosures
- Read weekly LLM visibility measurements across five LLMs
- Submit an agent-initiated audit request routed to Stripe, Calendly or email triage
- When to use it
- Useful when a procurement or buying agent needs to evaluate Elephant Accountability against the EVI v0.9 standard, compare its audit tiers, or check fit for a specific company without scraping the vendor's website.
- Requirements
- A remote streamable HTTP endpoint; no package install, API key or header is declared. The README's local-development path needs Python, a virtual environment and the dev requirements, and the server creates its own SQLite database on first boot.
Installation
In SourceWeft
- Open LLM SEO MCP — Elephant Accountability in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Chris-Eaccountability%2Felephant-accountability-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"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:
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
Quickstart — add to Claude Desktop
Edit claude_desktop_config.json and add:
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)
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:
Storage:
audit_requeststable — every agent-initiated audit request, persisted for follow-upreciprocal_callstable — tracks which AI clients have called which tools (buyer-intent signal)
Both tables auto-create on first boot. No migrations.
Running tests
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]
Source: README.md at commit cf8efe6
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
