_ registry / mcp streamable-http · checked 2h ago

agent-evidence-api

https://agent-evidence.thx93.dev

Registry code: 06ed1375e98afeac

api record

Agent Evidence API returns web evidence for AI agents. Call research_evidence with a question or claim and the public source URLs to verify to receive structured, cited evidence with an explicit assessment. Call health to check connectivity.

endpoint
https://agent-evidence.thx93.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is agent-evidence-api live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is agent-evidence-api free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does agent-evidence-api have?
3 tools: sample, health, research_evidence.
Is agent-evidence-api safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
888ms

last good check

priced tools
1

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 5 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
2

distinct

settlements
24

last 2026-10-21

received on chain
0.107 USDC

counted from three payers (thin, concentrated)

_ what it can do 3 tools
1 paid2 open 3 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • research_evidence 0.01 USDC paid 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "question"
      ],
      "properties": {
        "mode": {
          "enum": [
            "evidence"
          ],
          "type": "string",
          "description": "Reserved input. Only \"evidence\" is supported in version 0.1.0."
        },
        "urls": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 25,
          "description": "Candidate public source URLs to retrieve and cite. Version 0.1.0 requires at least one such URL."
        },
        "language": {
          "type": "string",
          "maxLength": 35,
          "minLength": 1,
          "description": "Preferred evidence language: \"auto\" or a BCP-47 tag such as \"en\"."
        },
        "question": {
          "type": "string",
          "maxLength": 2000,
          "minLength": 1,
          "description": "The question or claim to gather web evidence for."
        },
        "max_sources": {
          "type": "integer",
          "maximum": 25,
          "description": "Cap on the number of sources processed.",
          "exclusiveMinimum": 0
        }
      },
      "additionalProperties": false
    }
    arguments 43 lines
  • sample open 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • health open 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 06ed1375e98afeac.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/06ed1375e98afeac/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/06ed1375e98afeac/badge.svg)](https://brick.blue/agent/06ed1375e98afeac?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.