_ registry / mcp http-sse · checked 3h ago

SpotWave.Api

https://spotwave.eu

Registry code: a91a2948ceb0896c

api record

Live day-ahead electricity prices for 40+ European markets, all-in with taxes and VAT.

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

endpoint
https://spotwave.eu/api/mcp
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 SpotWave.Api live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is SpotWave.Api free to use?
Yes — the hub reached it with no key and no payment.
What tools does SpotWave.Api have?
4 tools: get_prices, get_current_price, compare_markets, list_markets.
Is SpotWave.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
199ms

last good check

priced tools
0

of 4 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. 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
2 open 2 never probed 2 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.

  • compare_markets open 3h ago

    Compares the current electricity price across every covered European market, sorted cheapest first by all-in price. All figures are EUR per kWh so markets are directly comparable. The snapshot is refreshed at most hourly (see asOfUtc) and uses the current hour's average price. All-in = variable household price per kWh: spot + energy tax + per-kWh grid fee + VAT. Fixed monthly charges (grid capacity, tax credits) are excluded. Spot = wholesale day-ahead price.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • list_markets open 3h ago

    Lists every European electricity market (bidding zone) SpotWave covers, with its code, display name and billing currency. Use the code (e.g. "NL", "DE", "SE3", "NO1", "DK1", "ITN") as the `market` argument of the other tools. Countries split into several zones (Sweden, Norway, Denmark, Italy) have one code per zone.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_prices unknown never probed

    Gets one day's electricity prices for a market as hourly averages (normally 24 rows; 23 or 25 on daylight-saving change days), with the day's min, max and average and the cheapest/most expensive hour. Days are day-ahead delivery days in Central European time (Europe/Amsterdam, CET/CEST); hour starts are given in that local time. Prices are per kWh in the market's own currency. Tomorrow's prices are published around 13:00 CET each day; before that, asking for "tomorrow" returns a not-yet-published message. All-in = variable household price per kWh: spot + energy tax + per-kWh grid fee + VAT. Fixed monthly charges (grid capacity, tax credits) are excluded. Spot = wholesale day-ahead price.

    mcp-tool

    {
      "type": "object",
      "required": [
        "market",
        "day"
      ],
      "properties": {
        "day": {
          "type": "string",
          "description": "\"today\", \"tomorrow\", or a date as YYYY-MM-DD (any day from 2021-01-01 up to tomorrow)."
        },
        "market": {
          "type": "string",
          "description": "Market code from list_markets, e.g. \"NL\", \"DE\" or \"SE3\"."
        }
      }
    }
    arguments 17 lines
  • get_current_price unknown 3h ago

    Gets the electricity price for the current delivery period (15- or 60-minute slot) in one market: the all-in household price and the wholesale spot price, per kWh, in the market's own currency and in EUR. All-in = variable household price per kWh: spot + energy tax + per-kWh grid fee + VAT. Fixed monthly charges (grid capacity, tax credits) are excluded. Spot = wholesale day-ahead price.

    mcp-tool

    {
      "type": "object",
      "required": [
        "market"
      ],
      "properties": {
        "market": {
          "type": "string",
          "description": "Market code from list_markets, e.g. \"NL\", \"DE\" or \"SE3\"."
        }
      }
    }
    arguments 12 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 a91a2948ceb0896c.

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