# Mentionry (remote · mentionry.com)

Find who links to your competitors but not you, judge each opening, and draft the pitch.

- Trust score: 25/100 (low)
- Change this week: −49
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-24

## Components

- remote · `mentionry.com`: 25/100 (this document), [markdown](https://verifymcp.io/servers/com-mentionry-mentionry/api-mcp.md), [page](https://verifymcp.io/servers/com-mentionry-mentionry/api-mcp)

## Channel facts

- Endpoint: `https://mentionry.com/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-08-24.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
  - 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**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 500.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 4 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Mentionry MCP server?

Mentionry is a hosted endpoint at https://mentionry.com/api/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-mentionry-mentionry 'https://mentionry.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-mentionry-mentionry": {
      "url": "https://mentionry.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-mentionry-mentionry": {
      "type": "http",
      "url": "https://mentionry.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-mentionry-mentionry]
url = "https://mentionry.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mentionry-mentionry": {
      "type": "remote",
      "url": "https://mentionry.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mentionry-mentionry --url 'https://mentionry.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-mentionry-mentionry:
    url: "https://mentionry.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-mentionry-mentionry": {
      "Transport": "http",
      "Url": "https://mentionry.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mentionry-mentionry -t streamable-http -u 'https://mentionry.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-mentionry-mentionry": {
      "type": "http",
      "url": "https://mentionry.com/api/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-08-21 (score 25, −50)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.13 → unverified
- [security regression] Authorization: fail → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-08-19 (score 75, +1)

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

### 2026-08-17 (score 74, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-16 (score 73)

First indexed and scored.

## MCP tools (7)

### `qualify_domain` (~87 tokens)

Qualify a domain

Judge whether a domain is worth running link building for at all, from live search data. Returns a verdict, the measured signals behind it, and the honest case against. This is the same free diagnostic the dashboard runs, and for a large share of sites the answer is that the niche has nothing to mine.

Input parameters:

- `domain` (string, required): The domain to judge, for example mentionry.com

### `read_site` (~65 tokens)

Read a site

Read a domain and return what we think it is about: a description, its audience, and the keywords it should be found for. This is the brief every other tool takes as input, so call it first when you do not already have one.

Input parameters:

- `domain` (string, required)

### `discover_competitors` (~68 tokens)

Discover competitors

Find the domains competing with this one, from both search results and link profile overlap. Returns each candidate with the evidence for it, so a wrong suggestion can be recognised rather than trusted.

Input parameters:

- `domain` (string, required)
- `keywords` (array): Optional. Sharpens the search half.

### `backlink_gap` (~69 tokens)

Backlink gap

Find pages that link to the named competitors but not to you, classified by whether a link is realistically winnable and why. Competitors are excluded from their own results: a competitor is never a prospect.

Input parameters:

- `competitors` (array): Up to five competitor domains.
- `domain` (string, required)

### `find_prospects` (~106 tokens)

Find prospects

Search the open web for pages that would plausibly link to this site: resource pages, roundups, listicles and directories in its subject. Returns each with the reason it was kept.

Input parameters:

- `audience` (string)
- `description` (string): What the site does. Use read_site if you do not have one.
- `domain` (string, required)
- `keywords` (array)
- `topic` (string): Optional. Narrows the search to one theme.

### `verify_links` (~79 tokens)

Check whether links landed

Check a list of domains against your live backlink profile and report which of them now link to you, when the link first appeared, and whether it is still there. A link that was removed shows as a change rather than staying on the scoreboard.

Input parameters:

- `domain` (string, required): Your domain.
- `pitched` (array, required): The domains or URLs you pitched.

### `draft_pitch` (~127 tokens)

Draft a pitch

Write one outreach email for one prospect, in your own words, using the reason that prospect would link to you. It returns the subject and body and sends nothing: sending happens from your own mailbox, after you have read it. Requires a paid Mentionry plan.

Input parameters:

- `description` (string): What your site does.
- `hook` (string, required): Why this page would link to you.
- `page_title` (string)
- `prospect_url` (string, required): The page you want the link on.
- `sender_name` (string)
- `sender_site` (string, required): Your domain.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-mentionry-mentionry/api-mcp#diagnostics

## Score history

- 2026-08-24: 25
- 2026-08-23: 25
- 2026-08-22: 25
- 2026-08-21: 25
- 2026-08-20: 75
- 2026-08-19: 75
- 2026-08-18: 74
- 2026-08-17: 74
- 2026-08-16: 73

## Common questions

### What is the Mentionry MCP server?

Mentionry is an MCP server listed in the public MCP registry as com.mentionry/mentionry. Find who links to your competitors but not you, judge each opening, and draft the pitch. This page covers its hosted endpoint (https://mentionry.com/api/mcp).

### Is the Mentionry MCP server safe to use?

Mentionry scores 25 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 Mentionry MCP server expose?

Mentionry exposes 7 tools: qualify_domain, read_site, discover_competitors, backlink_gap, find_prospects, and 2 more. Their descriptions and schemas cost roughly 601 tokens of context every time the server is loaded.

### Does the Mentionry MCP server require authentication?

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

### Is the Mentionry MCP server still maintained?

Mentionry is still listed as active in the MCP registry. We last reached this channel on 24 August 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://mentionry.com/api/mcp
- Authorisation metadata: https://mentionry.com/.well-known/oauth-protected-resource/api/mcp
- Website: https://mentionry.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-mentionry-mentionry/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mentionry-mentionry/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-mentionry-mentionry/api-mcp