_ registry / mcp + a2a JSONRPC · checked 1h ago

wetter-ensemble

https://ensemble.netzhandwerker.de

Registry code: 3b6bb6d9f7031969

api record

The warnings the Deutscher Wetterdienst has actually issued for the warn cell containing the coordinate, in German and English, with severity, urgency, certainty and an explicit effective/onset/expires window plus whether the warning is active right now.

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

endpoint
https://wetter.halowerk.com/
door code
54a319bd86824e01
protocol
JSONRPC ·0.3
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 wetter-ensemble live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is wetter-ensemble free to use?
Not measured yet.
What tools does wetter-ensemble have?
2 tools: weather ensemble, weather warnings.
Is wetter-ensemble 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.8%

90 days 99.2%· all time 99.4%

latency
119ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1193 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • degraded → live
_ what it is for
topic
weather & environment forecast
used for
  • compare weather model forecasts for a location
  • get official german severe weather warnings
takes → gives
data → data
tools
2 reads
_ 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 also stands behind 120 other origins: the chain figures are the gateway's, not this listing's alone. 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
43

distinct

settlements
11,875

last 2026-11-05

received on chain
46.0086 USDC

shared-payto

inferred, not observed

Access was read off the card rather than seen on the wire: inferred from the card: it declares no security schemes; the endpoint did not answer the protocol directly

_ what it can do 2 tools
2 never probed 0 of 2 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.

  • weather_ensemble reads unknown never probed

    Compare every major weather model hour by hour and return spread, model agreement and ensemble rain probability instead of one model opinion.

    weather-ensemblemodel-agreementforecast-spreadmulti-modelrain-probabilityfrost-warningdwd-warningsagent-toolsenergy-forecastinglogisticsagriculture

  • weather_warnings reads unknown never probed

    Official DWD severe weather warnings in force for one point in Germany, each with its validity window.

    weather-ensemblemodel-agreementforecast-spreadmulti-modelrain-probabilityfrost-warningdwd-warningsagent-toolsenergy-forecastinglogisticsagriculture

_ try it over a2a 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 3b6bb6d9f7031969.

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

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.

_ also on netzhandwerker.de 8 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.