# com.radveo/radveo (remote · radveo.com)

Checks if AI assistants name a local business. Free shareable report, honest fixes, no guarantees.

- Trust score: 67/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

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

## Channel facts

- Endpoint: `https://radveo.com/api/mcp`
- 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-08-03.

- **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 call this server, and 2 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 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**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 308 tokens (~154/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-radveo-radveo https://radveo.com/api/mcp
```

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Other

```json
{
  "mcpServers": {
    "com-radveo-radveo": {
      "type": "http",
      "url": "https://radveo.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-02 (score 67, +1)

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

### 2026-07-31 (score 66, +1)

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

### 2026-07-30 (score 65, −2)

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

### 2026-07-29 (score 67, +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-07-28 (score 66, +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-07-27 (score 65, 0)

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

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (2)

### `check_ai_visibility` (~158 tokens)

Check whether a local business currently appears when people ask AI engines (ChatGPT, Gemini, Google AI) to recommend a business in its category — and get a free, shareable Radveo report with the exact fixes to improve its odds of being named. Honest answer-engine optimization: improves the odds of being cited, never guarantees a placement.

Input parameters:

- `business_name` (string): The business name, e.g. "Joe's Plumbing". Provide this OR a website.
- `location` (string): City or region, e.g. "Seattle, WA". Optional but improves accuracy.
- `website` (string): The business website URL, e.g. https://joesplumbing.com. Optional if business_name is given; improves accuracy.

Output parameters:

- `aiVisibilityScore` (number|null): 0-100: the share of customer-style AI queries that named the business. Null when the probe didn't produce a measured score.
- `business` (string|null): The business name or website that was checked.
- `competitorsNamed` (array): Businesses surfaced instead of this one (deduped). Same list the public shareable report shows.
- `competitorsSource` (string|null): 'ai' = an AI engine named them; 'places' = real local leaders from Google's local results (shown when the engines named none). Null when no competitors surfaced.
- `enginesChecked` (array): The AI engine panel the probes consult — an indicative read of how AI assistants tend to answer, not a live probe of every public engine.
- `note` (string): Honesty framing: results improve odds and show what AI says today — never a guarantee of placement.
- `ok` (boolean): False when the check could not be completed (bad input, rate limit, or the audit engine timed out).
- `queriesChecked` (array): The customer-style questions asked to the AI engines (empty when the probe didn't run).
- `reportUrl` (string): Free, shareable, public report URL for this check.
- `seoGrade` (string|null): Letter grade (A-D) for the readiness score, when measured.
- `seoScore` (number|null): 0-100 on-page AI-visibility readiness score, when measured.
- `topFixes` (array): The top fixes to improve the odds of being named (max 3 here; full list in the report).
- `verdict` (string): Whether AI engines named this business when asked customer-style recommendation questions. 'named' = at least one query named it; 'absent' = confidently not named; 'unknown' = the engines could not g…

### `how_to_appear_in_ai_search` (~61 tokens)

Get Radveo's honest, practical playbook for getting a local business found and cited inside AI engine answers (ChatGPT, Gemini, Google AI Overviews) — answer-engine optimization (AEO) steps any owner can act on.

Output parameters:

- `freeCheckUrl` (string): Where to run the free AI-visibility check.
- `note` (string): Honesty framing: these steps improve odds, they never guarantee placement.
- `ok` (boolean)
- `steps` (array): The AEO steps, in order. Empty only when the server is rate-limiting.

## Diagnostics

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

## Score history

- 2026-08-03: 67
- 2026-08-02: 67
- 2026-08-01: 66
- 2026-07-31: 66
- 2026-07-30: 65
- 2026-07-29: 67
- 2026-07-28: 66
- 2026-07-27: 65
- 2026-07-26: 65

## Links

- Remote endpoint: https://radveo.com/api/mcp
- Website: https://radveo.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-radveo-radveo/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-radveo-radveo/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-radveo-radveo/api-mcp