com.radveo/radveo
REMOTE · RADVEO.COM · SCANNED AUG 3
Checks if AI assistants name a local business. Free shareable report, honest fixes, no guarantees.
Available components
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · radveo.com
claude mcp add --transport http com-radveo-radveo https://radveo.com/api/mcp
[mcp_servers.com-radveo-radveo] url = "https://radveo.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-radveo-radveo": {
"type": "remote",
"url": "https://radveo.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-radveo-radveo --url https://radveo.com/api/mcp --transport streamable-http
mcp_servers:
com-radveo-radveo:
url: "https://radveo.com/api/mcp" {
"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.
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.
- 2 Aug 26 +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.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 26 +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.
- 27 Jul 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 Jul 26 65
First indexed and scored.
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 3 Aug 2026 · Probed https://radveo.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=radveo.com | CN=YR2,O=Let's Encrypt,C=US | 21 Jun 2026 | 19 Sept 2026 | RSA 2048 | SHA256-RSA | 5c52afcfae84cae1795c70f0e121519a8d3 |
| SANs: radveo.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of radveo.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| radveo.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=(), payment=(self) |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://radveo.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://radveo.com/api/mcp | HTTPS enforced | 308 | https://radveo.com/api/mcp |
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.
check_ai_visibility ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Honesty framing: results improve odds and show what AI says today — never a guarantee of placement. |
| ok | boolean | yes | 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 | yes | 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 | yes | 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… |
No examples provided.
how_to_appear_in_ai_search ~61
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| freeCheckUrl | string | yes | Where to run the free AI-visibility check. |
| note | string | yes | Honesty framing: these steps improve odds, they never guarantee placement. |
| ok | boolean | yes | — |
| steps | array | yes | The AEO steps, in order. Empty only when the server is rate-limiting. |
No examples provided.