# AgentAvow Trust (remote · agentavow.com)

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

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `agentavow.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-agentavow-agentavow-trust/agentavow.md), [page](https://verifymcp.io/servers/com-agentavow-agentavow-trust/agentavow)
- pypi · `agentavow-trust`: 62/100, [markdown](https://verifymcp.io/servers/com-agentavow-agentavow-trust/agentavow-trust.md), [page](https://verifymcp.io/servers/com-agentavow-agentavow-trust/agentavow-trust)

## Channel facts

- Endpoint: `https://agentavow.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.6.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## 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.

### Claude

```bash
claude mcp add --transport http com-agentavow-agentavow-trust 'https://agentavow.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-agentavow-agentavow-trust": {
      "url": "https://agentavow.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-agentavow-agentavow-trust": {
      "type": "http",
      "url": "https://agentavow.com/mcp"
    }
  }
}
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-agentavow-agentavow-trust --url 'https://agentavow.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-agentavow-agentavow-trust:
    url: "https://agentavow.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-agentavow-agentavow-trust": {
      "Transport": "http",
      "Url": "https://agentavow.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-agentavow-agentavow-trust -t streamable-http -u 'https://agentavow.com/mcp'
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 75, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-18 (score 74)

First indexed and scored.

## MCP tools (8)

### `scan_repo` (~173 tokens)

Scan a GitHub repo

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.

Input parameters:

- `force` (boolean): Re-scan now instead of returning the cached verdict (results cache ~1h). Use after the target has changed.
- `owner` (string): Repo owner (optional if 'repo' is already 'owner/name').
- `repo` (string, required): Repo as 'owner/name' (e.g. 'vercel/next.js'), or just the name when 'owner' is given separately.

### `scan_package` (~180 tokens)

Scan a package

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.

Input parameters:

- `ecosystem` (string): Alias for registry.
- `force` (boolean): Re-scan now instead of returning the cached verdict (results cache ~1h). Use after a new version ships.
- `name` (string, required): Package name, e.g. 'chalk' (or 'org/model' for hf).
- `registry` (string): Package registry: npm, pypi, crates, docker, or hf.
- `surface` (string): Alias for registry.

### `scan_mcp_server` (~118 tokens)

Scan an MCP server

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.

Input parameters:

- `endpoint_url` (string, required): The MCP server's https:// URL.
- `force` (boolean): Re-scan now instead of returning the cached verdict (results cache ~1h).

### `verify_trust` (~108 tokens)

Verify an entity's trust score

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.

Input parameters:

- `entity_id` (string, required): UUID of a registered AgentAvow entity (resolve one with lookup_identity; unknown ids return guidance, not an error).
- `min_trust` (number): Min score, 0-1.

### `check_interaction_safety` (~101 tokens)

Check interaction safety

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.

Input parameters:

- `interaction_type` (string, required)
- `target_entity_id` (string, required): UUID of a registered target entity (resolve one with lookup_identity).

### `lookup_identity` (~71 tokens)

Look up an agent or tool

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.

Input parameters:

- `query` (string, required): A did:web:... or a display name.

### `get_trust_badge` (~75 tokens)

Get a trust badge

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.

Input parameters:

- `entity_id` (string, required): UUID of a registered AgentAvow entity (resolve one with lookup_identity).

### `about_agentavow` (~49 tokens)

About AgentAvow

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-agentavow-agentavow-trust/agentavow#diagnostics

## Score history

- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 74

## 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.

## Links

- Remote endpoint: https://agentavow.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-agentavow-agentavow-trust/agentavow.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-agentavow-agentavow-trust/agentavow.json
- HTML version of this page: https://verifymcp.io/servers/com-agentavow-agentavow-trust/agentavow