# WhereAmIMentioned Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## WhereAmIMentioned

Check how AI assistants see your site and whether they can read and cite it.

- Record: https://musedirectory.ai/connector/whereamimentioned
- Category: Marketing & Ads
- Developer: Athanasios Chatzis (https://whereamimentioned.com)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 248ms, checked 2026-11-08T01:45:47Z
- Endpoint: https://whereamimentioned.com/api/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-11-07T14:41:11Z)
- Source: Found in the official MCP Registry (com.whereamimentioned/whereamimentioned) https://registry.modelcontextprotocol.io/v0/servers?search=com.whereamimentioned%2Fwhereamimentioned

Connects to a public website and inspects it the way AI assistants do. Muse can check robots.txt rules for AI crawlers, validate or generate llms.txt and sitemap.xml, score page chunking and structured data, and review titles and meta descriptions for truncation.

Example request: "Check whether my bakery's site blocks AI crawlers and tell me what to fix so assistants can find and cite my pages."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use WhereAmIMentioned to help me. It is a free service with an MCP server at https://whereamimentioned.com/api/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- check_ai_crawler_access: Check whether a site's robots.txt allows or blocks each known AI crawler (GPTBot, ClaudeBot, PerplexityBot, Google-Extended and about thirty others), with the exact rule and line that decided it.
- validate_llms_txt: Fetch and validate a site's llms.txt: findings with severity and line numbers, a 0 to 100 score, section and entry counts, whether the linked URLs resolve, and whether a sibling llms-full.txt exists.
- generate_llms_txt: Crawl a site and generate an llms.txt. depth "index" produces the link index (up to 30 pages); depth "full" produces llms-full.txt with extracted page content (up to 20 pages).
- generate_sitemap: Crawl a site (up to 200 pages, sitemap-first with a link-following fallback) and return a valid sitemap.xml, with lastmod only where it was genuinely observed.
- analyze_content_chunking: Analyze how well a page is chunked for retrieval: per-heading sections with word and token counts, findings by severity, strengths, a score and the top fixes.
- validate_structured_data: Fetch a page, validate its JSON-LD entities against the schema.org types that matter for AI visibility, and report per-entity findings with severity, entity counts and a score. Also reports how many microdata and RDFa annotations are present, without validating them.
- check_meta_description: Analyze a page's title, meta description, og:description and opening paragraph: character and pixel widths, where desktop and mobile truncate, a score and per-check findings.

Screening checks:
- MCP handshake: pass (Answered in 272ms)
- Domain against threat feeds (Cloudflare security DNS): pass (whereamimentioned.com not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (7 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 109 days ago)
- AI review of purpose and tool behavior: pass (No concerns)