Web Evidence
REMOTE · API.AISOUP.NET · SCANNED OCT 1
Paid claim verification with cited web evidence, source provenance, snapshots, and hashes.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 573 tokens (~114/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 18% 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 5 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
How do I install the Web Evidence MCP server?
Web Evidence is a hosted endpoint at https://api.aisoup.net/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 · api.aisoup.net
claude mcp add --transport http impanyu-web-evidence 'https://api.aisoup.net/mcp'
{
"mcpServers": {
"impanyu-web-evidence": {
"url": "https://api.aisoup.net/mcp"
}
}
} {
"servers": {
"impanyu-web-evidence": {
"type": "http",
"url": "https://api.aisoup.net/mcp"
}
}
} [mcp_servers.impanyu-web-evidence] url = "https://api.aisoup.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"impanyu-web-evidence": {
"type": "remote",
"url": "https://api.aisoup.net/mcp",
"enabled": true
}
}
} openclaw mcp add impanyu-web-evidence --url 'https://api.aisoup.net/mcp' --transport streamable-http
mcp_servers:
impanyu-web-evidence:
url: "https://api.aisoup.net/mcp" {
"McpServers": {
"impanyu-web-evidence": {
"Transport": "http",
"Url": "https://api.aisoup.net/mcp"
}
}
} assistant mcp add impanyu-web-evidence -t streamable-http -u 'https://api.aisoup.net/mcp'
{
"mcpServers": {
"impanyu-web-evidence": {
"type": "http",
"url": "https://api.aisoup.net/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 1 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Sept 26 59
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 1 Oct 2026 · Probed https://api.aisoup.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.aisoup.net | CN=YE1,O=Let's Encrypt,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 54cd7cbe735840987d7f8853df8e025561c |
| SANs: api.aisoup.net | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 api.aisoup.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| aisoup.net. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.aisoup.net/mcp | Verified | 200 | |
| http (plaintext) | http://api.aisoup.net/mcp | HTTPS enforced | 308 | https://api.aisoup.net/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 →
list_verification_tiers ~28
List Web Evidence verification tools, prices, and research limits. This tool is free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_claim ~130
Standard verification with balanced evidence coverage. Costs $0.05 USDC on Base per call.
| Name | Type | Req | Description |
|---|---|---|---|
| allowedDomains | array | – | – |
| asOf | string | – | Optional YYYY-MM-DD date at which the claim should be evaluated. |
| blockedDomains | array | – | – |
| claim | string | yes | The factual claim to verify. |
| freshnessHours | integer | – | – |
| includeConflicts | boolean | – | – |
| jurisdiction | string | – | – |
| language | string | – | – |
| maxSources | integer | – | – |
| minimumSources | integer | – | – |
| sourcePolicy | string | – | – |
No output schema declared.
No examples provided.
verify_claim_deep ~140
Deep verification for compound or contested claims using up to 15 cited sources. Costs $0.12 USDC on Base per call.
| Name | Type | Req | Description |
|---|---|---|---|
| allowedDomains | array | – | – |
| asOf | string | – | Optional YYYY-MM-DD date at which the claim should be evaluated. |
| blockedDomains | array | – | – |
| claim | string | yes | The factual claim to verify. |
| freshnessHours | integer | – | – |
| includeConflicts | boolean | – | – |
| jurisdiction | string | – | – |
| language | string | – | – |
| maxSources | integer | – | – |
| minimumSources | integer | – | – |
| sourcePolicy | string | – | – |
No output schema declared.
No examples provided.
verify_claim_quick ~139
Quick verification for a narrow claim using up to 3 cited sources. Costs $0.02 USDC on Base per call.
| Name | Type | Req | Description |
|---|---|---|---|
| allowedDomains | array | – | – |
| asOf | string | – | Optional YYYY-MM-DD date at which the claim should be evaluated. |
| blockedDomains | array | – | – |
| claim | string | yes | The factual claim to verify. |
| freshnessHours | integer | – | – |
| includeConflicts | boolean | – | – |
| jurisdiction | string | – | – |
| language | string | – | – |
| maxSources | integer | – | – |
| minimumSources | integer | – | – |
| sourcePolicy | string | – | – |
No output schema declared.
No examples provided.
verify_claim_research ~136
Research-grade verification with the largest search and evidence budget. Costs $0.25 USDC on Base per call.
| Name | Type | Req | Description |
|---|---|---|---|
| allowedDomains | array | – | – |
| asOf | string | – | Optional YYYY-MM-DD date at which the claim should be evaluated. |
| blockedDomains | array | – | – |
| claim | string | yes | The factual claim to verify. |
| freshnessHours | integer | – | – |
| includeConflicts | boolean | – | – |
| jurisdiction | string | – | – |
| language | string | – | – |
| maxSources | integer | – | – |
| minimumSources | integer | – | – |
| sourcePolicy | string | – | – |
No output schema declared.
No examples provided.
What is the Web Evidence MCP server?
Web Evidence is an MCP server listed in the public MCP registry as io.github.impanyu/web-evidence. Paid claim verification with cited web evidence, source provenance, snapshots, and hashes. This page covers its hosted endpoint (https://api.aisoup.net/mcp).
Is the Web Evidence MCP server safe to use?
Web Evidence scores 59 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 Web Evidence MCP server expose?
Web Evidence exposes 5 tools: list_verification_tiers, verify_claim_quick, verify_claim, verify_claim_deep, verify_claim_research. Their descriptions and schemas cost roughly 573 tokens of context every time the server is loaded.
Does the Web Evidence MCP server require authentication?
No. We connected to Web Evidence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Web Evidence MCP server still maintained?
Web Evidence is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.