# io.github.huxleypeckham/found-by-ai-monitor (remote · areyoufoundbyai.com)

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

- Trust score: 81/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `areyoufoundbyai.com`: 81/100 (this document), [markdown](https://verifymcp.io/servers/huxleypeckham-found-by-ai-monitor/mcp-demo.md), [page](https://verifymcp.io/servers/huxleypeckham-found-by-ai-monitor/mcp-demo)

## Channel facts

- Endpoint: `https://areyoufoundbyai.com/mcp/demo`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-22.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 88/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1654 tokens (~97/item across 17 items; 17 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http huxleypeckham-found-by-ai-monitor 'https://areyoufoundbyai.com/mcp/demo'
```

### Cursor

```json
{
  "mcpServers": {
    "huxleypeckham-found-by-ai-monitor": {
      "url": "https://areyoufoundbyai.com/mcp/demo"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "huxleypeckham-found-by-ai-monitor": {
      "type": "http",
      "url": "https://areyoufoundbyai.com/mcp/demo"
    }
  }
}
```

### Codex

```toml
[mcp_servers.huxleypeckham-found-by-ai-monitor]
url = "https://areyoufoundbyai.com/mcp/demo"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "huxleypeckham-found-by-ai-monitor": {
      "type": "remote",
      "url": "https://areyoufoundbyai.com/mcp/demo",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add huxleypeckham-found-by-ai-monitor --url 'https://areyoufoundbyai.com/mcp/demo' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  huxleypeckham-found-by-ai-monitor:
    url: "https://areyoufoundbyai.com/mcp/demo"
```

### Netclaw

```json
{
  "McpServers": {
    "huxleypeckham-found-by-ai-monitor": {
      "Transport": "http",
      "Url": "https://areyoufoundbyai.com/mcp/demo"
    }
  }
}
```

### Vellum

```bash
assistant mcp add huxleypeckham-found-by-ai-monitor -t streamable-http -u 'https://areyoufoundbyai.com/mcp/demo'
```

### Other

```json
{
  "mcpServers": {
    "huxleypeckham-found-by-ai-monitor": {
      "type": "http",
      "url": "https://areyoufoundbyai.com/mcp/demo"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-22 (score 81, +1)

- [security] Tool “get_fix_plan” rewrote its description, which is the text the model reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “review-answers”

### 2026-09-21 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 76, +1)

- [security] 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
- [functional regression] Schema quality: 84 → 97

### 2026-09-11 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (17)

### `get_visibility` (~216 tokens)

Current visibility + readiness scores

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.

### `get_question_trajectories` (~50 tokens)

Per-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.

### `get_personas` (~46 tokens)

Buyer personas driving the tracked questions

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.

### `get_mentions` (~54 tokens)

Recent web mentions

New pages on the web that mention the business, from the daily sweep. Independent mentions are the strongest signal that moves AI answers.

Input parameters:

- `days` (number): Look-back window in days (1-90, default 30)

### `get_rivals` (~29 tokens)

Competitors AI names instead

The competitor names the answer engines actually gave in the latest scan when they did not name this business.

### `get_cited_queries` (~174 tokens)

Where a competitor is named or cited

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.

Input parameters:

- `competitor` (string, required): A brand name or domain, e.g. Rocketlane or rocketlane.com
- `engine` (string): Optional: only questions where this engine named them
- `limit` (integer): Maximum questions, default 25, max 100
- `since` (string): Optional ISO date, only measurements on or after it

### `get_answers` (~295 tokens)

Verbatim engine answers, question by question

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.

Input parameters:

- `chars` (integer): Maximum characters per answer, default 700, max 4000
- `engine` (string): One of ChatGPT, Perplexity, Gemini, Claude, Grok, DeepSeek, Google AI Overviews
- `limit` (integer): Maximum question rows, default 12, max 25
- `question` (string): Substring of a tracked question, case-insensitive

### `get_share_of_voice` (~81 tokens)

Share of voice, two instruments

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.

### `get_context` (~42 tokens)

Full context pack

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.

### `get_fix_plan` (~36 tokens)

Priority fix plan

The prioritised fix list from the latest deep scan: the specific changes that move this business up in AI answers, highest impact first.

### `get_citation_sources` (~46 tokens)

Where the engines read

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.

### `get_source_profile` (~131 tokens)

What a cited source is and how to get on it

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.

Input parameters:

- `source` (string, required): The source domain, e.g. canstar.com.au or yelp.com

### `get_post_brief` (~97 tokens)

Post brief from verified data

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.

### `get_ai_traffic` (~61 tokens)

AI-sent visitors (30 days)

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.

### `get_agent_view` (~69 tokens)

How an agent browser reads the site

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.

### `get_benchmark` (~40 tokens)

Rank against the measured category

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.

### `request_rescan` (~72 tokens)

Re-measure now

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/huxleypeckham-found-by-ai-monitor/mcp-demo#diagnostics

## Score history

- 2026-09-22: 81
- 2026-09-21: 80
- 2026-09-20: 79
- 2026-09-19: 79
- 2026-09-18: 78
- 2026-09-17: 78
- 2026-09-16: 77
- 2026-09-15: 77
- 2026-09-14: 76
- 2026-09-13: 76
- 2026-09-12: 75
- 2026-09-11: 75
- 2026-09-10: 74
- 2026-09-09: 74
- 2026-09-08: 73
- 2026-09-07: 73
- 2026-09-06: 73
- 2026-09-05: 61
- 2026-09-04: 72
- 2026-09-03: 72
- 2026-09-02: 71
- 2026-09-01: 71
- 2026-08-31: 70
- 2026-08-30: 70
- 2026-08-29: 70
- 2026-08-28: 69
- 2026-08-27: 69
- 2026-08-26: 68

## Common questions

### 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 across 7 answer engines, queryable by the business owner's 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 81 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 17 tools: get_visibility, get_question_trajectories, get_personas, get_mentions, get_rivals, and 12 more. Their descriptions and schemas cost roughly 1,539 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 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://areyoufoundbyai.com/mcp/demo
- Repository: https://github.com/techhorizonlabs/foundbyai-mcp
- Website: https://areyoufoundbyai.com/guides/connect-your-ai
- Changelog RSS feed: https://verifymcp.io/servers/huxleypeckham-found-by-ai-monitor/mcp-demo.xml
- Changelog JSON feed: https://verifymcp.io/servers/huxleypeckham-found-by-ai-monitor/mcp-demo.json
- HTML version of this page: https://verifymcp.io/servers/huxleypeckham-found-by-ai-monitor/mcp-demo