# MentionedOn Discovery Evidence Tools (remote · mentioned-on.com)

Assess AI-discovery readiness, plan visibility fixes, and summarize scan evidence. Read-only.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- remote · `mentioned-on.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-mentioned-on-ai-discovery-readiness/mentioned-on.md), [page](https://verifymcp.io/servers/com-mentioned-on-ai-discovery-readiness/mentioned-on)

## Channel facts

- Endpoint: `https://mentioned-on.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-26.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 337 tokens (~112/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 78% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the MentionedOn Discovery Evidence Tools MCP server?

MentionedOn Discovery Evidence Tools is a hosted endpoint at https://mentioned-on.com/mcp, 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 com-mentioned-on-ai-discovery-readiness 'https://mentioned-on.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-mentioned-on-ai-discovery-readiness": {
      "url": "https://mentioned-on.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-mentioned-on-ai-discovery-readiness": {
      "type": "http",
      "url": "https://mentioned-on.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-mentioned-on-ai-discovery-readiness]
url = "https://mentioned-on.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mentioned-on-ai-discovery-readiness": {
      "type": "remote",
      "url": "https://mentioned-on.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mentioned-on-ai-discovery-readiness --url 'https://mentioned-on.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-mentioned-on-ai-discovery-readiness:
    url: "https://mentioned-on.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-mentioned-on-ai-discovery-readiness": {
      "Transport": "http",
      "Url": "https://mentioned-on.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mentioned-on-ai-discovery-readiness -t streamable-http -u 'https://mentioned-on.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-mentioned-on-ai-discovery-readiness": {
      "type": "http",
      "url": "https://mentioned-on.com/mcp"
    }
  }
}
```

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-26 (score 74, +1)

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

### 2026-09-25 (score 73, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 73, +1)

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

### 2026-09-22 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-21 (score 72)

First indexed and scored.

## MCP tools (3)

### `analyze_discovery_readiness` (~108 tokens)

Analyze AI Discovery Readiness

Score caller-supplied website and business discovery signals. This tool does not fetch the website, run an AI scan, persist data, or verify inclusion in any AI product.

Input parameters:

- `businessName` (string, required): The business name used only to label this assessment.
- `signals` (array, required): Caller-supplied signal observations. Omitted signals are treated as unknown.
- `websiteUrl` (string): Optional page URL used only as a label. The tool will not fetch this URL.

Output parameters:

- `assessment` (string)
- `businessName` (string)
- `evaluatedSignals` (array)
- `evidenceCoveragePercent` (number)
- `limitations` (array)
- `priorities` (array)
- `readinessScore`
- `scope` (string)
- `verificationNeeded` (array)
- `websiteUrl`

### `build_visibility_action_plan` (~112 tokens)

Build an AI Visibility Action Plan

Prioritize fixes from caller-supplied findings using a deterministic rubric. This tool does not edit a website, contact third parties, persist data, or promise rankings or mentions.

Input parameters:

- `businessName` (string, required)
- `effortBudget` (string, required): Controls how many actions are returned and how they are phased.
- `findings` (array, required): Caller-supplied findings. Present findings are acknowledged but do not create actions.
- `goal` (string, required): The outcome used to break ties in the deterministic priority rubric.

Output parameters:

- `actions` (array)
- `businessName` (string)
- `effortBudget` (string)
- `excludedPresentSignals` (array)
- `goal` (string)
- `goalLabel` (string)
- `limitations` (array)
- `omittedActionCount` (integer)
- `scope` (string)

### `summarize_scan_evidence` (~78 tokens)

Summarize AI Scan Evidence

Calculate mention and business-citation rates from caller-supplied captures. This tool does not call AI providers, fetch URLs, persist data, or establish current inclusion beyond the supplied observations.

Input parameters:

- `businessName` (string, required)
- `observations` (array, required): Point-in-time captures supplied by the caller. The tool will not obtain new captures.

Output parameters:

- `businessCitationCount` (integer)
- `businessCitationRatePercent`
- `businessName` (string)
- `bySource` (array)
- `completedCount` (integer)
- `establishesLiveInclusion` (boolean)
- `evidenceStatements` (array)
- `limitations` (array)
- `mentionCount` (integer)
- `mentionRatePercent`
- `observationCount` (integer)
- `observedAtRange`
- `scope` (string)
- `sentimentBreakdown` (object)
- `unavailable` (array)
- `unavailableCount` (integer)
- `uniqueBusinessCitationHosts` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-mentioned-on-ai-discovery-readiness/mentioned-on#diagnostics

## Score history

- 2026-09-26: 74
- 2026-09-25: 73
- 2026-09-24: 73
- 2026-09-23: 73
- 2026-09-22: 72
- 2026-09-21: 72

## Common questions

### What is the MentionedOn Discovery Evidence Tools MCP server?

MentionedOn Discovery Evidence Tools is an MCP server listed in the public MCP registry as com.mentioned-on/ai-discovery-readiness. Assess AI-discovery readiness, plan visibility fixes, and summarize scan evidence. Read-only. This page covers its hosted endpoint (https://mentioned-on.com/mcp).

### Is the MentionedOn Discovery Evidence Tools MCP server safe to use?

MentionedOn Discovery Evidence Tools scores 74 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 MentionedOn Discovery Evidence Tools MCP server expose?

MentionedOn Discovery Evidence Tools exposes 3 tools: analyze_discovery_readiness, build_visibility_action_plan, summarize_scan_evidence. Their descriptions and schemas cost roughly 298 tokens of context every time the server is loaded.

### Does the MentionedOn Discovery Evidence Tools MCP server require authentication?

No. We connected to MentionedOn Discovery Evidence Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MentionedOn Discovery Evidence Tools MCP server still maintained?

MentionedOn Discovery Evidence Tools is still listed as active in the MCP registry. We last reached this channel on 26 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://mentioned-on.com/mcp
- Website: https://mentioned-on.com/developers/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-mentioned-on-ai-discovery-readiness/mentioned-on.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mentioned-on-ai-discovery-readiness/mentioned-on.json
- HTML version of this page: https://verifymcp.io/servers/com-mentioned-on-ai-discovery-readiness/mentioned-on