mcpbeat Sign in

Found By AI Monitor MCP Server

by huxleypeckham Your server? Claim it
answering

Found By AI Monitor is answering right now. Last checked 1 min ago. It exposes 17 tools. Last commit 26 Aug 2026.

Live AI-visibility measurements across 7 answer engines, queryable by the business owner's own AI.

Uptime history 23 days of history
23 days agonow
100.0%
Uptime 24h
92 of 92 checks
17
Tools
read from the server
723 ms
Response time
average over 24h
0
Stars
last commit 26 Aug 2026

What changed 10

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 29 August 2026. No other catalogue keeps this.

14 Sep 2 tool descriptions were rewritten get_answers, get_visibility
12 Sep 2 tool descriptions were rewritten get_answers, get_visibility
6 Sep a tool description was rewritten get_share_of_voice
4 Sep a tool appeared request_rescan
4 Sep a tool description was rewritten get_visibility
1 Sep a tool appeared get_source_profile
29 Aug 2 tools appeared get_answers, get_cited_queries

Nothing serious here today

Today is the operative word: we check Found By AI Monitor every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add found-by-ai-monitor --transport http https://areyoufoundbyai.com/mcp/demo
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "found-by-ai-monitor": {
      "url": "https://areyoufoundbyai.com/mcp/demo"
    }
  }
}
~/.codex/config.toml
[mcp_servers.found-by-ai-monitor]
url = "https://areyoufoundbyai.com/mcp/demo"
.cursor/mcp.json
{
  "mcpServers": {
    "found-by-ai-monitor": {
      "url": "https://areyoufoundbyai.com/mcp/demo"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "found-by-ai-monitor": {
      "url": "https://areyoufoundbyai.com/mcp/demo"
    }
  }
}

Available tools 17

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

agent
get_agent_view
A headless agent-browser read of the site (refreshed daily): full, partial or blank, with how many characters of real content an agent can extract. A site that renders blank to agents is invisible to agentic AI regardless of content quality. No other tool in this lane measures it.
answers
get_answers
The exact answer each engine gave to each tracked buyer question in the latest deep measurement for areyoufoundbyai.com: engine, model, date, whether this business was named and on how many samples, live web search or model memory, the competitors named in that answer, the web searches the engine ran before answering (fan-out), and the question's Google demand. This is the receipt behind every score. Filter by a question substring or an engine; answers are trimmed to `chars` characters. Named: your business name is recorded in the answer prose. Cited: your website is linked in the answer’s sources. Listed: your name appears in a list, heading or source title rather than in the prose. Found via search: a page appears in recorded search results; that alone is not a citation or recommendation. These can overlap. A web-search flag only records that search was used. Older positive flags may not distinguish these types; read the retained answer. Unavailable is not a negative result.
benchmark
get_benchmark
Where this business sits against every other measured business in its category: rank, percentile, and the distribution above and below. Real corpus, not an estimate.
citation
get_citation_sources
The domains AI engines actually cite in answers matching this category, most-cited first, with whether this business appears on each. Getting mentioned there moves visibility more than on-site changes.
cited
get_cited_queries
Reverse lookup over every measurement we have already run: give a competitor's brand name or domain and get the buyer questions where the answer engines named them, which engines, how often, when they were last seen, and who else was named on those questions. Also reports where that domain was cited as a source. Coverage is the questions we have measured, so a thin result means we have not asked those questions yet, never that the competitor is absent from AI.
context
get_context
The complete weekly context document: scores, every tracked question with its verbatim answer status, mentions, and what to do next. Same content as the downloadable context.md.
fix
get_fix_plan
The prioritised fix list from the latest deep scan: the specific changes that move this business up in AI answers, highest leverage first.
mentions
get_mentions
New pages on the web that mention the business, from the daily sweep. Independent mentions are the strongest signal that moves AI answers.
personas
get_personas
The 2-4 buyer personas inferred from this business's measured questions, the way AI models would describe each buyer type, with the exact tracked questions each persona asks. Read-only.
post
get_post_brief
Everything an AI needs to draft social posts that move AI visibility, assembled from this week's measured data: fresh third-party mentions to anchor on, the exact buyer questions the engines answer without naming the business (and who they name instead), the domains the engines actually read, and the entity rules that make a post retrievable. Returns a drafting brief, never generated copy: the drafting happens in your AI, in the business's own voice.
question
get_question_trajectories
Every tracked buyer question with its measured history: how many of the 7 engines named the business on each measured day. This is where visibility is actually won or lost, question by question.
request
request_rescan
DEMO: returns a worked example of the response and queues nothing. Queue a fresh deep measurement right now instead of waiting for the weekly scan. Uses one of the plan's capped on-demand re-measures; runs the measurement and changes nothing else. Results land in a few minutes, then read get_visibility again.
rivals
get_rivals
The competitor names the answer engines actually gave in the latest scan when they did not name this business.
share
get_share_of_voice
Two measurements, kept apart. First, your share of mentions in your own tracked answers against the rivals the engines named there. Second, web mention share: how often a web-scale index of ChatGPT answers mentions you against the brands we compare you with, which is not a rival list. Use get_rivals for who the engines name instead of you.
source
get_source_profile
A profile of any domain the answer engines cite: how often our measurements saw engines read it and across how many businesses and categories, what the site says it is (title and description from our crawl of its homepage), the co-read pack it travels in (sources the engines read together), and, where our crawler found one, the page where a business gets listed on it. Aggregate market data from our measurement corpus; a thin result means the engines rarely cite it in what we have measured so far.
traffic
get_ai_traffic
Visitors the AI engines actually sent to the business's site in the last 30 days, recorded by the site's own beacon: totals by engine and by week, with the tracking wiring status. This closes the loop from being named in answers to humans arriving.
visibility
get_visibility
The latest AI Visibility and AI Readiness scores (each /100) for areyoufoundbyai.com, with the previous week's scores, the separate off-site Footprint score, and the subscores (citability, E-E-A-T, technical, schema, platform compose Readiness; Footprint sits beside it). Being named in the answer prose counts in full toward your visibility score. A positive result recorded only as a list entry, citation or source title counts half. Older results without this distinction retain their recorded scoring basis. Named: your business name is recorded in the answer prose. Cited: your website is linked in the answer’s sources. Listed: your name appears in a list, heading or source title rather than in the prose. Found via search: a page appears in recorded search results; that alone is not a citation or recommendation. These can overlap. A web-search flag only records that search was used. Older positive flags may not distinguish these types; read the retained answer. Unavailable is not a negative result.

Endpoints

URLTransportStateLatencyChecked
https://areyoufoundbyai.com/mcp/demo streamable-http answering 689 ms 1 min ago

Alternatives to Found By AI Monitor

same job, measured the same way
I
logbook-mcp
by abduljabbarbxr

Project memory across sessions for AI agents. A queryable decision log in the repo.

520 installs/wk local only
UK Air Quality MCP Server from MCPBundles
by mcpbundles

Access UK air quality data, monitoring sites, and hourly pollutant measurements across regions

answering
New Relic MCP Server
by newrelic

Access New Relic observability data through MCP - query metrics, logs, traces, entities, and more

answering
Spanly
by spanly

MCP observability. Query live traffic, errors, duration, and alerts from your AI agent.

answering
Madjik Io
by madjik-io

Quantum-finance market metrics for AI agents, computed by the Black Belt Labs engine.

41 installs/wk local only
PumpX
by pumpx

Read-only access to your PumpX workout log: sessions, lift history, PRs, routines, measurements.

answering
Entalpa Requirements MCP
by entalpa

Live Entalpa requirements, stories, stakeholders, interfaces, and project traceability.

answering
Honeycomb
by honeycomb

Query Honeycomb observability data: traces, events, metrics, SLOs, triggers, and boards.

answering

Found By AI Monitor — questions

Answers built from our own checks of this server.

What can Found By AI Monitor do?
It exposes 17 tools, read directly from the server on our last check. Among them: get_agent_view, get_ai_traffic, get_answers, get_benchmark, get_citation_sources, get_cited_queries and 11 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Found By AI Monitor working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 723 ms. The bar chart above shows every period we have measured.
How do I connect Found By AI Monitor?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Found By AI Monitor need an API key?
No. Found By AI Monitor completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 17 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Found By AI Monitor?
It answers our handshake in 723 ms on average, which is faster than 16% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Found By AI Monitor open source?
Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.