Security & Testing

whysaid.ai

Provides tools to verify sources, claims, and AI-generated content through live checks and provenance analysis.

1 endpoint8 known toolsFirst detected August 21, 2026Last detected August 21, 2026

ENDPOINT 1

https://api.whysaid.ai/mcp

No auth detected

MCP server metadata

Name: whysaid
Version: 1.0.0

Capabilities

tools

Server instructions

Whysaid verifies claims, sources, and AI answer share. Paid tools cost USDC on Base via x402: send an X-PAYMENT header with your request. Call `pricing` (free) for current prices.

Known tools 8

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.

Inferred read-only

check_provenance

Detect whether a piece of text was model-generated and whether this system has emitted something materially identical before.

Inferred read-only

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.

Potential side effects

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.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

pricing

What each Whysaid verification costs and how to pay.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

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

Claude Code

.mcp.json

{
  "mcpServers": {
    "whysaid": {
      "type": "http",
      "url": "https://api.whysaid.ai/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: whysaid
Remote MCP URL: https://api.whysaid.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "whysaid": {
      "type": "http",
      "url": "https://api.whysaid.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "whysaid",
  "transport": "streamable-http",
  "url": "https://api.whysaid.ai/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for whysaid.ai was fetched 2026-08-24T06:00:37.596Z.

Trust status Neutral

whysaid.ai is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.