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

MCP Energy Data

https://entsoemcp.com

Registry code: 7b9c1bacb41710bf

api record

ENTSO-E European power-market data: prices, load, generation, cross-border flows, outages. Hot-path is DuckDB-over-Parquet — queries are sub-second over the cached ingest. Use `data_coverage` before assuming a recent date is landed.

DATE CONVENTION (read before every series query):

endpoint
https://entsoemcp.com/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 MCP Energy Data live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is MCP Energy Data free to use?
Yes — the hub reached it with no key and no payment.
What tools does MCP Energy Data have?
14 tools: get_generation, get_derivation, get_load, get_tb_spread, compare_zones, get_day_ahead_prices, get_crossborder_flow, get_outages, ….
Is MCP Energy Data 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.5%

90 days 99.5%· all time 99.5%

latency
200ms

last good check

priced tools
0

of 14 tools

_ answered our checks, 90 days 614 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
topic
energy & utilities electricity & power markets
used for
  • get european day-ahead power prices
  • get electricity load and generation
  • check cross-border power flows
  • compute battery arbitrage spreads
takes → gives
text → data
tools
14 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 14 tools
5 open 9 never probed 5 of 14 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.

  • data_coverage reads open 11h ago

    Show ingest coverage and lag for (endpoint × zone) — call before queries if you're not sure whether the data is landed yet.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "zone": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "endpoint": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    }
  },
  "additionalProperties": false
}
    arguments 28 lines
  • list_derivations reads open 11h ago

    List computed-metric derivations available via get_derivation(). Each derivation is a metric computed on-the-fly from one or more landed endpoints (Tier-2 Parquet). Today: capture_price (monthly VWAP capture price + baseload + capture rate per technology; "capture rate" is the industry-standard name for what the JSON response calls `quality_factor`), negative_price_hours, residual_load, res_share, emissions (monthly CO2 emissions per fuel using IPCC AR5 lifecycle factors, production-based), and tb_spread (monthly or annual Top-Bottom battery-arbitrage spread TB1/TB2/TB4/TB6 per zone on SDAC market days; accepts zone='all' for every zone in one call).

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list_zones reads open 11h ago

    List registered ENTSO-E bidding zones.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "cluster": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "active_only": {
      "type": "boolean",
      "default": true
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • list_endpoints reads open 3d ago

    List supported ENTSO-E endpoint families.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "family": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • list_psr_types reads open 3h ago

    List production-type (psr_type) codes. Pass zone= to scope the answer. Most codes are ENTSO-E's B01..B25 and mean the same thing in every ENTSO-E zone. A few are source-native (source != "entsoe") and exist only where that source publishes — they express concepts the B-codes cannot, so they are NOT interchangeable with a similar-looking B-code. Check `source` and read `description` before comparing a code across zones. Passing zone= also returns `taxonomy_note` for zones that mix taxonomies (e.g. GB), and per-code `endpoints` showing where each code comes from. Each code carries `counts_as_generation`: when False the figure is a net flow or net storage number, not production — do not sum it into a generation total.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "zone": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • get_generation reads unknown 46h ago

    Aggregated generation (MW) per production type. `start`/`end` default to UTC; `start` inclusive, `end` EXCLUSIVE. For a full calendar month set `end` to the first day of the next month. Pass `tz="local"` or an IANA name to interpret start/end as wall-clock in that timezone. GB/UK: ENTSO-E's GB generation ended 2021-06-15. For later windows use `get_series(endpoint="generation_mix", zone="GB", …)` (NESO, 2009→now, its own wind codes — `list_psr_types(zone="GB")` first); a window past a series' end answers with `series_ended`, naming that endpoint. If you're computing a **generation-weighted** price metric — capture price, capture rate, value factor, merchant-PPA achieved price — use `get_derivation(slug="capture_price", …)` instead. It runs server-side over the full window and returns monthly rows; no row cap, no pagination.

    mcp-tool

    {
  "type": "object",
  "required": [
    "zone",
    "start",
    "end"
  ],
  "properties": {
    "tz": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "end": {
      "type": "string"
    },
    "zone": {
      "type": "string"
    },
    "start": {
      "type": "string"
    },
    "psr_types": {
      "anyOf": [
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "aggregation": {
      "type": "string",
      "default": "raw"
    }
  },
  "additionalProperties": false
}
    arguments 49 lines
  • get_derivation reads unknown 46h ago

    Compute **capture price**, **capture rate** (a.k.a. value factor / quality factor / Marktwertfaktor), **TBx battery-arbitrage spreads**, and other generation-weighted market metrics server-side from landed Parquet. Use this instead of fetching hourly prices + hourly generation yourself and weighting them client-side — server-side aggregation has no row cap and no pagination. `slug`: a key from list_derivations() — today: `"capture_price"`, `"negative_price_hours"`, `"residual_load"`, `"res_share"`, `"emissions"`, `"tb_spread"`. `tb_spread` returns monthly (default) or annual (aggregation='annual') Top-Bottom spreads TB1/TB2/TB4/TB6 in <currency>/MW per period — the sum of daily (top-x minus bottom-x hourly prices) over SDAC market days. The only slug accepting `aggregation`, and the only one accepting multi-zone `zone` ('all', a list, or CSV). Example — annual TB2 across every European market in ONE call: get_derivation("tb_spread", "2025-01-01", "2026-01-01", zone="all", aggregation="annual") For a single day's top/bottom hour TIMESTAMPS use get_tb_spread. `capture_price` returns monthly rows per (zone, psr_type, currency) with columns: currency, capture_price_eur_per_mwh, baseload_price_eur_per_mwh, quality_factor (the capture rate = capture/baseload), total_gen_mwh, n_hours. Months are bucketed by local time using the zone's IANA timezone. ENDED INPUTS: when an input series stopped upstream before the window's end, the answer carries `series_ended` (per zone for a multi-zone tb_spread): which inputs, why, what carries each on, and any metric that carries this one on. GB: ENTSO-E's day-ahead price ended 2020-12-31, so GB capture_price, negative_price_hours and tb_spread stop there; `capture_price_mid` covers GB 2016-09 → now against the Market Index Price (a traded index, not the auction — read its note). CURRENCY (capture_price and tb_spread alike): the `*_eur_per_mwh` / `tb*_eur_per_mw` key names are FIXED for API stability and do NOT track the actual unit — read the row's `currency` column, which is authoritative (EUR for euro zones, GBP for GB, PLN/RON/BGN for the PL/RO/BG local-currency eras). The response echoes it top-level as `currency`; a window spanning two currencies instead sets `unit` to null with `mixed_currency: true` and a `currencies` list. A month (or period) spanning a redenomination splits into one row PER CURRENCY, each computed only from that currency's hours — so never average or sum a price column across rows with different `currency` values. Summing `total_gen_mwh` across them IS correct: the split rows partition the month's hours rather than duplicating them. `quality_factor` is a ratio and stays comparable across currencies. `emissions` returns monthly rows per (zone, psr_type) with columns: generation_mwh, n_hours, emission_factor_kg_per_mwh, emissions_t_co2. Production-based; IPCC AR5 lifecycle factors. Zero-emission rows (nuclear, wind, solar, hydro, geothermal, marine) appear with emissions_t_co2 = 0 — useful for stacked charts. Filter via `psr_types=["solar","wind_onshore","wind_offshore"]` (or raw B-codes like "B16") to get only the technologies you care about. Defaults to all psr_types that have generation data. Example — Spain solar capture price, last 12 months: get_derivation("capture_price", "2025-05-01", "2026-05-01", zone="ES", psr_types=["B16"], tz="Europe/Madrid") Example — Germany 2024 emissions by fuel: get_derivation("emissions", "2024-01-01", "2025-01-01", zone="DE_LU", tz="Europe/Berlin") Returns 12 monthly rows in one call; no pagination.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug",
    "start",
    "end"
  ],
  "properties": {
    "tz": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": "local"
    },
    "end": {
      "type": "string"
    },
    "slug": {
      "type": "string"
    },
    "zone": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "start": {
      "type": "string"
    },
    "to_zone": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "from_zone": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "psr_types": {
      "anyOf": [
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "aggregation": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    }
  },
  "additionalProperties": false
}
    arguments 95 lines
  • get_load reads unknown 46h ago

    Actual or forecast load (MW). kind = actual | forecast | both. `start`/`end` default to UTC; `start` inclusive, `end` EXCLUSIVE. For a full calendar month set `end` to the first day of the next month. Pass `tz="local"` or an IANA name to interpret start/end as wall-clock in that timezone.

    mcp-tool

    {
  "type": "object",
  "required": [
    "zone",
    "kind",
    "start",
    "end"
  ],
  "properties": {
    "tz": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "end": {
      "type": "string"
    },
    "kind": {
      "type": "string"
    },
    "zone": {
      "type": "string"
    },
    "start": {
      "type": "string"
    },
    "aggregation": {
      "type": "string",
      "default": "raw"
    }
  },
  "additionalProperties": false
}
    arguments 39 lines
  • get_tb_spread reads unknown 1h ago

    Top-Bottom (TBx) spread — daily battery-arbitrage benchmark. TBx = sum(top X priced hours) − sum(bottom X priced hours) over the day-ahead clearing prices for `zone` on `date`. The day is the SDAC market day (23/25 hours on DST-transition days). `date` must be a bare YYYY-MM-DD — time-bearing strings are rejected. Returns both `spread` (<currency>/MW/day) and `mean_spread` (<currency>/MWh = spread/X) in the zone's trading currency — see the response `currency`/`unit` (EUR for euro zones; GB=GBP). Common X: 1, 2, 4. A day past the zone's day-ahead series end (GB after 2020-12-31) answers with `series_ended`, naming the endpoint that carries the prices on.

    mcp-tool

    {
  "type": "object",
  "required": [
    "zone",
    "date"
  ],
  "properties": {
    "x": {
      "type": "integer",
      "default": 2
    },
    "date": {
      "type": "string"
    },
    "zone": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • compare_zones reads unknown 1h ago

    Compare one endpoint across multiple zones. `start`/`end` default to UTC; `start` inclusive, `end` EXCLUSIVE. `tz="local"` is rejected (zones may differ); pass an explicit IANA tz like "Europe/Berlin" if you need wall-clock alignment. `filters={column: [values]}` keeps only rows whose categorical column holds one of the values, in every zone (see get_series); zones whose periods hold several rows are listed under `split_periods_by_zone`. A zone whose series stopped upstream before the window's end (GB day-ahead after 2020-12-31) is listed under `series_ended_by_zone`, with the endpoint that carries it on — an empty `[]` there is not "no data yet".

    mcp-tool

    {
  "type": "object",
  "required": [
    "endpoint",
    "zones",
    "start",
    "end"
  ],
  "properties": {
    "tz": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "end": {
      "type": "string"
    },
    "start": {
      "type": "string"
    },
    "zones": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "filters": {
      "anyOf": [
        {
          "type": "object",
          "additionalProperties": {
            "type": "array",
            "items": {
              "type": "string"
            }
          }
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "endpoint": {
      "type": "string"
    },
    "aggregation": {
      "type": "string",
      "default": "daily"
    }
  },
  "additionalProperties": false
}
    arguments 59 lines
  • get_day_ahead_prices reads unknown 1h ago

    Day-ahead clearing price for a bidding zone, in the zone's trading currency (EUR for euro zones; the per-row `currency` column and the response `unit` say which — GB=GBP, PL/RO/BG carry local-currency eras). `start`/`end` default to UTC; `start` inclusive, `end` EXCLUSIVE. For 'all of April 2026' use start=2026-04-01, end=2026-05-01 (end=2026-04-30 silently drops the final UTC day — and 1–2 local-time hours of April for European zones in CET/CEST). The response's `period` block shows the resolved window so you can verify (a 30-day month is 720 hours). `tz`: pass "local" to interpret start/end as wall-clock in the zone's timezone, or an explicit IANA name like "Europe/Berlin". The server converts to UTC at the boundary. GB/UK: ENTSO-E's GB day-ahead price ended 2020-12-31, when GB left European market coupling. For later windows use `get_series(endpoint="day_ahead_price_imrp", zone="GB", …)` — the same GB day-ahead auction, GBP/MWh, published ~D-2; a window past a series' end answers with `series_ended`, naming the endpoint that carries it on. If you're computing a **generation-weighted** price metric — capture price, capture rate, value factor, merchant-PPA achieved price — use `get_derivation(slug="capture_price", …)` instead. It runs server-side over the full window and returns monthly rows; no row cap, no pagination.

    mcp-tool

    {
  "type": "object",
  "required": [
    "zone",
    "start",
    "end"
  ],
  "properties": {
    "tz": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "end": {
      "type": "string"
    },
    "zone": {
      "type": "string"
    },
    "start": {
      "type": "string"
    },
    "aggregation": {
      "type": "string",
      "default": "raw"
    }
  },
  "additionalProperties": false
}
    arguments 35 lines
  • get_crossborder_flow reads unknown never probed

    Cross-border physical flow (MW) between two adjacent zones. `start`/`end` default to UTC; `start` inclusive, `end` EXCLUSIVE. `tz="local"` uses the FROM-zone's timezone; or pass an IANA name.

    mcp-tool

    {
  "type": "object",
  "required": [
    "from_zone",
    "to_zone",
    "start",
    "end"
  ],
  "properties": {
    "tz": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "end": {
      "type": "string"
    },
    "start": {
      "type": "string"
    },
    "to_zone": {
      "type": "string"
    },
    "from_zone": {
      "type": "string"
    },
    "aggregation": {
      "type": "string",
      "default": "raw"
    }
  },
  "additionalProperties": false
}
    arguments 39 lines
  • get_outages reads unknown 3h ago

    Generation-unit unavailability events (UMM). `start`/`end` default to UTC; `start` inclusive, `end` EXCLUSIVE. An outage is returned if it overlaps the window. Pass `tz="local"` or an IANA name to interpret start/end as wall-clock in that timezone. A zone whose outage feed stopped upstream (GB, 2021-06-15) carries `series_ended`: outages announced since then are missing, though older documents may still schedule events into the window.

    mcp-tool

    {
  "type": "object",
  "required": [
    "zone",
    "start",
    "end"
  ],
  "properties": {
    "tz": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "end": {
      "type": "string"
    },
    "kind": {
      "type": "string",
      "default": "generation"
    },
    "zone": {
      "type": "string"
    },
    "start": {
      "type": "string"
    },
    "min_mw": {
      "anyOf": [
        {
          "type": "number"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    }
  },
  "additionalProperties": false
}
    arguments 46 lines
  • get_series reads unknown 3h ago

    Generic time-series query for ANY registered series endpoint. One tool covers every (non-outage) endpoint in the registry, so adding a new dataset (call `list_endpoints()` to see the current 14) gets an MCP surface automatically — no new tool to learn. Argument shape adapts to the endpoint: • single-zone (day_ahead_price, actual_load, generation_per_type, …) → pass `zone="DE_LU"` • cross-zone (crossborder_flow, scheduled_exchanges, net_transfer_capacity_dayahead) → pass `from_zone="DE_LU"` AND `to_zone="FR"` • psr-dependent (generation_per_type, wind_solar_forecast, installed_generation_capacity) → optionally filter via `psr_types=["solar","wind_onshore"]` `start`/`end`: UTC by default; `start` inclusive, `end` EXCLUSIVE (for "all of April 2026" use end=2026-05-01). Pass `tz="local"` or an IANA name to interpret as wall-clock in that timezone. `aggregation`: 'raw' (default — native PT15M/PT60M per endpoint), 'hourly' (AVG over quarters → one row per hour, useful for the growing list of PT15M-stored endpoints like DE_LU day_ahead_price), 'daily', or 'monthly'. For day-ahead prices specifically the auction still clears hourly even where stored at PT15M, so AVG=any-quarter; SUM would 4× over-count. Currency: price columns keep `_eur_` in their names for stability. An endpoint whose rows carry a `currency` column (day-ahead and intraday prices, the A81/A15 capacity prices, activated_balancing_price, imbalance_prices) labels each row (PLN, HUF, RON, CZK, GBP, …) and the response `unit` follows it; `unit` is null when the window mixes currencies (`mixed_currency`) or, for activated_balancing_price and imbalance_prices, holds rows of unknown currency (`currency_unknown_rows`). Never average a price across rows with different `currency`. Split periods: when a response carries `split_periods`, some periods hold more than one row — different published series told apart by the listed columns (activated_balancing_price: `product`, e.g. CZ/SK mFRR standard A01 vs specific A02; or `currency`). Never average across them. Keep one with `filters={"product": ["A01"]}` — `filters` takes any categorical column of the endpoint (`{column: [values]}`). Process types: activated balancing prices are one endpoint per ENTSO-E processType (activated_balancing_price = A16 realised; _mfrr_scheduled = A60, _mfrr_direct = A61, _afrr_local = A68) — different prices for the same period, never to be merged. `related_series` names the siblings holding data for the zone. Ended series: a window reaching past the day a series stopped upstream (a zone that left ENTSO-E, a frozen archive, a series that ended) carries `series_ended` — the last day, why, and `successors`: the endpoints that carry it on, each with a ready `call` and a `note` on how it differs. GB day-ahead after 2020-12-31 → day_ahead_price_imrp (GBP/MWh); GB generation after 2021-06-15 → generation_mix (NESO). Outage-family endpoints (different schema) stay on `get_outages()`.

    mcp-tool

    {
  "type": "object",
  "required": [
    "endpoint",
    "start",
    "end"
  ],
  "properties": {
    "tz": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "end": {
      "type": "string"
    },
    "zone": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "start": {
      "type": "string"
    },
    "filters": {
      "anyOf": [
        {
          "type": "object",
          "additionalProperties": {
            "type": "array",
            "items": {
              "type": "string"
            }
          }
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "to_zone": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "endpoint": {
      "type": "string"
    },
    "from_zone": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "psr_types": {
      "anyOf": [
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "aggregation": {
      "type": "string",
      "default": "raw"
    }
  },
  "additionalProperties": false
}
    arguments 99 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 7b9c1bacb41710bf.

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

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.