mcp-registry/com.groundedaeo/grounded-aeo · v1.1.0
As of 2026-10-23 02:42 UTC, the Groundedaeo Grounded Aeo MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 8 minutes.
Audit and fix a site for AI citation + SEO, verify it, then publish a v=AEO1 record.
Claude Code
claude mcp add --transport http groundedaeo-grounded-aeo-mcp-server https://groundedaeo.com/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"groundedaeo-grounded-aeo-mcp-server": {
"type": "http",
"url": "https://groundedaeo.com/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
15 of 15 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 →
8 parameter(s) across 4 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 →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~1,667 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.groundedaeo%2Fgrounded-aeo/fixes
{
"name": "check_aeo_record",
"description": "Check any domain (cataloged or not) for a v=AEO1 DNS record at _aeo.<domain>, the open standard (aeorecord.org) declaring whether a verified fact record exists and at what trust tier. Verifies the Ed25519 sig= against the live catalog content when present.",
"inputSchema": {
"type": "object",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "check_serp",
"description": "Check the live Google search results for any keyword: the top 10 organic results (rank, domain, title), the People Also Ask questions, related searches, and which non-organic blocks occupy the page, so you can tell whether a query has an AI Overview or local pack slot at all. Public data, no catalog entry required. A keyword with genuinely no results returns empty arrays, which is a real finding, not an error.",
"inputSchema": {
"type": "object",
"required": [
"keyword"
],
"properties": {
"keyword": {
"type": "string",
"description": "Search query, e.g. \"roof repair denver\""
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_citations",
"description": "Get the latest citation check per (question, engine) for a cataloged domain: the question asked, the engine, whether the answer cited this domain, the URL of theirs it cited, and the day checked. Claimed domains only, read-only, one row per cell so re-running the checker cannot inflate anything. The engine answers are stored verbatim as the evidence behind each verdict but are NOT served here; the owner sees those in their dashboard. An empty list means no check has run yet, never \"never cited\".",
"inputSchema": {
"type": "object",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string",
"description": "Company domain, e.g. acme.com"
}
}
},
"annotations": {
"readOnlyHint": true
}
}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/com.groundedaeo/grounded-aeo"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.groundedaeo/grounded-aeo"}) over MCP.
generate_free_record ~205 tokensget_engine_visibility ~194 tokensget_keyword_gap ~192 tokensget_citations ~191 tokensget_cited_domains ~191 tokensStatic 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. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.groundedaeo%2Fgrounded-aeo?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.groundedaeo%2Fgrounded-aeo?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.groundedaeo%2Fgrounded-aeo.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.groundedaeo%2Fgrounded-aeo.svg :target: https://glimind.com/server/mcp-registry%2Fcom.groundedaeo%2Fgrounded-aeo?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:5594ddf0511e8b54…, first seen 2026-10-17, included at leaf 276 of 49,552. Version history · verify what your client received.
Compare: most reliable other servers · most reliable search servers · most reliable code servers · most reliable knowledge servers · most reliable retrieval servers
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.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-23 02:42 UTC, the Groundedaeo Grounded Aeo MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 8 minutes.
Groundedaeo Grounded Aeo MCP server advertises 15 tools, including check_aeo_record, check_serp, generate_fixes, generate_free_record, get_citations.
Point your MCP client at this streamable-http endpoint: https://groundedaeo.com/api/mcp
Glimind scanned all 15 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.
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.