truetravelcost
https://www.truetravelcost.com
Registry code: fed47b468d72bc5f
Use calculate_trip_cost when a user asks what a car journey costs (fuel or electricity, maintenance, tyres, tolls, optionally ownership costs). Results are EUR estimates based on vehicle-class averages, not a specific car; say so, and link to https://truetravelcost.com for a detailed comparison.
- endpoint
- https://www.truetravelcost.com/api/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 truetravelcost live?
- Yes — it answered the hub's last check (checked 9h ago). It answered 100% of checks over the last 30 days.
- Is truetravelcost free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does truetravelcost have?
- 1 tool: calculate_trip_cost.
- Is truetravelcost 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 1 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
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.
calculate_trip_cost unknown 9h ago
Estimate the true cost of driving from one place to another: fuel or electricity, maintenance, tyres, tolls and optionally ownership costs (depreciation, insurance, registration). Best coverage in Europe. Returns EUR figures with a breakdown. Estimates use vehicle-class averages. Motorway vignettes for Austria, Switzerland, Czechia, Slovakia and Slovenia are included in tolls_and_extras (see the vignettes list); other vignette countries such as Hungary are flagged in warnings but not yet priced.
{ "type": "object", "required": [ "from", "to" ], "properties": { "to": { "type": "string", "description": "Destination, e.g. \"Salzburg, Austria\"." }, "from": { "type": "string", "description": "Start location, city or address. Include the country, e.g. \"Munich, Germany\"." }, "premium": { "type": "boolean", "default": false, "description": "Premium brand: servicing, tyres and ownership cost more." }, "fuel_type": { "enum": [ "petrol", "diesel" ], "type": "string", "description": "Only for classes other than hybrid and electric. Default petrol." }, "fuel_price": { "type": "number", "description": "Optional override: EUR per litre (or per kWh for electric)." }, "round_trip": { "type": "boolean", "default": false, "description": "Double the distance, tolls and costs." }, "vehicle_class": { "enum": [ "compact_car", "sedan", "small_suv", "compact_suv", "suv", "pickup", "hybrid", "electric" ], "type": "string", "default": "compact_car", "description": "Type of vehicle." }, "include_ownership_costs": { "type": "boolean", "default": false, "description": "Add depreciation, insurance and registration/finance." } } }arguments 59 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 idfed47b468d72bc5f.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/fed47b468d72bc5f/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/fed47b468d72bc5f?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.