Chargt EV Charging — Netherlands
Registry code: 6d90520943db8d23
Find EV charging stations, live availability and prices across the Netherlands via NDW data.
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.chargt.eu/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 Chargt EV Charging — Netherlands live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is Chargt EV Charging — Netherlands free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does Chargt EV Charging — Netherlands have?
- 2 tools: chargt_find_chargers, chargt_get_details.
- Is Chargt EV Charging — Netherlands 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.
90 days 99.5%· all time 99.5%
last good check
of 2 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- find ev charging stations nearby
- check charger availability and prices
- takes → gives
- text → data
- tools
- 2 reads
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.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
chargt_find_chargers reads unknown 18h ago
Find electric vehicle charging stations near a location in the Netherlands. This server is currently NL-only: the country parameter accepts only 'NL' (default). Returns stations sorted by distance (closest first), then by power output (fastest first), with prices from the Dutch National Road Traffic Data Portal (NDW). Includes operator name, station name, address, connector types, power, parking type, and postal code. Some chargers have time-of-use pricing (price varies by time of day) — these are shown as a price range. Some stations charge extra fees NOT included in the per-kWh price: a one-off start fee, an idle fee, or a time-based fee. Each hit flags this compactly via has_additional_costs plus up-to amounts (start_fee_eur / idle_fee_eur_per_hour / time_fee_eur_per_hour). When flagged, call get_details for the full breakdown. Prices update daily from the NDW. This tool does not return live availability; call get_details for a specific station's near-real-time NDW availability (real-time status for stations that report it). Prices are indicative and sourced from NDW — tell the user to verify at the charger before relying on them, and do NOT recommend a specific charge card or plan.
{ "type": "object", "required": [ "latitude", "longitude" ], "properties": { "limit": { "type": "integer", "default": 20, "description": "Max result count, default 20, max 50" }, "country": { "enum": [ "NL" ], "type": "string", "default": "NL", "description": "Country of the charging stations; NL only" }, "language": { "enum": [ "nl", "en" ], "type": "string", "default": "nl", "description": "Response prose language; default nl" }, "latitude": { "type": "number", "description": "Decimal degrees, e.g. 52.0902" }, "longitude": { "type": "number", "description": "Decimal degrees, e.g. 5.1213" }, "radius_km": { "type": "number", "default": 10, "description": "Search radius, clamped to max 50" }, "min_power_kw": { "type": "number", "description": "Minimum charging power, e.g. 50" }, "connector_types": { "type": "array", "items": { "type": "string" }, "description": "Connector types (case-insensitive): friendly names (CCS, CHAdeMO, TYPE2, TYPE1) or raw OCPI/IEC codes (e.g. IEC_62196_T2). e.g. [\"CCS\"], [\"CCS\",\"CHAdeMO\"]" } } }arguments 55 lineschargt_get_details reads unknown 18h ago
Full station details for one Dutch EV charging station, including near-real-time NDW availability. This server is currently NL-only: the country parameter accepts only 'NL' (default). Returns: operator, all connectors with power levels and prices, and the full cost breakdown (price_slots) including the per-kWh (ENERGY) price, time-based (TIME) fees, idle (PARKING_TIME) fees, and one-off/start (FLAT) fees. Also returns parking type, postal code, and live availability status when the station reports to NDW. availability.status is one of available|partial|occupied|unknown matching the Chargt website: available="Beschikbaar"(nl)/"available"(en); partial="Gedeeltelijk bezet"/"partially occupied"; occupied="Alle plaatsen bezet"/"all occupied"; unknown="Onbekend"/"unknown". available_count/total_count give the count, e.g. "2 van de {total} laadpunten vrij"(nl) / "{available} of {total} chargers available"(en) — use the language param for the locale; never state a count as 0 when it is null/unknown. availability.availability_note (localized nl/en) explains the status semantics: when status is "unknown" it usually means the latest live NDW reading was older than 15 hours and was filtered out, or no live reading has come in yet — report this as "unknown / retry in a few minutes", NOT as "no data" or a coverage gap (the charging point exists). When status is available|partial|occupied, the note confirms a current live NDW reading as of the timestamp shown. This is the only Chargt tool that returns the complete tariff breakdown and real-time availability. Call this after find_chargers flags a station with extra fees (start/idle/time) to see its exact costs. Prices are indicative and sourced from NDW — tell the user to verify at the charger before relying on them, and do NOT recommend a specific charge card or plan.
{ "type": "object", "required": [ "station_id" ], "properties": { "country": { "enum": [ "NL" ], "type": "string", "default": "NL", "description": "Country of the charging station; NL only" }, "language": { "enum": [ "nl", "en" ], "type": "string", "default": "nl", "description": "Response prose language; default nl" }, "station_id": { "type": "string", "description": "Charging station ID" } } }arguments 29 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id6d90520943db8d23.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/6d90520943db8d23/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/6d90520943db8d23?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.