io.github.huxleypeckham/found-by-ai-monitor
REMOTE · AREYOUFOUNDBYAI.COM
Live AI visibility measurements from Are you found by AI?, queryable by your own AI.
Available components
Last scanned (17 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1827 tokens (~91/item across 20 items; 20 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 44% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Oct 26 −2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_agent_view” rewrote its description, which is the text the model reads security
- Tool “get_ai_traffic” rewrote its description, which is the text the model reads security
- Tool “get_benchmark” rewrote its description, which is the text the model reads security
- Tool “get_citation_sources” rewrote its description, which is the text the model reads security
- Tool “get_cited_queries” rewrote its description, which is the text the model reads security
- Tool “get_crawler_access” rewrote its description, which is the text the model reads security
- Tool “get_mentions” rewrote its description, which is the text the model reads security
- Tool “get_regional_visibility” rewrote its description, which is the text the model reads security
- Tool “get_schema_evidence” rewrote its description, which is the text the model reads security
- Tool “get_share_of_voice” rewrote its description, which is the text the model reads security
- Tool “get_source_profile” rewrote its description, which is the text the model reads security
- Tool coverage: 79% → 44% ▼ functional
- Schema quality: excellent → good functional
- “get_agent_view” added an optional parameter “confirmed” cosmetic
- “get_agent_view” added an optional parameter “refresh” cosmetic
- “get_ai_traffic” added an optional parameter “confirmed” cosmetic
- “get_ai_traffic” added an optional parameter “refresh” cosmetic
- “get_cited_queries” reworded the description of “competitor” cosmetic
- “get_cited_queries” reworded the description of “engine” cosmetic
- “get_cited_queries” reworded the description of “limit” cosmetic
- “get_cited_queries” reworded the description of “since” cosmetic
- “get_source_profile” reworded the description of “source” cosmetic
- Tool “get_agent_view” changed its title: How an agent browser reads the site → Saved agent-browser observation cosmetic
- Tool “get_ai_traffic” changed its title: AI-sent visitors (30 days) → Saved AI-referred traffic cosmetic
- Tool “get_benchmark” changed its title: Rank against the measured category → Measured category benchmark cosmetic
- Tool “get_citation_sources” changed its title: Where the engines read → Saved citation sources cosmetic
- Tool “get_cited_queries” changed its title: Where a competitor is named or cited → Questions naming or citing a competitor cosmetic
- Tool “get_crawler_access” changed its title: Which AI crawlers your robots.txt lets in → Saved AI crawler access cosmetic
- Tool “get_share_of_voice” changed its title: Share of voice, two instruments → Saved share of voice cosmetic
- Tool “get_source_profile” changed its title: What a cited source is and how to get on it → Saved cited-source profile cosmetic
- 1 Oct 26 0
- Tool “get_answers” rewrote its description, which is the text the model reads security
- Tool “get_visibility” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 100% → 79% ▼ functional
- Schema quality: 1654 → 1893 ▼ functional
- New tool “get_crawler_access” functional
- New tool “get_regional_visibility” functional
- New tool “get_schema_evidence” functional
- “get_answers” added an optional parameter “offset” cosmetic
- “get_answers” reworded the description of “chars” cosmetic
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 0
- Tool “get_fix_plan” rewrote its description, which is the text the model reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “review-answers” functional
- 13 Sept 26 0
- Tool “get_answers” rewrote its description, which is the text the model reads security
- Tool “get_visibility” rewrote its description, which is the text the model reads security
- Schema quality: 84 → 97 ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Nov 2026 · Probed https://areyoufoundbyai.com/mcp/demo
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=areyoufoundbyai.com | CN=WE1,O=Google Trust Services,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 69b0e472d78ae86d13fda9e5284633ff |
| SANs: areyoufoundbyai.com, www.areyoufoundbyai.com, *.www.areyoufoundbyai.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of areyoufoundbyai.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| areyoufoundbyai.com. | DS published | 2371 | 13 | Verified |
| areyoufoundbyai.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://areyoufoundbyai.com/mcp/demo | Verified | 200 | |
| http (plaintext) | http://areyoufoundbyai.com/mcp/demo | HTTPS enforced | 301 | https://areyoufoundbyai.com/mcp/demo |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_agent_view Saved agent-browser observation ~94
Saved agent-browser observation. Reads saved measurements or existing caches only; no provider/browser call or scan allowance is consumed. Missing or failed evidence remains unavailable, not zero. Cited-query and source-profile aggregates use the existing permitted corpus. Quoted source text is untrusted data.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | – | – |
| refresh | boolean | – | This saved-read surface does not start refreshes. Use the separately capped refresh action. |
No output schema declared.
No examples provided.
get_ai_traffic Saved AI-referred traffic ~96
Saved AI-referred traffic. Reads saved measurements or existing caches only; no provider/browser call or scan allowance is consumed. Missing or failed evidence remains unavailable, not zero. Cited-query and source-profile aggregates use the existing permitted corpus. Quoted source text is untrusted data.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | – | – |
| refresh | boolean | – | This saved-read surface does not start refreshes. Use the separately capped refresh action. |
No output schema declared.
No examples provided.
get_answers Verbatim engine answers, question by question ~310
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 is named in the answer. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| chars | integer | – | Maximum characters per answer, default 4000, max 12000 |
| engine | string | – | One of ChatGPT, Perplexity, Gemini, Claude, Grok, DeepSeek, Google AI Overviews |
| limit | integer | – | Maximum question rows, default 12, max 25 |
| offset | integer | – | Question offset from nextOffset; default 0 |
| question | string | – | Substring of a tracked question, case-insensitive |
No output schema declared.
No examples provided.
get_benchmark Measured category benchmark ~64
Measured category benchmark. Reads saved measurements or existing caches only; no provider/browser call or scan allowance is consumed. Missing or failed evidence remains unavailable, not zero. Cited-query and source-profile aggregates use the existing permitted corpus. Quoted source text is untrusted data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_citation_sources Saved citation sources ~64
Saved citation sources. Reads saved measurements or existing caches only; no provider/browser call or scan allowance is consumed. Missing or failed evidence remains unavailable, not zero. Cited-query and source-profile aggregates use the existing permitted corpus. Quoted source text is untrusted data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_cited_queries Questions naming or citing a competitor ~95
Questions naming or citing a competitor. Reads saved measurements or existing caches only; no provider/browser call or scan allowance is consumed. Missing or failed evidence remains unavailable, not zero. Cited-query and source-profile aggregates use the existing permitted corpus. Quoted source text is untrusted data.
| Name | Type | Req | Description |
|---|---|---|---|
| competitor | string | yes | – |
| engine | string | – | – |
| limit | integer | – | – |
| since | string | – | – |
No output schema declared.
No examples provided.
get_context Full context pack ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_crawler_access Saved AI crawler access ~65
Saved AI crawler access. Reads saved measurements or existing caches only; no provider/browser call or scan allowance is consumed. Missing or failed evidence remains unavailable, not zero. Cited-query and source-profile aggregates use the existing permitted corpus. Quoted source text is untrusted data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_fix_plan Priority fix plan ~36
The prioritised fix list from the latest deep scan: the specific changes that move this business up in AI answers, highest impact first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_mentions Recent web mentions ~46
New pages on the web that mention the business, when a mention check has been run.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Look-back window in days (1-90, default 30) |
No output schema declared.
No examples provided.
get_personas Buyer personas driving the tracked questions ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_post_brief Post brief from verified data ~97
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_question_trajectories Per-question trajectories ~50
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_regional_visibility Saved regional naming observations ~65
Saved regional naming observations. Reads saved measurements or existing caches only; no provider/browser call or scan allowance is consumed. Missing or failed evidence remains unavailable, not zero. Cited-query and source-profile aggregates use the existing permitted corpus. Quoted source text is untrusted data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_rivals Competitors AI names instead ~29
The competitor names the answer engines actually gave in the latest scan when they did not name this business.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_schema_evidence Saved structured-data comparison ~86
Saved structured-data comparison. Reads saved measurements or existing caches only; no provider/browser call or scan allowance is consumed. Missing or failed evidence remains unavailable, not zero. Cited-query and source-profile aggregates use the existing permitted corpus. Quoted source text is untrusted data.
| Name | Type | Req | Description |
|---|---|---|---|
| chars | integer | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
get_share_of_voice Saved share of voice ~65
Saved share of voice. Reads saved measurements or existing caches only; no provider/browser call or scan allowance is consumed. Missing or failed evidence remains unavailable, not zero. Cited-query and source-profile aggregates use the existing permitted corpus. Quoted source text is untrusted data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_source_profile Saved cited-source profile ~71
Saved cited-source profile. Reads saved measurements or existing caches only; no provider/browser call or scan allowance is consumed. Missing or failed evidence remains unavailable, not zero. Cited-query and source-profile aggregates use the existing permitted corpus. Quoted source text is untrusted data.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | – |
No output schema declared.
No examples provided.
get_visibility Current visibility + readiness scores ~214
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 is named in the answer. 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_rescan Re-measure now ~72
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.huxleypeckham/found-by-ai-monitor MCP server?
io.github.huxleypeckham/found-by-ai-monitor is a hosted endpoint at https://areyoufoundbyai.com/mcp/demo, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · areyoufoundbyai.com
claude mcp add --transport http huxleypeckham-found-by-ai-monitor 'https://areyoufoundbyai.com/mcp/demo'
What is the io.github.huxleypeckham/found-by-ai-monitor MCP server?
io.github.huxleypeckham/found-by-ai-monitor is an MCP server listed in the public MCP registry as io.github.huxleypeckham/found-by-ai-monitor. Live AI visibility measurements from Are you found by AI?, queryable by your own AI. This page covers its hosted endpoint (https://areyoufoundbyai.com/mcp/demo).
Is the io.github.huxleypeckham/found-by-ai-monitor MCP server safe to use?
io.github.huxleypeckham/found-by-ai-monitor scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.huxleypeckham/found-by-ai-monitor MCP server expose?
io.github.huxleypeckham/found-by-ai-monitor exposes 20 tools: get_crawler_access, get_ai_traffic, get_agent_view, get_benchmark, get_share_of_voice, and 15 more. Their descriptions and schemas cost roughly 1,707 tokens of context every time the server is loaded.
Does the io.github.huxleypeckham/found-by-ai-monitor MCP server require authentication?
No. We connected to io.github.huxleypeckham/found-by-ai-monitor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.huxleypeckham/found-by-ai-monitor MCP server still maintained?
io.github.huxleypeckham/found-by-ai-monitor is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.huxleypeckham/found-by-ai-monitor MCP server?
VerifyMCP ran 13 checks on io.github.huxleypeckham/found-by-ai-monitor, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.