Agent Evidence API
REMOTE · AGENT-EVIDENCE.THX93.DEV
Cited web evidence and fact checking for AI agents. $0.01 per call, no API key.
Available components
Last scanned (11 hours ago)
Scores higher than 70% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Search and Retrieval
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 559 tokens (~139/item across 4 items; 4 tools + 0 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 23 Oct 26 +2
- DNSSEC: fail → pass ▲ security
- Schema quality: 436 → 559 ▼ functional
- Server version: 0.1.6 → 0.1.9 functional
- New tool “preview_evidence” functional
- 22 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 21 Oct 26 74
First indexed and scored.
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 23 Oct 2026 · Probed https://agent-evidence.thx93.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=thx93.dev | CN=YE2,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6adade33d17913a83ddf674e419b129eb98 |
| SANs: *.thx93.dev, thx93.dev | ||||||
| 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 secure
Validation of agent-evidence.thx93.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| thx93.dev. | present | 2371 | 13 | Verified |
| agent-evidence.thx93.dev. | Verified address RRset verified with the apex keys |
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=15552000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent-evidence.thx93.dev/mcp | Verified | 200 | |
| http (plaintext) | http://agent-evidence.thx93.dev/mcp | HTTPS enforced | 301 | https://agent-evidence.thx93.dev/mcp |
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 →
health Health ~52
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
preview_evidence Preview evidence (free) ~123
Free preview of the paid tool: give one question and one public URL and get back up to three cited excerpts with the source URL, retrieval time and content hash. No assessment and no verdict - that is what research_evidence adds, over up to five sources. Capped per day. Use this to judge whether the paid call is worth 0.01 USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The question or claim to gather web evidence for. |
| url | string | yes | One public source URL to retrieve and cite. The paid tool accepts up to five. |
No output schema declared.
No examples provided.
research_evidence Research Evidence ~262
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. No API key and no account: discovery is free, a call costs $0.01 in USDC on Base via x402, and nothing is charged when no source is retrieved.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
sample Sample evidence ~76
Return one real, previously produced evidence package, free, so you can see exactly what a paid call returns before spending anything: a verdict, and for every source the URL, retrieval time, content hash and the cited excerpts. Takes no arguments and always returns the same package. The paid tool is research_evidence, which answers your own question.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Agent Evidence API MCP server?
Agent Evidence API is a hosted endpoint at https://agent-evidence.thx93.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.
remote · agent-evidence.thx93.dev
claude mcp add --transport http thx93-agent-evidence-api 'https://agent-evidence.thx93.dev/mcp'
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. Cited web evidence and fact checking for AI agents. $0.01 per call, no API key. This page covers its hosted endpoint (https://agent-evidence.thx93.dev/mcp).
Is the Agent Evidence API MCP server safe to use?
Agent Evidence API scores 76 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 4 tools: research_evidence, preview_evidence, sample, health. Their descriptions and schemas cost roughly 513 tokens of context every time the server is loaded.
Does the Agent Evidence API MCP server require authentication?
No. We connected to Agent Evidence API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.