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

oversize-escort-hub

https://www.oversize-escort-hub.com

Registry code: 5e501b56db338312

api record

Read-only tools about pilot car (P/EVO) work and the Oversize Escort Hub marketplace. Pilot car rules are set by each state and change: tell people to confirm with the state. Contact details are never available through these tools.

endpoint
https://www.oversize-escort-hub.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 it live, free and safe measured by this hub
Is oversize-escort-hub live?
Yes — it answered the hub's last check (checked 15h ago). It answered 100% of checks over the last 30 days.
Is oversize-escort-hub free to use?
Yes — the hub reached it with no key and no payment.
What tools does oversize-escort-hub have?
5 tools: find_pilot_car_escorts, search_open_loads, get_pilot_car_guide, search_open_jobs, get_site_facts.
Is oversize-escort-hub 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 5 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 5 tools
3 open 2 never probed 3 of 5 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_pilot_car_guide open 15h ago

    Links-only guide for people new to pilot car / P/EVO work: what the job is in plain words, free training links (FHWA and the Evergreen Safety Council), where to check each state's own rules (FHWA's list of state permit offices), and finding work on Oversize Escort Hub. It states no rules: rules are set state by state and change, so always check with the state.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "section": {
          "type": "string",
          "description": "Optional section id: what-it-is, learn, state-rules, finding-work. Omit for the whole guide."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • search_open_jobs open 15h ago

    Open jobs from companies and fleets hiring pilot car / P/EVO subcontractors or drivers: title, company, contractor or employee, vehicle and gear, pay, schedule, base location and a link. Applicants and posters share contact details only after the company accepts.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1
        },
        "state": {
          "type": "string",
          "description": "Optional two-letter state or province code the job is based in or covers."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • get_site_facts open 15h ago

    What Oversize Escort Hub is, what it costs, how the flat-rate board and the Bid Board work for escorts, carriers, brokers and fleets, and the privacy rules.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • find_pilot_car_escorts unknown never probed

    Pilot car / P/EVO escorts who list a US state, DC or Canadian province on Oversize Escort Hub. Returns names and a profile link. Oversize Escort Hub does not check or verify anyone. No phone numbers or emails: an escort's contact details go to a poster only when the poster accepts that escort for a load. A listing does not mean the escort is free today.

    mcp-tool

    {
      "type": "object",
      "required": [
        "state"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1
        },
        "state": {
          "type": "string",
          "description": "Two-letter state or province code, for example TX or AB."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • search_open_loads unknown never probed

    Open loads on the boards right now: route, escort type, pay, date and a link. No company names or contact details. Optionally filter by a state the load starts or ends in.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1
        },
        "state": {
          "type": "string",
          "description": "Optional two-letter state or province code."
        }
      },
      "additionalProperties": false
    }
    arguments 15 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 5e501b56db338312.

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

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.