Cavyro: MCP server, CLI and agent surfaces
Not counted. The endpoint listed for Cavyro at ai.cavyro.com asks for credentials and publishes no OAuth metadata, so it looks like any other protected API. Checked on 4 November 2026. A credential prompt without OAuth metadata is what any protected web API returns.
Fact sheet
| Company | Cavyro |
|---|---|
| Domain | cavyro.com |
| Category | CRM (assigned by this directory from the registry description) |
| MCP server | Credential wall |
| Ora score | 73, grade B; Ora scanned the domain on 8 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for cavyro.com, a vendor-published score) |
| Company found through | the GitHub MCP Registry; the official MCP Registry |
| Last verified | 4 November 2026 |
MCP server
| Endpoint | https://ai.cavyro.com/mcp |
|---|---|
| How it was found | listed in the GitHub MCP Registry; the official MCP Registry |
| Transport | streamable-http |
| HTTP status | 401 |
| Connected | 4 November 2026, 20:02 UTC |
| Handshake time | 617 ms over 1 attempt |
The endpoint asked for credentials without publishing OAuth metadata. It is not counted as an MCP server, because the same answer is what any protected API gives.
Connector log
2 connections on 4 November 2026, read-only methods only
- 19:56:50Z https://ai.cavyro.com/mcp sent initialize result auth-required-no-oauth (HTTP 401) 675 ms
- 20:02:21Z https://ai.cavyro.com/mcp sent initialize result auth-required-no-oauth (HTTP 401) 617 ms
Authentication
| Auth type | API key |
|---|---|
| What the challenge said | Bearer realm="cavyro" |
The sign-in route, step by step
- Request
https://ai.cavyro.com/mcpwithout a token. It answers with a credential challenge but no OAuth metadata. - Create a key or token in the company's own settings; the metadata gives an agent no way to do that itself.
- Send the key in the header the vendor documents and retry. The connector sends no key.
See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.
CLI
No CLI is on record for Cavyro. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.
Other agent surfaces
| Surface | Result |
|---|---|
| OpenAPI file | Found: cavyro.com (JSON, via a direct request). |
| WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. |
| MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. |
| A2A agent card | Not checked: the domain is not in the shared crawl for this edition. |
| A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. |
| agents.json | Not checked: the domain is not in the shared crawl for this edition. |
| OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. |
| NLWeb endpoint | Not checked in this edition. |
Registry listings
| Registry | Listed |
|---|---|
| Official MCP Registry | Yes: com.cavyro/cavyro |
| GitHub MCP Registry | Yes |
| awesome-remote-mcp-servers | No |
| Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. |
| Glama | Not checked: Glama's API needs a key and attribution terms. |