Is the LLM SEO MCP — Elephant Accountability down?

mcp-registry/io.github.chris-eaccountability/elephant-accountability-mcp · v1.0.1

Also listed as glama/chris-eaccountability/elephant-accountability-mcp

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
down
Last checked 2026-11-22 15:22 UTC

As of 2026-11-22 15:22 UTC, the LLM SEO MCP — Elephant Accountability is down with a Glimind reliability score of 11/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks.

uptime (30d checks)
0%
checks observed
78
outages (90d)
0
tools
6

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

Point your MCP client at this streamable-http endpoint: https://elephant-mcp.fly.dev/mcp

Agent-readiness: D (68/100)

D (68/100): 2 error(s), 2 warning(s) across 6 tool(s); ~803 tokens of tool definitions.
Scores higher than 3% of 27,661 MCP servers Glimind has audited.
Its tool list costs an agent ~803 tokens per session — lighter than 75% of servers.
no tool-poisoning patterns
Schemas100
Descriptions67
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability0
Stability100

What to fix (5)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →

Up 0.0% of the time over the last 30 days.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: assess_fit, get_covered_surfaces, get_offerings, get_proof_points, get_transparency_snapshot and 1 more

11 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: assess_fit, request_audit

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.chris-eaccountability%2Felephant-accountability-mcp/fixes

get_covered_surfaces 1 change
{
  "name": "get_covered_surfaces",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "include_status": {
        "type": "boolean",
        "description": "If true, includes which surfaces Elephant has shipped on its own domain (proof of practice)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_offerings 1 change
{
  "name": "get_offerings",
  "description": "Returns Elephant Accountability's service tiers, pricing, delivery SLAs, and checkout / booking URLs. Optionally personalized to the asking buyer's company size or urgency.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "tier": {
        "enum": [
          "self_serve",
          "done_for_you",
          "retainer"
        ],
        "type": "string",
        "description": "Optional: filter to one tier"
      },
      "company_size": {
        "enum": [
          "seed",
          "series_a",
          "series_b",
          "series_c_plus"
        ],
        "type": "string",
        "description": "Buyer stage hint for tier recommendation"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_proof_points 1 change
{
  "name": "get_proof_points",
  "description": "Returns current client outcomes with specific metrics, formatted for vendor-research agents to cite. Includes full related-party disclosure where applicable.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "vertical": {
        "type": "string",
        "description": "Filter to this vertical"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.chris-eaccountability/elephant-accountability-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.chris-eaccountability/elephant-accountability-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fio.github.chris-eaccountability%2Felephant-accountability-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.chris-eaccountability%2Felephant-accountability-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.chris-eaccountability%2Felephant-accountability-mcp?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.chris-eaccountability%2Felephant-accountability-mcp.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8f1112a7ca967db0…, first seen 2026-10-17, included at leaf 12938 of 384,794. Version history · verify what your client received.

Working alternatives

Tools (6)

Compare: most reliable ml servers · most reliable knowledge servers · most reliable sales servers · most reliable marketing servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the LLM SEO MCP — Elephant Accountability down right now?

As of 2026-11-22 15:22 UTC, the LLM SEO MCP — Elephant Accountability is down with a Glimind reliability score of 11/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks.

How many tools does LLM SEO MCP — Elephant Accountability provide?

LLM SEO MCP — Elephant Accountability advertises 6 tools, including assess_fit, get_covered_surfaces, get_offerings, get_proof_points, get_transparency_snapshot.

How do I install LLM SEO MCP — Elephant Accountability?

Point your MCP client at this streamable-http endpoint: https://elephant-mcp.fly.dev/mcp

Is the LLM SEO MCP — Elephant Accountability safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of LLM SEO MCP — Elephant Accountability?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve