_ registry / mcp streamable-http · checked 1h ago

motor-row

https://offerlaneauto.com

Registry code: 91d91e915e021747

api record

Motor Row is an online marketplace for used cars in Indianapolis, Indiana. Local dealers list the cars they have for sale; shoppers browse free and contact the dealer directly. Motor Row does not own the cars and is not a party to any sale. Listing details are entered by dealers and are not verified by Motor Row. Use search_cars to find cars, get_car for one listing, site_info for how the marketplace works. Always tell users to confirm price and availability with the dealer.

endpoint
https://offerlaneauto.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 it live, free and safe measured by this hub
Is motor-row live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is motor-row free to use?
Yes — the hub reached it with no key and no payment.
What tools does motor-row have?
3 tools: site_info, get_car, search_cars.
Is motor-row 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
100%

90 days 100%· all time 100%

latency
530ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 3 tools
1 open 2 never probed 1 of 3 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.

  • search_cars open 1h ago

    Search the used cars currently for sale on Motor Row (Indianapolis, Indiana). All filters optional. Returns a count and up to `limit` cars, each with a plain-English summary, price, mileage, location, photos, the selling dealer's contact details, and links. Listing data was entered by the dealer and is not verified by Motor Row.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "make": {
      "type": "string"
    },
    "sort": {
      "enum": [
        "newest",
        "price_asc",
        "price_desc",
        "mileage_asc"
      ],
      "type": "string",
      "default": "newest"
    },
    "limit": {
      "type": "integer",
      "default": 25,
      "maximum": 100
    },
    "model": {
      "type": "string"
    },
    "query": {
      "type": "string",
      "description": "Free-text words to match against year, make, model, trim, city and description, e.g. \"honda civic\" or \"truck 4wd\"."
    },
    "year_max": {
      "type": "integer"
    },
    "year_min": {
      "type": "integer"
    },
    "max_price": {
      "type": "number",
      "description": "US dollars"
    },
    "min_price": {
      "type": "number",
      "description": "US dollars"
    },
    "max_mileage": {
      "type": "integer",
      "description": "miles"
    }
  },
  "additionalProperties": false
}
    arguments 49 lines
  • site_info unknown never probed

    What Motor Row is, how buying works, how dealers can list cars, contact details, and the URLs of the machine-readable versions of the site.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_car unknown 1h ago

    Get one Motor Row listing by its id (e.g. "CL-9E9039FA2F"), including sold or removed status.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    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 91d91e915e021747.

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

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.