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

AgentAvow Trust

REMOTE · AGENTAVOW.COM · 2 COMPONENTS · SCANNED SEP 20

Signed, offline-verifiable safety scores for the MCP servers, packages & tools an agent connects to

75 Trust /100
Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1176 tokens (~130/item across 9 items; 8 tools + 1 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 Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% 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 8 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Install

How do I install the AgentAvow Trust MCP server?

AgentAvow Trust is a hosted endpoint at https://agentavow.com/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 · agentavow.com

# add to Claude Code
claude mcp add --transport http com-agentavow-agentavow-trust 'https://agentavow.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-agentavow-agentavow-trust": {
      "url": "https://agentavow.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-agentavow-agentavow-trust": {
      "type": "http",
      "url": "https://agentavow.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-agentavow-agentavow-trust]
url = "https://agentavow.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-agentavow-agentavow-trust": {
      "type": "remote",
      "url": "https://agentavow.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-agentavow-agentavow-trust --url 'https://agentavow.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-agentavow-agentavow-trust:
    url: "https://agentavow.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-agentavow-agentavow-trust": {
      "Transport": "http",
      "Url": "https://agentavow.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-agentavow-agentavow-trust -t streamable-http -u 'https://agentavow.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-agentavow-agentavow-trust": {
      "type": "http",
      "url": "https://agentavow.com/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.

  • 19 Sept 26 +1
    • Stability: unverified → 0.03 functional
  • 18 Sept 26 74

    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 20 Sept 2026 · Probed https://agentavow.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agentavow.com CN=YE2,O=Let's Encrypt,C=US 6 Aug 2026 4 Nov 2026 ECDSA 256 ECDSA-SHA384 50dcfd09464d0a1d723315023d6d642efac
SANs: agentavow.com, www.agentavow.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agentavow.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
agentavow.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
content-security-policy default-src 'self'; script-src 'self' https://cdn.jsdelivr.net https://accounts.google.com https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net https://accounts.google.com; img-src 'self' data: blob: https:; font-src 'self' https://cdn.jsdelivr.net; connect-src 'self' wss://agentavow.com https://accounts.google.com https://cloudflareinsights.com; frame-src https://accounts.google.com; frame-ancestors 'none'; form-action 'self'; base-uri 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), camera=(), microphone=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agentavow.com/mcp Verified 200
http (plaintext) http://agentavow.com/mcp HTTPS enforced 301 https://agentavow.com/mcp
MCP tools · 8 exposed · ~875 tokens

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 →

Tool Tokens
about_agentavow ~49

What AgentAvow is, which tool to use for what, how to read a verdict, and example scans. Call this for an overview or when getting started. No input, read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

check_interaction_safety ~101

Check whether it is safe to interact with another agent by trust threshold. Thresholds: delegate 0.6, trade 0.5, collaborate 0.4, follow 0.1. Returns is_safe, risk_level, the score, and a recommendation. Read-only, no auth.

NameTypeReqDescription
interaction_typestringyes
target_entity_idstringyesUUID of a registered target entity (resolve one with lookup_identity).

No output schema declared.

No examples provided.

get_trust_badge ~75

Get an embeddable AgentAvow trust badge (SVG) for an entity, with ready-to-paste Markdown and HTML. The badge auto-updates as the score changes. Read-only, no auth.

NameTypeReqDescription
entity_idstringyesUUID of a registered AgentAvow entity (resolve one with lookup_identity).

No output schema declared.

No examples provided.

lookup_identity ~71

Look up an AgentAvow entity by W3C DID or display name. Returns the entity's id, name, type, trust score and tier. Read-only, no auth. Use to resolve an identity before checking its trust.

NameTypeReqDescription
querystringyesA did:web:... or a display name.

No output schema declared.

No examples provided.

scan_mcp_server ~118

Scan a live MCP server's tool definitions for tool-poisoning, prompt-injection, invisible-unicode, and manifest-execution risks before your agent connects to it. Returns a 0-100 trust score, a safe / needs-review verdict, findings, and a signed attestation. Read-only; calls the agentavow.com public API.

NameTypeReqDescription
endpoint_urlstringyesThe MCP server's https:// URL.
forcebooleanRe-scan now instead of returning the cached verdict (results cache ~1h).

No output schema declared.

No examples provided.

scan_package ~180

Scan a published package (npm, PyPI, crates, Docker, or Hugging Face) with AgentAvow. Returns a 0-100 trust score, a safe / needs-review verdict, findings with remediation, and a signed attestation. Also reports repo-vs-artifact drift (files shipped that aren't in the source). Read-only; calls agentavow.com.

NameTypeReqDescription
ecosystemstringAlias for registry.
forcebooleanRe-scan now instead of returning the cached verdict (results cache ~1h). Use after a new version ships.
namestringyesPackage name, e.g. 'chalk' (or 'org/model' for hf).
registrystringPackage registry: npm, pypi, crates, docker, or hf.
surfacestringAlias for registry.

No output schema declared.

No examples provided.

scan_repo ~173

Scan a public GitHub repository with AgentAvow and return whether it is safe for an agent to connect to: a 0-100 trust score, a plain safe / needs-review verdict, the findings behind it (with where and how to fix), and a signed, offline-verifiable attestation. Read-only, no account. Calls the AgentAvow public API at agentavow.com.

NameTypeReqDescription
forcebooleanRe-scan now instead of returning the cached verdict (results cache ~1h). Use after the target has changed.
ownerstringRepo owner (optional if 'repo' is already 'owner/name').
repostringyesRepo as 'owner/name' (e.g. 'vercel/next.js'), or just the name when 'owner' is given separately.

No output schema declared.

No examples provided.

verify_trust ~108

Verify an AgentAvow entity's trust score. Returns trust_score (0-1), trust_score_pct (0-100), trust_tier, and whether it meets a minimum threshold. Read-only, no auth. Use before interacting with an unknown agent.

NameTypeReqDescription
entity_idstringyesUUID of a registered AgentAvow entity (resolve one with lookup_identity; unknown ids return guidance, not an error).
min_trustnumberMin score, 0-1.

No output schema declared.

No examples provided.

Common questions

What is the AgentAvow Trust MCP server?

AgentAvow Trust is an MCP server listed in the public MCP registry as com.agentavow/agentavow-trust. Signed, offline-verifiable safety scores for the MCP servers, packages & tools an agent connects to. This page covers its hosted endpoint (https://agentavow.com/mcp).

Is the AgentAvow Trust MCP server safe to use?

AgentAvow Trust scores 75 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 AgentAvow Trust MCP server expose?

AgentAvow Trust exposes 8 tools: scan_repo, scan_package, scan_mcp_server, verify_trust, check_interaction_safety, and 3 more. Their descriptions and schemas cost roughly 875 tokens of context every time the server is loaded.

Does the AgentAvow Trust MCP server require authentication?

No. We connected to AgentAvow Trust without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AgentAvow Trust MCP server still maintained?

AgentAvow Trust 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.