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

costheta

https://costheta.dev

Registry code: fef4dd8da7a498d3

api record

Verifiable physical randomness from cosmic-ray detections. Free beacon, paid signed decisions.

from a public catalogue that lists it, not from the operator

endpoint
https://costheta.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 costheta live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is costheta free to use?
Not measured yet.
What tools does costheta have?
3 tools: costheta_random, costheta_decide, costheta_witness.
Is costheta 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
99%

90 days 99.1%· all time 99.1%

latency
146ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 329 checks · signed record
  • degraded → live
  • live → degraded· HTTP 530
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • get a verifiable random outcome
  • make a signed commit-and-reveal decision
  • witness a commitment against a random pulse
takes → gives
data → data
tools
1 reads2 changes data
_ 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
3 never probed 0 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.

  • costheta_random reads unknown never probed

    Free public random outcome anchored to the latest signed cosmic-ray coincidence pulse. This is a shared beacon: every caller sees the same latest signed pulse until the next muon arrives. For private commitments and retry-safe paid certificates, use costheta_decide.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "n_options": {
          "type": "integer",
          "default": 2,
          "maximum": 1000000,
          "minimum": 2,
          "description": "Number of equally indexed outcomes. Result is in [0, n_options)."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • costheta_decide changes data unknown never probed

    Paid x402 Base mainnet tool: commit-and-reveal decision with a signed certificate. Requires PAYMENT-SIGNATURE and idempotency_key.

    mcp-tool

    {
      "type": "object",
      "required": [
        "commitment",
        "idempotency_key",
        "n_options"
      ],
      "properties": {
        "n_options": {
          "type": "integer",
          "default": 2,
          "maximum": 1000000,
          "minimum": 2
        },
        "commitment": {
          "type": "string",
          "description": "Caller commitment, usually sha256:<hex>."
        },
        "idempotency_key": {
          "type": "string",
          "description": "Stable retry key. Same key + commitment returns the same paid result."
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • costheta_witness changes data unknown never probed

    Paid x402 Base mainnet tool: witness a caller commitment against a signed pulse certificate. Requires PAYMENT-SIGNATURE and idempotency_key.

    mcp-tool

    {
      "type": "object",
      "required": [
        "commitment",
        "idempotency_key"
      ],
      "properties": {
        "commitment": {
          "type": "string",
          "description": "Caller commitment, usually sha256:<hex>."
        },
        "idempotency_key": {
          "type": "string",
          "description": "Stable retry key. Same key + commitment returns the same paid result."
        }
      },
      "additionalProperties": false
    }
    arguments 18 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 fef4dd8da7a498d3.

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