_ registry / mcp streamable-http · checked just now

chargealong

https://api.chargealong.io

Registry code: 6c0cf56228c0f953

api record

Public EV charging sites in Australia, New Zealand, the United States, Canada and the United Kingdom, with their plugs, power, price, network and access. Use find_chargers for what is nearest a coordinate, which is the usual question, and narrow it with min_kw, plugs and network when the question does; use search_places first when there is a suburb name but no coordinate; use get_charger to read one site in full, with its connectors and how to get in; use list_networks for who operates chargers in a country. No key and no account: this is free to call. Every answer carries the page's URL and…

endpoint
https://api.chargealong.io/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 it live, free and safe measured by this hub
Is chargealong live?
Yes — it answered the hub's last check (checked just now). It answered 98% of checks over the last 30 days.
Is chargealong free to use?
Yes — the hub reached it with no key and no payment.
What tools does chargealong have?
4 tools: list_networks, get_charger, find_chargers, search_places.
Is chargealong 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
98.4%

90 days 99.1%· all time 99.1%

latency
1,255ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 317 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· HTTP 522
  • down → live
_ what it is for
topic
energy & utilities ev charging
used for
  • find nearest ev chargers
  • get ev charging site details
  • list charging networks in a country
  • search places by name
takes → gives
data → data
tools
4 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

inferred, not observed

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

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

  • list_networks reads unknown 5h ago

    Every network with charging sites in a country, biggest first, with how many sites and how many regions each reaches.

    mcp-tool

    {
  "type": "object",
  "required": [
    "country"
  ],
  "properties": {
    "country": {
      "type": "string",
      "description": "Country slug: australia, new-zealand, united-states, canada or united-kingdom."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_charger reads unknown 21h ago

    Everything about one site from an earlier answer: its connectors with power and quantity, price, access notes, network and when the record was last checked.

    mcp-tool

    {
  "type": "object",
  "required": [
    "public_id"
  ],
  "properties": {
    "public_id": {
      "type": "string",
      "description": "The id from an earlier answer, the last part of a site's URL: abcd2345."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • find_chargers reads unknown 21h ago

    The charging sites nearest a point, nearest first, with their power, plugs, price, network and the page each is on. Narrow with min_kw for fast charging, plugs for what the car takes, and network for one operator.

    mcp-tool

    {
  "type": "object",
  "required": [
    "lat",
    "lng"
  ],
  "properties": {
    "lat": {
      "type": "number",
      "description": "Latitude in degrees, between -90 and 90."
    },
    "lng": {
      "type": "number",
      "description": "Longitude in degrees, between -180 and 180."
    },
    "limit": {
      "type": "integer",
      "description": "How many sites to return, 1 to 30. Default 10."
    },
    "plugs": {
      "type": [
        "null",
        "array"
      ],
      "items": {
        "type": "string"
      },
      "description": "Only sites with one of these plugs: ccs2, ccs1, chademo, type-2, type-1, nacs, gbt."
    },
    "min_kw": {
      "type": "number",
      "description": "Only sites this fast or faster, in kW. 50 is rapid, 150 and above is ultra fast."
    },
    "network": {
      "type": "string",
      "description": "Only this network, by slug: tesla, evie-networks, chargefox and so on. Use list_networks to find one."
    },
    "radius_km": {
      "type": "number",
      "description": "How far to look, in kilometres, up to 150. Default 50."
    }
  },
  "additionalProperties": false
}
    arguments 44 lines
  • search_places reads unknown 21h ago

    Places matching a name, each with a coordinate to search around and the count of charging sites in it.

    mcp-tool

    {
  "type": "object",
  "required": [
    "q"
  ],
  "properties": {
    "q": {
      "type": "string",
      "description": "A suburb, town or postcode. At least two characters."
    }
  },
  "additionalProperties": false
}
    arguments 13 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 6c0cf56228c0f953.

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