# Agent Evidence API (remote · agent-evidence-api.thx93.workers.dev)

MCP-native web evidence and claim verification: cited, source-grounded evidence for AI agents.

- Trust score: 18/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-07

## Components

- remote · `agent-evidence-api.thx93.workers.dev`: 18/100 (this document), [markdown](https://verifymcp.io/servers/thx93-agent-evidence-api/agent-evidence-api-2.md), [page](https://verifymcp.io/servers/thx93-agent-evidence-api/agent-evidence-api-2)

## Channel facts

- Endpoint: `https://agent-evidence-api.thx93.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.5`

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

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 530, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 502.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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

### How do I install the Agent Evidence API MCP server?

Agent Evidence API is a hosted endpoint at https://agent-evidence-api.thx93.workers.dev/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 thx93-agent-evidence-api 'https://agent-evidence-api.thx93.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "thx93-agent-evidence-api": {
      "url": "https://agent-evidence-api.thx93.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "thx93-agent-evidence-api": {
      "type": "http",
      "url": "https://agent-evidence-api.thx93.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.thx93-agent-evidence-api]
url = "https://agent-evidence-api.thx93.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "thx93-agent-evidence-api": {
      "type": "remote",
      "url": "https://agent-evidence-api.thx93.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add thx93-agent-evidence-api --url 'https://agent-evidence-api.thx93.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  thx93-agent-evidence-api:
    url: "https://agent-evidence-api.thx93.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "thx93-agent-evidence-api": {
      "Transport": "http",
      "Url": "https://agent-evidence-api.thx93.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add thx93-agent-evidence-api -t streamable-http -u 'https://agent-evidence-api.thx93.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "thx93-agent-evidence-api": {
      "type": "http",
      "url": "https://agent-evidence-api.thx93.workers.dev/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-28 (score 18, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 18, −45)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.17 → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-09-26 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 62, +44)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.10
- [functional improvement] MCP protocol: unverified → pass
- [functional] Server version: 0.1.4 → 0.1.5

### 2026-09-23 (score 18, −43)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-22 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.1.3 → 0.1.4

### 2026-09-21 (score 61)

First indexed and scored.

## MCP tools (2)

### `research_evidence` (~225 tokens)

Fetch public web sources and return structured, cited web evidence for a question or claim. Use this for source verification, claim verification, evidence extraction, and source-grounded research, or to compare sources. Returns source URLs, retrieval timestamps, short evidence excerpts, publisher and document metadata, and an explicit supported/contradicted/mixed/inconclusive assessment. Fresh web evidence is retrieved per request unless served from a bounded cache, and each source reports its actual retrieval time. Every excerpt returned is cited evidence tied to its source URL.

Input parameters:

- `language` (string): Preferred evidence language: "auto" or a BCP-47 tag such as "en".
- `max_sources` (integer): Cap on the number of sources processed.
- `mode` (string): Reserved input. Only "evidence" is supported in version 0.1.0.
- `question` (string, required): The question or claim to gather web evidence for.
- `urls` (array): Candidate public source URLs to retrieve and cite. Version 0.1.0 requires at least one such URL.

### `health` (~52 tokens)

Check that the Agent Evidence API MCP server is reachable and report which service version is running. Free to call, takes no arguments or payment. Returns only {status, service, version} and exposes no secrets or infrastructure detail.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/thx93-agent-evidence-api/agent-evidence-api-2#diagnostics

## Score history

- 2026-10-07: 18
- 2026-10-04: 18
- 2026-10-03: 18
- 2026-10-02: 18
- 2026-10-01: 18
- 2026-09-30: 18
- 2026-09-29: 18
- 2026-09-28: 18
- 2026-09-27: 18
- 2026-09-26: 63
- 2026-09-25: 62
- 2026-09-24: 62
- 2026-09-23: 18
- 2026-09-22: 61
- 2026-09-21: 61

## Common questions

### What is the Agent Evidence API MCP server?

Agent Evidence API is an MCP server listed in the public MCP registry as io.github.Thx93/agent-evidence-api. MCP-native web evidence and claim verification: cited, source-grounded evidence for AI agents. This page covers its hosted endpoint (https://agent-evidence-api.thx93.workers.dev/mcp).

### Is the Agent Evidence API MCP server safe to use?

Agent Evidence API scores 18 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 Agent Evidence API MCP server expose?

Agent Evidence API exposes 2 tools: research_evidence, health. Their descriptions and schemas cost roughly 277 tokens of context every time the server is loaded.

### Does the Agent Evidence API MCP server require authentication?

Its publisher declares no required credentials for Agent Evidence API. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Agent Evidence API MCP server still maintained?

Agent Evidence API is still listed as active in the MCP registry. We last reached this channel on 7 October 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://agent-evidence-api.thx93.workers.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/thx93-agent-evidence-api/agent-evidence-api-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/thx93-agent-evidence-api/agent-evidence-api-2.json
- HTML version of this page: https://verifymcp.io/servers/thx93-agent-evidence-api/agent-evidence-api-2