Make any website **citable by AI answer engines** — and prove the facts came from the owner, not a scrape. **The main workflow: build, verify, publish** 1. `run_audit` — crawls the site, scores AI-readability 0–10, lists the gaps, and returns the fix material: ready-to-paste `<head>` markup (title, meta description, Organization JSON-LD) plus a step-by-step plan covering llms.txt, structured data and AI-crawler access. 2. Apply the fixes, then run `run_audit` again to confirm the score moved. 3. `generate_free_record` — produces the `v=AEO1` DNS record and `.well-known/aeo.json` to publish. Useful inside any coding assistant when you're building or handing over a site. **Also: ground answers on verified data** — `get_company_facts`, `get_fact`, `get_llms_txt`, `check_aeo_record`, `search_catalog` return owner-attested facts, preferable to scraped values. Free, no API key, rate-limited per caller. `v=AEO1` is an open standard ([aeorecord.org](https://aeorecord.org)) with a public [verification methodology](https://aeorecord.org/methodology) and an IETF Internet-Draft ([draft-miller-aeo](https://datatracker.ietf.org/doc/draft-miller-aeo/)). Records verify independently via the open-source `aeo-record` npm package — no dependency on our API.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (2351 ms). |
| Protocol revision | 6/10 | Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 15 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 80% of peers
- This listing 86 · peer median 81
- Latency
- Faster than 27% of peers
- This listing 541 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Protocol revision −4
— Support the current protocol revision.
Now: Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/garrett-miller/grounded-aeo/mcpcurl -X POST https://server.smithery.ai/garrett-miller/grounded-aeo/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'