_ registry / mcp + a2a streamable-http · checked 9h ago

WHP Standing

https://whp-standing-live-production.up.railway.app

Registry code: 997945e750674b33

api record

Read https://whp-standing-live-production.up.railway.app/v1/contract and fetch a fresh probe from https://whp-standing-live-production.up.railway.app/examples/submission.PROBE.json before evaluation. Acquisition is submit -> 402 -> x402 payment; no WHP-specific buyer proof is required.

endpoint
https://whp-standing-live-production.up.railway.app/mcp
door code
09edf28362918078
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 WHP Standing live?
Yes — it answered the hub's last check (checked 9h ago). It answered 96% of checks over the last 30 days.
Is WHP Standing free to use?
Yes — the hub reached it with no key and no payment.
What tools does WHP Standing have?
4 tools: whp_standing_result, whp_standing_evaluation, whp_standing_recover, whp_standing_contract.
Is WHP Standing 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
96.4%

90 days 98.6%· all time 98.4%

latency
44ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 499 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • verify provenance of signed json
  • buy a provenance evaluation
  • retrieve an evaluation result
takes → gives
data → data
tools
2 reads2 moves money
_ 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 4 tools
1 open 3 never probed 1 of 4 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.

  • whp_standing_contract reads open 35d ago

    Discover WHP Standing: Verify whether signed JSON provenance preserves identity, authority, scope, jurisdiction, time, and operation through exact COPY or identity-preserving COMPOSE. Includes exact profile, schema, authority prerequisites, fresh probe URL, and 1 USDC Base x402 payment contract.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • whp_standing_result reads unknown 35d ago

    Retrieve the exact original WHP Standing Mark or negative assessment bytes by durable purchase ID, without another charge or WHP-specific signature.

    mcp-tool

    {
      "type": "object",
      "required": [
        "purchase_id"
      ],
      "properties": {
        "purchase_id": {
          "type": "string",
          "pattern": "^[0-9a-f]{64}$"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • whp_standing_evaluation moves money unknown never probed

    Purchase one evaluation for 1 native USDC on Base mainnet (eip155:8453). Fetch a fresh submission example from /examples/submission.PROBE.json, submit it unchanged, read the x402 402 requirements, then replay with payment. Payment never guarantees a Mark.

    mcp-tool

    {
      "type": "object",
      "required": [
        "submission_raw"
      ],
      "properties": {
        "payer": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{40}$"
        },
        "submission_raw": {
          "type": "string",
          "maxLength": 262144,
          "description": "Exact UTF-8 JSON bytes. Fresh example: /examples/submission.PROBE.json"
        },
        "wallet_signature": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{128}(?:00|01|1[bBcC])$"
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • whp_standing_recover moves money unknown never probed

    Progress an already authorized pending purchase using its original durable payment. Supply only the purchase ID. Never sign another payment; if result retrieval says QUOTED, replay the original submission and identical saved wallet signature through whp_standing_evaluation.

    mcp-tool

    {
      "type": "object",
      "required": [
        "purchase_id"
      ],
      "properties": {
        "purchase_id": {
          "type": "string",
          "pattern": "^[0-9a-f]{64}$"
        }
      },
      "additionalProperties": false
    }
    arguments 13 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 997945e750674b33.

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

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.