_ registry / mcp streamable-http · checked 21m ago

voxcars-pt

https://www.voxcars.pt

Registry code: a88a22c51ba54d4c

api record

Used-car listings in Portugal: search, price statistics, comparables and articles.

from a public catalogue that lists it, not from the operator

endpoint
https://www.voxcars.pt/api/mcp
protocol
streamable-http ·2024-11-05
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 voxcars-pt live?
Yes — it answered the hub's last check (checked 21m ago). It answered 100% of checks over the last 30 days.
Is voxcars-pt free to use?
Yes — the hub reached it with no key and no payment.
What tools does voxcars-pt have?
6 tools: search_cars_by_description, find_similar_cars, get_car_detail, get_price_stats, search_articles, search_cars.
Is voxcars-pt 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.6%

90 days 99.3%· all time 99.3%

latency
212ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 400 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
payments & commerce marketplaces & listings
used for
  • search used cars for sale in portugal
  • get used car price statistics
  • find comparable car listings
  • read used car market articles
takes → gives
text, data → data
tools
6 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 6 tools
3 open 3 never probed 3 of 6 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.

  • get_price_stats reads open 20h ago

    Get price statistics for a slice of the Portugal used-car market: how many listings match, the median price, the p25–p75 range, the median price per kilometre and a breakdown by body type. Use this when the user asks what something costs, whether an asking price is fair, or how two makes compare — instead of listing individual cars. Takes the same filters as search_cars and describes exactly the set that tool would return, so the two never disagree. Reports medians and quartiles rather than averages, because car prices have a long right tail and a single luxury listing moves an average.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "fuel": {
      "enum": [
        "GASOLINE",
        "DIESEL",
        "ELECTRIC",
        "HYBRID",
        "PLUG_IN_HYBRID",
        "LPG"
      ],
      "type": "string",
      "description": "Fuel type. GASOLINE = gasolina, ELECTRIC = eléctrico, HYBRID = full hybrid, PLUG_IN_HYBRID = PHEV."
    },
    "make": {
      "type": "string",
      "description": "Make slug (e.g. toyota, bmw, volkswagen). Not free text — the slug is the same in every market."
    },
    "kmMax": {
      "type": "number",
      "description": "Maximum kilometres on the odometer."
    },
    "model": {
      "type": "string",
      "description": "Model slug (e.g. corolla, serie-3, golf). Requires `make` to disambiguate."
    },
    "yearMax": {
      "type": "number",
      "description": "Maximum registration year."
    },
    "yearMin": {
      "type": "number",
      "description": "Minimum registration year."
    },
    "bodyType": {
      "enum": [
        "SUV",
        "SEDAN",
        "HATCHBACK",
        "COMBI",
        "COUPE",
        "CABRIO",
        "MINIVAN",
        "PICKUP"
      ],
      "type": "string",
      "description": "Body style. SEDAN = berlina, HATCHBACK = citadino, COMBI = carrinha, CABRIO = descapotável, MINIVAN = monovolume."
    },
    "district": {
      "type": "string",
      "description": "District or region inside the market (e.g. Lisboa, Porto, Berlin, Madrid). Matched exactly."
    },
    "priceMax": {
      "type": "number",
      "description": "Maximum price in the market currency. Listings with no published price are excluded by either bound."
    },
    "priceMin": {
      "type": "number",
      "description": "Minimum price in the market currency."
    },
    "condition": {
      "enum": [
        "new",
        "used",
        "semi_new"
      ],
      "type": "string",
      "description": "Vehicle condition. new = 0 km / registered this year; semi_new = <2 years and <20 000 km; used = everything else."
    }
  }
}
    arguments 72 lines
  • search_articles reads open 20h ago

    Search editorial articles about the used-car market in Portugal: buying guides, reviews, comparisons and market analysis. Use this when the user asks how something works — financing, warranty, IUC, IPO/ITV, the buying process — rather than asking for listings.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Maximum number of results (default 5, max 10)."
    },
    "category": {
      "enum": [
        "GUIA",
        "REVIEW",
        "COMPARATIVO",
        "MERCADO",
        "GLOSSARIO",
        "NOTICIA"
      ],
      "type": "string",
      "description": "Article category."
    }
  }
}
    arguments 21 lines
  • search_cars reads open 20h ago

    Search current used-car listings for sale in Portugal. Use this whenever the user wants to find, compare or explore cars — by make, model, budget, mileage, fuel or district. Returns price, mileage, fuel, body and a citable listing URL, plus `total`: the exact number of listings matching the filters, which makes this tool usable to answer 'how many' questions. Listings are aggregated from stands and portals and refreshed daily; each result carries `publishedAt`. Prefer the broadest filters that answer the question and report `total` as a floor, not a census.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "fuel": {
      "enum": [
        "GASOLINE",
        "DIESEL",
        "ELECTRIC",
        "HYBRID",
        "PLUG_IN_HYBRID",
        "LPG"
      ],
      "type": "string",
      "description": "Fuel type. GASOLINE = gasolina, ELECTRIC = eléctrico, HYBRID = full hybrid, PLUG_IN_HYBRID = PHEV."
    },
    "make": {
      "type": "string",
      "description": "Make slug (e.g. toyota, bmw, volkswagen). Not free text — the slug is the same in every market."
    },
    "page": {
      "type": "number",
      "description": "1-based page number. Use with `total` to walk a large result set."
    },
    "sort": {
      "enum": [
        "recent",
        "price_asc",
        "price_desc",
        "km_asc",
        "year_desc"
      ],
      "type": "string",
      "description": "Result order. Default `recent` (most recently seen first)."
    },
    "kmMax": {
      "type": "number",
      "description": "Maximum kilometres on the odometer."
    },
    "limit": {
      "type": "number",
      "description": "Results per page (default 10, max 20)."
    },
    "model": {
      "type": "string",
      "description": "Model slug (e.g. corolla, serie-3, golf). Requires `make` to disambiguate."
    },
    "yearMax": {
      "type": "number",
      "description": "Maximum registration year."
    },
    "yearMin": {
      "type": "number",
      "description": "Minimum registration year."
    },
    "bodyType": {
      "enum": [
        "SUV",
        "SEDAN",
        "HATCHBACK",
        "COMBI",
        "COUPE",
        "CABRIO",
        "MINIVAN",
        "PICKUP"
      ],
      "type": "string",
      "description": "Body style. SEDAN = berlina, HATCHBACK = citadino, COMBI = carrinha, CABRIO = descapotável, MINIVAN = monovolume."
    },
    "district": {
      "type": "string",
      "description": "District or region inside the market (e.g. Lisboa, Porto, Berlin, Madrid). Matched exactly."
    },
    "priceMax": {
      "type": "number",
      "description": "Maximum price in the market currency. Listings with no published price are excluded by either bound."
    },
    "priceMin": {
      "type": "number",
      "description": "Minimum price in the market currency."
    },
    "condition": {
      "enum": [
        "new",
        "used",
        "semi_new"
      ],
      "type": "string",
      "description": "Vehicle condition. new = 0 km / registered this year; semi_new = <2 years and <20 000 km; used = everything else."
    }
  }
}
    arguments 91 lines
  • search_cars_by_description reads unknown 10h ago

    Search Portugal listings by describing the car in plain language, matched against listing text by meaning rather than keywords. Use this for wants that are not filter fields — 'a family SUV good in the snow', 'a low-mileage hybrid for the city', 'a used 4x4 to restore'. Prefer search_cars for entirely structural queries (make/model/budget); use this when the request is descriptive. Combine both by passing structural filters here too — they act as hard constraints while the description only ranks. Results are ordered by relevance, so `total` is the number matching the structural filters, not the number that fit the description.

    mcp-tool

    {
  "type": "object",
  "required": [
    "description"
  ],
  "properties": {
    "fuel": {
      "enum": [
        "GASOLINE",
        "DIESEL",
        "ELECTRIC",
        "HYBRID",
        "PLUG_IN_HYBRID",
        "LPG"
      ],
      "type": "string",
      "description": "Fuel type. GASOLINE = gasolina, ELECTRIC = eléctrico, HYBRID = full hybrid, PLUG_IN_HYBRID = PHEV."
    },
    "make": {
      "type": "string",
      "description": "Make slug (e.g. toyota, bmw, volkswagen). Not free text — the slug is the same in every market."
    },
    "kmMax": {
      "type": "number",
      "description": "Maximum kilometres on the odometer."
    },
    "limit": {
      "type": "number",
      "description": "Maximum number of results (default 10, max 20)."
    },
    "yearMin": {
      "type": "number",
      "description": "Minimum registration year."
    },
    "bodyType": {
      "enum": [
        "SUV",
        "SEDAN",
        "HATCHBACK",
        "COMBI",
        "COUPE",
        "CABRIO",
        "MINIVAN",
        "PICKUP"
      ],
      "type": "string",
      "description": "Body style. SEDAN = berlina, HATCHBACK = citadino, COMBI = carrinha, CABRIO = descapotável, MINIVAN = monovolume."
    },
    "priceMax": {
      "type": "number",
      "description": "Maximum price in the market currency. Listings with no published price are excluded by either bound."
    },
    "description": {
      "type": "string",
      "description": "What the user is looking for, in their own words. Full phrases work better than keywords. Pass the qualities here and the hard limits in the other arguments."
    }
  }
}
    arguments 58 lines
  • find_similar_cars reads unknown 10h ago

    Given one listing, find comparable ones: same make, similar year, mileage and price band. Use this when the user likes a car but wants alternatives — 'find me something similar', 'the same but cheaper', 'what else is around this price'. Pass `maxPrice` for the cheaper case; without it, comparables are drawn from a band around the reference price. Comparability is by structure (make/model/year/km/price), not by text similarity: it answers 'is this well priced for what it is', which a keyword search cannot.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Slug of the reference listing, as returned by search_cars or get_car_detail."
    },
    "limit": {
      "type": "number",
      "description": "Maximum number of comparables (default 6, max 20)."
    },
    "maxPrice": {
      "type": "number",
      "description": "Optional budget ceiling, in EUR. Use it for 'similar but cheaper'; it overrides the default band around the reference price."
    }
  }
}
    arguments 20 lines
  • get_car_detail reads unknown 10h ago

    Get the complete record of one used-car listing in Portugal by its slug. Use this after search_cars when the user asks about a specific car: full description, features, photos, seller, and the original source URL to cite.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Unique listing slug, as returned by search_cars."
    }
  }
}
    arguments 12 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 a88a22c51ba54d4c.

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