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

Operating Authority Sentinel

https://authority.amacunia.fr

Registry code: 35f805099d9e0241

api record

US motor carrier operating authority and insurance status by USDOT number, read live from the public FMCSA registration datasets (Motus); carrier_compliance_lookup adds the MCS-150 biennial update deadline from the Company Census File. Use authority_example and carrier_compliance_example (free) to see the output; authority_lookup and carrier_compliance_lookup are paid via x402 (USDC on Base).

endpoint
https://authority.amacunia.fr/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 Operating Authority Sentinel live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is Operating Authority Sentinel free to use?
Not measured yet.
What tools does Operating Authority Sentinel have?
4 tools: authority_example, carrier_compliance_example, authority_lookup, carrier_compliance_lookup.
Is Operating Authority Sentinel 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
152ms

last good check

priced tools
0

of 4 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 4 tools
4 never probed 0 of 4 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.

  • authority_example unknown never probed

    Free sample: a real answer for one large motor carrier, same shape as authority_lookup.

    mcp-tool

    {
      "type": "object",
      "title": "authority_exampleArguments",
      "properties": {}
    }
    arguments 5 lines
  • carrier_compliance_example unknown never probed

    Free sample: a real answer for one large motor carrier, same shape as carrier_compliance_lookup.

    mcp-tool

    {
      "type": "object",
      "title": "carrier_compliance_exampleArguments",
      "properties": {}
    }
    arguments 5 lines
  • authority_lookup unknown never probed

    Use this when you need to check, before tendering a load or renewing a contract, whether a US motor carrier's operating authority is active and its insurance on file. For 1 to 10 USDOT numbers: authority per docket, BMC-91/34/84 filings, suspension notices and insurance cancellations with effective date and days left, next deadline. For carrier vetting. No personal data. Not a consumer report under the FCRA. Price: 0.01 USDC per call (x402).

    mcp-tool

    {
      "type": "object",
      "required": [
        "usdot"
      ],
      "properties": {
        "usdot": {
          "type": "string",
          "pattern": "^[0-9]{1,8}( *, *[0-9]{1,8}){0,9}$",
          "description": "1 to 10 USDOT numbers, comma-separated"
        }
      }
    }
    arguments 13 lines
  • carrier_compliance_lookup unknown never probed

    Use this when you need a one-call check of a US motor carrier before tendering a load. For 1 to 10 USDOT numbers: operating authority per docket, insurance on file, each suspension notice and insurance cancellation effective date, and the MCS-150 biennial update deadline with the FMCSA's current enforcement, merged into one list of deadlines sorted by date with days left. States and dates only. No personal data. Not a consumer report under the FCRA. Price: 0.012 USDC per call (x402).

    mcp-tool

    {
      "type": "object",
      "required": [
        "usdot"
      ],
      "properties": {
        "usdot": {
          "type": "string",
          "pattern": "^[0-9]{1,8}( *, *[0-9]{1,8}){0,9}$",
          "description": "1 to 10 USDOT numbers, comma-separated"
        }
      }
    }
    arguments 13 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 35f805099d9e0241.

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

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.

_ also on amacunia.fr 8 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.