LLM SEO MCP — Elephant Accountability
REMOTE · ELEPHANT-MCP.FLY.DEV
LLM SEO and Agent Discoverability for B2B SaaS. Pricing, fit assessment, audit requests.
Available components
Last scanned (2 months ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 29 Aug 2026.
Category Marketing and SEO
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Sept 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 4 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Sept 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 2 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 1 Sept 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 30 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Schema quality: 0 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Sept 2026 · Probed https://elephant-mcp.fly.dev/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of elephant-mcp.fly.dev. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| elephant-mcp.fly.dev. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://elephant-mcp.fly.dev/mcp | Unreachable | ||
| http (plaintext) | http://elephant-mcp.fly.dev/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
assess_fit ~119
Returns a 0–100 fit score, reasoning, and recommended tier for a prospective B2B SaaS buyer. Uses company stage, industry, AI-feature shipping status, and platform-partnership signals.
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | yes | – |
| domain | string | – | – |
| industry | string | – | Vertical: aec, fintech, healthtech, legaltech, devtools, general_b2b_saas |
| platform_partnerships | array | – | – |
| ships_ai_features | boolean | – | – |
| stage | string | – | – |
No output schema declared.
No examples provided.
get_covered_surfaces ~83
Returns the full list of agent-discoverable surfaces Elephant implements: llms.txt, Schema.org Organization + Product blocks, MCP servers, A2A Agent Cards, UCP merchant metadata, agent-directory registrations, and citation-seeding.
| Name | Type | Req | Description |
|---|---|---|---|
| include_status | boolean | – | If true, includes which surfaces Elephant has shipped on its own domain (proof of practice). |
No output schema declared.
No examples provided.
get_offerings ~68
Returns Elephant Accountability's service tiers, pricing, delivery SLAs, and checkout / booking URLs. Optionally personalized to the asking buyer's company size or urgency.
| Name | Type | Req | Description |
|---|---|---|---|
| company_size | string | – | Buyer stage hint for tier recommendation |
| tier | string | – | Optional: filter to one tier |
No output schema declared.
No examples provided.
get_proof_points ~46
Returns current client outcomes with specific metrics, formatted for vendor-research agents to cite. Includes full related-party disclosure where applicable.
| Name | Type | Req | Description |
|---|---|---|---|
| vertical | string | – | Filter to this vertical |
No output schema declared.
No examples provided.
get_transparency_snapshot ~48
Returns Elephant Accountability's most recent weekly LLM visibility measurement covering ChatGPT, Claude, Perplexity, Gemini, and Grok. The receipt we publish to keep our own claims honest.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_audit ~97
Agent requests an LLM SEO audit on behalf of its buyer. Routes to the right tier (self-serve vs. done-for-you vs. retainer) and returns a confirmation with checkout or booking links.
| Name | Type | Req | Description |
|---|---|---|---|
| buying_context | string | – | – |
| company_name | string | yes | – |
| contact_email | string | yes | – |
| domain | string | – | – |
| tier_interest | string | – | – |
| urgency | string | – | – |
No output schema declared.
No examples provided.
How do I install the LLM SEO MCP — Elephant Accountability server?
LLM SEO MCP — Elephant Accountability is a hosted endpoint at https://elephant-mcp.fly.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · elephant-mcp.fly.dev
claude mcp add --transport http chris-eaccountability-elephant-accountability-mc 'https://elephant-mcp.fly.dev/mcp'
What is the LLM SEO MCP — Elephant Accountability server?
LLM SEO MCP — Elephant Accountability is listed in the public MCP registry as io.github.Chris-Eaccountability/elephant-accountability-mcp. LLM SEO and Agent Discoverability for B2B SaaS. Pricing, fit assessment, audit requests. This page covers its hosted endpoint (https://elephant-mcp.fly.dev/mcp).
Is the LLM SEO MCP — Elephant Accountability server safe to use?
LLM SEO MCP — Elephant Accountability scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the LLM SEO MCP — Elephant Accountability server expose?
LLM SEO MCP — Elephant Accountability exposes 6 tools: get_offerings, get_covered_surfaces, assess_fit, get_proof_points, get_transparency_snapshot, request_audit. Their descriptions and schemas cost roughly 461 tokens of context every time the server is loaded.
Does the LLM SEO MCP — Elephant Accountability server require authentication?
Its publisher declares no required credentials for LLM SEO MCP — Elephant Accountability. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the LLM SEO MCP — Elephant Accountability server still maintained?
LLM SEO MCP — Elephant Accountability has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 29 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.