_ registry / mcp + a2a http-sse · checked 16m ago

kairostamp

https://kairostamp.com

Registry code: 6cfd9fab126058cc

api record

Kairostamp is a pay-per-call web evidence API for autonomous agents. Each endpoint fetches one public http/https URL server-side and returns a time-stamped, tamper-evident result. Payment is x402 exact USDC on Base — no accounts, no API keys. Use `list_endpoints` to see what is available, `get_payment_terms` for the payment details, and `plan_call` to get the exact request for a given endpoint and target URL. These tools return public catalog data only; the paid work happens when you make the planned HTTP request and settle the 402 challenge.

endpoint
https://kairostamp.com/mcp
door code
08d12cfdadf89ec0
protocol
http-sse ·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 kairostamp live?
Yes — it answered the hub's last check (checked 16m ago). It answered 94% of checks over the last 30 days.
Is kairostamp free to use?
Yes — the hub reached it with no key and no payment.
What tools does kairostamp have?
3 tools: get_payment_terms, plan_call, list_endpoints.
Is kairostamp 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
94.3%

90 days 94.6%· all time 99.5%

latency
1,399ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 801 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
search & web scraping & fetch
used for
  • capture time-stamped evidence of a web page
  • list web evidence endpoints
  • plan a paid evidence request
takes → gives
web pages, text → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 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.

  • list_endpoints reads open 16h ago

    List every Kairostamp web-evidence endpoint with its price, method and input/output schema, plus the buyer-oriented offers those endpoints are grouped into. Use this first to pick a tool.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_payment_terms reads unknown never probed

    Return the live x402 payment terms Kairostamp advertises: protocol version, scheme, chain, asset, price and how a client should negotiate payment.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • plan_call reads unknown 16h ago

    Given an endpoint (e.g. 'digest' or '/api/v1/snapshot') and its parameters, return the exact request to make — URL, method, curl snippet and payment terms. The caller pays via x402 when the service replies 402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "endpoint"
  ],
  "properties": {
    "url": {
      "type": "string",
      "format": "uri",
      "description": "Target public http/https URL to inspect."
    },
    "params": {
      "type": "object",
      "description": "Any additional endpoint parameters, as strings.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {
        "type": "string"
      }
    },
    "endpoint": {
      "type": "string",
      "minLength": 1,
      "description": "Endpoint slug, path or advertised name."
    }
  }
}
    arguments 29 lines
_ try it over mcp 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 6cfd9fab126058cc.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6cfd9fab126058cc/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/6cfd9fab126058cc/badge.svg)](https://brick.blue/agent/6cfd9fab126058cc?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 knowoff the mcp door
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.