Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Avo

REMOTE · MCP.AVO.APP · SCANNED AUG 3

Define, ship & query your analytics tracking from one source of truth, trusted by humans and agents.

Available components

remote · mcp.avo.app 31
+11 this week 31 Trust /100
Trust breakdown (6 categories)

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 Security78
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 5 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

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 · mcp.avo.app

# add to Claude Code
claude mcp add --transport http avohq-avo https://mcp.avo.app/mcp
# ~/.codex/config.toml
[mcp_servers.avohq-avo]
url = "https://mcp.avo.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "avohq-avo": {
      "type": "remote",
      "url": "https://mcp.avo.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add avohq-avo --url https://mcp.avo.app/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  avohq-avo:
    url: "https://mcp.avo.app/mcp"
// mcp.json
{
  "mcpServers": {
    "avohq-avo": {
      "type": "http",
      "url": "https://mcp.avo.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 31 Jul 26 +11
    • 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 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 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 20

    First indexed and scored.

Diagnostics

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://mcp.avo.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.avo.app CN=WR3,O=Google Trust Services,C=US 11 Jul 2026 9 Oct 2026 RSA 2048 SHA256-RSA e1a86e0e504527e00943380f80565a5a
SANs: mcp.avo.app
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d
DNSSEC insecure

Validation of mcp.avo.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
avo.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer resource_metadata="https://mcp.avo.app/.well-known/oauth-protected-resource", scope="read write" 

Bearer resource_metadata="https://mcp.avo.app/.well-known/oauth-protected-resource", scope="read write"
Header Value
www-authenticate Bearer resource_metadata="https://mcp.avo.app/.well-known/oauth-protected-resource", scope="read write"

Protected resource metadata

Document https://mcp.avo.app/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.avo.app/mcp
Authorisation server https://api.avo.app
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.avo.app/mcp Auth required 401
http (plaintext) http://mcp.avo.app/mcp Inconclusive 401
MCP tools

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.

No tool schema has been captured from this endpoint yet.