Web Evidence is answering right now. Last checked 12 min ago. It exposes 5 tools. Last commit 12 Oct 2026.
Paid claim verification with cited web evidence, source provenance, snapshots, and hashes.
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 3 October 2026. No other catalogue keeps this.
We read the source, 6 h ago · tools taken from the live server · rules ccca72095570
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
'limits':{'radiusMeters':20000,'candidatePlaces':30,'sampledImages':MAX_SCORED_IMAGES,'inspectedImages':MAX_SCORED_IMAGES,'imagesPerBatch':max(1,min(32,int(os.getenv('PHOTO_SCOUT_SCORING_BATCH_SIZE','24')))),'parallelBatches':max(1,min(16,int(os.getenv('PHOTO_SCOUT_SC…
…if(this._events&&(n=this._events[t]))if(1===arguments.length){if(this._firingCount)for(o=0,s=n.length;o<s;o++)n[o].fn=u;delete this._events[t]}else"function"!=typeof e?console.warn("wrong listener type: "+typeof e):!1!==(e=this._listens(t,e,i))&&(i=n[e],this._firingCount&&(i.fn=u…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.
claude mcp add web-evidence --transport http https://api.aisoup.net/mcp
{
"mcpServers": {
"web-evidence": {
"url": "https://api.aisoup.net/mcp"
}
}
}
[mcp_servers.web-evidence]
url = "https://api.aisoup.net/mcp"
{
"mcpServers": {
"web-evidence": {
"url": "https://api.aisoup.net/mcp"
}
}
}
{
"mcpServers": {
"web-evidence": {
"url": "https://api.aisoup.net/mcp"
}
}
}
This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
verify_claim
verify_claim_deep
verify_claim_quick
verify_claim_research
list_verification_tiers
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://api.aisoup.net/mcp | streamable-http | answering | 456 ms | 12 min ago |
| https://api.aisoup.net/web-evidence/mcp | streamable-http | answering | 525 ms | 12 min ago |
Swiss business verification with per-check source provenance and evidence freshness.
Christian source evidence for AI agents, with provenance, tradition coverage, and citation checks.
Verified cloud storage provider facts: prices, storage, encryption. Dated and source-cited.
AI claim verification MCP endpoint with x402 payments and stealth web fetch
Verify citations in AI text: fetches each cited source, returns verdicts with evidence quotes.
Agent leases, signed receipts, watchdogs, and optional paid source-verification evidence.
Deterministic JSON checks with signed evidence and x402-paid execution
Reference verification MCP server for CSL bibliographies, evidence, and audited writes.
Answers built from our own checks of this server.