ev-load-check
https://ev-load-check.permitev.com
Registry code: 72258a05740981c0
NEC-based screening for a home EV charger: panel capacity, wire sizing, voltage drop, GA incentives.
from a public catalogue that lists it, not from the operator
- endpoint
- https://ev-load-check.permitev.com/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 ev-load-check live?
- Yes — it answered the hub's last check (checked 51m ago). It answered 100% of checks over the last 30 days.
- Is ev-load-check free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does ev-load-check have?
- 4 tools: check_panel_capacity, recommend_charger_setup, check_voltage_drop, lookup_georgia_rebate.
- Is ev-load-check 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 100%· all time 100%
last good check
of 4 tools
- unknown → live
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
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.
lookup_georgia_rebate open 51m ago
Look up Georgia EV charger rebates and incentives: the Georgia Power EV rebate program and the Georgia state tax credit. Use when a user asks about EV charger rebates, incentives, or tax credits in Georgia.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "charger_type": { "enum": [ "level2", "dcfc", "unknown" ], "type": "string", "description": "Level 2 charger or DC fast charger. Default level2." } }, "additionalProperties": false }arguments 16 linescheck_panel_capacity unknown 51m ago
Check whether a home's electrical panel has capacity for an EV charger. Use when a user asks if their panel or breaker box can handle an EV charger, or whether they need a panel upgrade or load management. Returns a verdict (fits / tight / does-not-fit), amps, and a plain-language explanation.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "main_breaker_amps", "charger_amps" ], "properties": { "appliances": { "type": "array", "items": { "type": "object", "required": [ "name", "va" ], "properties": { "va": { "type": "number", "description": "Nameplate VA (volts x amps) from the label" }, "name": { "type": "string", "description": "Appliance name, e.g. 'electric range'" }, "count": { "type": "number" } }, "additionalProperties": false }, "maxItems": 15, "description": "Major appliances with nameplate VA. Optional; improves accuracy." }, "charger_amps": { "type": "integer", "maximum": 80, "minimum": 8, "description": "Charger charging current in amps, e.g. 32, 40, 48, 80" }, "square_footage": { "type": "integer", "maximum": 20000, "minimum": 200, "description": "Home size in square feet. Omit if unknown (assumes 2000)." }, "main_breaker_amps": { "type": "integer", "maximum": 400, "minimum": 30, "description": "Main breaker rating of the panel in amps, e.g. 100, 150, 200" } }, "additionalProperties": false }arguments 55 linesrecommend_charger_setup unknown never probed
Recommend breaker size, wire gauge, conduit, and ground wire for a home EV charger circuit. Use when a user asks what wire size, breaker, or circuit their charger needs. Returns wire gauge, breaker amps, EGC size, and a plain-language explanation with NEC citations.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "charger_amps" ], "properties": { "charger_amps": { "type": "integer", "maximum": 80, "minimum": 8, "description": "Charger charging current in amps, e.g. 32, 40, 48" }, "run_length_ft": { "type": "integer", "maximum": 500, "minimum": 10, "description": "Cable run length in feet. Omit if unknown." }, "wire_material": { "enum": [ "Cu", "Al" ], "type": "string", "description": "Copper (Cu) or aluminum (Al) wire. Default copper." }, "ambient_temp_c": { "type": "number", "maximum": 60, "minimum": -10, "description": "Ambient temperature in Celsius. Default 30 (standard)." } }, "additionalProperties": false }arguments 36 linescheck_voltage_drop unknown never probed
Check whether a cable run length causes excessive voltage drop for an EV charger circuit. Use when a user asks about long garage/driveway runs, voltage drop, upsizing wire for distance. Returns pass/fail at 3%.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "charger_amps", "wire_size", "run_length_ft" ], "properties": { "wire_size": { "enum": [ "14", "12", "10", "8", "6", "4", "3", "2", "1", "1/0", "2/0", "3/0", "4/0" ], "type": "string", "description": "Wire gauge in AWG, e.g. '8' for 8 AWG" }, "charger_amps": { "type": "integer", "maximum": 80, "minimum": 8, "description": "Charging current in amps" }, "run_length_ft": { "type": "integer", "maximum": 500, "minimum": 10, "description": "One-way cable run length in feet" }, "wire_material": { "enum": [ "Cu", "Al" ], "type": "string", "description": "Default copper." } }, "additionalProperties": false }arguments 51 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 id72258a05740981c0.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/72258a05740981c0/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/72258a05740981c0?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.