Whysaid — Verify claims, sources & AI answer share MCP Server

by whysaid Your server? Claim it

answering

Whysaid — Verify claims, sources & AI answer share is answering right now. Last checked 6 min ago. It exposes 8 tools.

Verify claims and sources, and check whether AI assistants name a brand.

Uptime history 12 days of history · worst day 97%

12 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

664 ms

Response time

average over 24h

open, no key

Access

streamable-http

Whysaid — Verify claims, sources & AI answer share does not always answer

Over the last week it answered 99.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add verify --transport http https://api.whysaid.ai/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "verify": {
      "url": "https://api.whysaid.ai/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.verify]
url = "https://api.whysaid.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "verify": {
      "url": "https://api.whysaid.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "verify": {
      "url": "https://api.whysaid.ai/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

verify

verify_answer

Check an entire AI answer: open every source it cited, say which are real, which are missing or invented, and which are merely paywalled. Returns a PUBLIC receipt URL you can cite as proof. Call before storing or repeating another model's answer — an invented source that enters your state is re-reasoned over on every later run. Costs $1.00 in USDC.

verify_claim

Independently verify a claim against a real check — an HTTP fetch, a file, or a command — instead of taking an assertion on trust. Call it on the premise BEFORE committing to a multi-step plan that depends on it, and to confirm work another agent reports as done. A false premise caught here costs $0.35; caught at the end of the plan it costs the whole plan. Costs $0.35 in USDC.

verify_source

Confirm a URL is reachable and actually says what it is claimed to say, BEFORE you spend a long context reading or acting on it. Catches dead links, pages that changed, and pages that do not support the claim attached to them. One cheap call here replaces a full fetch-and-reason pass that ends in nothing. Costs $0.20 in USDC.

answer

answer_share

Ask a live AI assistant a buyer question and report whether a given brand is named, at what position, and which competitors appear instead. Use for competitive and market research that reflects what assistants say right now. Costs $0.75 in USDC.

pricing

pricing

What each Whysaid verification costs and how to pay. Free.

provenance

check_provenance

Detect whether a piece of text was model-generated and whether this system has emitted something materially identical before. Call before writing to long-term memory: model output that gets re-ingested comes back later as a trusted fact, and every downstream run that reasons over it is wasted work you will not be able to trace. Costs $0.25 in USDC.

report

report_waste

Record work your agent run spent money on and then threw away, and get back your waste rate — wasted spend as a share of total spend. Agent waste never raises an exception, so it is invisible to normal monitoring; this is the ledger for it. Report a discarded plan, a wrong target, a retry, or a call that returned nothing usable. Free.

waste

waste_report

Read the agent-integrity ledger: total spend, spend that produced nothing usable, the waste rate, and a breakdown by failure kind and by agent. Self-reported and independently detected waste are reported separately — an agent grading its own work is not evidence. Free.

Endpoints

URL	Transport	State	Latency	Checked
https://api.whysaid.ai/mcp	streamable-http	answering	853 ms	6 min ago

Alternatives to Whysaid — Verify claims, sources & AI answer share

same job, measured the same way

Statistikdata

by statistikdata

Swedish open data for Claude and other AI assistants - verified, with sources.

answering

Fidenta Verify

by noevant

Independent fact-checking for AI answers: a verdict and sources for every claim.

5 tools answering

Citation Check

by secondstageturbine

Does a cited URL exist, and does the source name what your claim names? Two answers.

2 tools answering

Audit

by beket

See how AI assistants answer about your brand

answering

Asked Thrice

by askedthrice

Measure whether AI assistants actually recommend a brand, from measured answers.

2 tools answering

Ranklogs

by ranklogs

See whether AI assistants recommend your business - and where you rank - without leaving the chat.

answering

Radveo

by radveo

Checks if AI assistants name a local business. Free shareable report, honest fixes, no guarantees.

2 tools answering

Fact Checker API

by br0ski777

Verify claims with web evidence. Returns sources and verdict. x402 micropayment.

1 tools answering

Whysaid — Verify claims, sources & AI answer share — questions

Answers built from our own checks of this server.

What can Whysaid — Verify claims, sources & AI answer share do?

It exposes 8 tools, read directly from the server on our last check. Among them: answer_share, check_provenance, pricing, report_waste, verify_answer, verify_claim and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Whysaid — Verify claims, sources & AI answer share working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 664 ms. The bar chart above shows every period we have measured.

How do I connect Whysaid — Verify claims, sources & AI answer share?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Whysaid — Verify claims, sources & AI answer share need an API key?

No. Whysaid — Verify claims, sources & AI answer share completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Whysaid — Verify claims, sources & AI answer share?

It answers our handshake in 664 ms on average, which is faster than 23% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.