co.cuvo/website
REMOTE · CUVO.CO · 2 COMPONENTS · SCANNED SEP 20
Cuvo Health published site content and live discovery-call booking tools for AI agents.
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 → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 638 tokens (~70/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the co.cuvo/website MCP server?
co.cuvo/website is a hosted endpoint at https://cuvo.co/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.
remote · cuvo.co
claude mcp add --transport http co-cuvo-website 'https://cuvo.co/mcp'
{
"mcpServers": {
"co-cuvo-website": {
"url": "https://cuvo.co/mcp"
}
}
} {
"servers": {
"co-cuvo-website": {
"type": "http",
"url": "https://cuvo.co/mcp"
}
}
} [mcp_servers.co-cuvo-website] url = "https://cuvo.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-cuvo-website": {
"type": "remote",
"url": "https://cuvo.co/mcp",
"enabled": true
}
}
} openclaw mcp add co-cuvo-website --url 'https://cuvo.co/mcp' --transport streamable-http
mcp_servers:
co-cuvo-website:
url: "https://cuvo.co/mcp" {
"McpServers": {
"co-cuvo-website": {
"Transport": "http",
"Url": "https://cuvo.co/mcp"
}
}
} assistant mcp add co-cuvo-website -t streamable-http -u 'https://cuvo.co/mcp'
{
"mcpServers": {
"co-cuvo-website": {
"type": "http",
"url": "https://cuvo.co/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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://cuvo.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cuvo.co | CN=WE1,O=Google Trust Services,C=US | 13 Aug 2026 | 11 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 1c75ee95b0faabe2136ba43f35e05d11 |
| SANs: cuvo.co, *.cuvo.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of cuvo.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| cuvo.co. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cuvo.co/mcp | Verified | 200 | |
| http (plaintext) | http://cuvo.co/mcp | HTTPS enforced | 301 | https://cuvo.co/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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
book_discovery_call Book a discovery call ~133
Book a real 30-minute Cuvo discovery call for the user. Requires their explicit confirmation of a specific slot from get_availability plus their real full name and email; the calendar invite goes to that email. Do not book without the user's consent.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | User's email (receives the invite) | |
| name | string | yes | User's full name |
| phone | string | – | Optional phone number |
| slot_start_iso | string | yes | startIso of the chosen slot, exactly as returned by get_availability |
| timezone | string | yes | IANA timezone used when fetching availability |
No output schema declared.
No examples provided.
get_article Read one blog article ~47
Full text (markdown) of one published article, by slug from list_articles.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Article slug, e.g. "dea-telemedicine-flexibilities-2026" |
No output schema declared.
No examples provided.
get_availability Check discovery-call availability ~74
Next open 30-minute discovery-call slots on the Cuvo team's calendar, in the user's timezone. Call before offering any times; returns each slot's startIso and human label.
| Name | Type | Req | Description |
|---|---|---|---|
| timezone | string | – | IANA timezone of the user, e.g. "America/New_York". Defaults to America/New_York. |
No output schema declared.
No examples provided.
get_comparison Read one comparison page ~53
Full text (markdown) of one Cuvo-vs-competitor comparison page, by slug from list_comparisons.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Comparison slug, e.g. "cuvo-vs-wheel" |
No output schema declared.
No examples provided.
get_overview Cuvo overview and FAQ ~40
What Cuvo Health is, who it is for, and the canonical FAQ: the white label telehealth platform that operates the licensed clinic behind consumer brands.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pricing Published pricing ~45
Cuvo's published pricing as markdown: plan tiers with setup fees, the flat $25 per-consult fee, 0% medication markup, commercial terms, and add-ons.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_articles List blog articles ~38
List every published article on the Cuvo blog (slug, title, excerpt, date, category): telehealth compliance, pharmacy, and growth guides.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_comparisons List comparison pages ~35
List every Cuvo-vs-competitor comparison page (slug, competitor name, one-line summary, facts-reviewed date).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_callback Request a phone callback ~56
Ask the Cuvo team to phone the user back, when live booking is unavailable or the user prefers a callback. Requires the user's consent, name, and phone number.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| phone | string | yes | – |
No output schema declared.
No examples provided.
What is the co.cuvo/website MCP server?
co.cuvo/website is an MCP server listed in the public MCP registry as co.cuvo/website. Cuvo Health published site content and live discovery-call booking tools for AI agents. This page covers its hosted endpoint (https://cuvo.co/mcp).
Is the co.cuvo/website MCP server safe to use?
co.cuvo/website scores 86 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 co.cuvo/website MCP server expose?
co.cuvo/website exposes 9 tools: get_overview, get_pricing, list_comparisons, get_comparison, list_articles, and 4 more. Their descriptions and schemas cost roughly 521 tokens of context every time the server is loaded.
Does the co.cuvo/website MCP server require authentication?
No. We connected to co.cuvo/website without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the co.cuvo/website MCP server still maintained?
co.cuvo/website is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.