# USDOT Operating Authority and Insurance Status Sentinel (remote · authority.amacunia.fr)

Is this US carrier's authority active, insurance on file, a suspension or an MCS-150 update due?

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `authority.amacunia.fr`: 68/100 (this document), [markdown](https://verifymcp.io/servers/fr-amacunia-usdot-carrier-operating-authority-insurance/authority.md), [page](https://verifymcp.io/servers/fr-amacunia-usdot-carrier-operating-authority-insurance/authority)

## Channel facts

- Endpoint: `https://authority.amacunia.fr/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 481 tokens (~120/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the USDOT Operating Authority and Insurance Status Sentinel MCP server?

USDOT Operating Authority and Insurance Status Sentinel is a hosted endpoint at https://authority.amacunia.fr/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http fr-amacunia-usdot-carrier-operating-authority-in 'https://authority.amacunia.fr/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "fr-amacunia-usdot-carrier-operating-authority-in": {
      "url": "https://authority.amacunia.fr/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fr-amacunia-usdot-carrier-operating-authority-in": {
      "type": "http",
      "url": "https://authority.amacunia.fr/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fr-amacunia-usdot-carrier-operating-authority-in]
url = "https://authority.amacunia.fr/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fr-amacunia-usdot-carrier-operating-authority-in": {
      "type": "remote",
      "url": "https://authority.amacunia.fr/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fr-amacunia-usdot-carrier-operating-authority-in --url 'https://authority.amacunia.fr/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fr-amacunia-usdot-carrier-operating-authority-in:
    url: "https://authority.amacunia.fr/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fr-amacunia-usdot-carrier-operating-authority-in": {
      "Transport": "http",
      "Url": "https://authority.amacunia.fr/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fr-amacunia-usdot-carrier-operating-authority-in -t streamable-http -u 'https://authority.amacunia.fr/mcp'
```

### Other

```json
{
  "mcpServers": {
    "fr-amacunia-usdot-carrier-operating-authority-in": {
      "type": "http",
      "url": "https://authority.amacunia.fr/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 66, 0)

- [security] Tool “carrier_compliance_lookup” rewrote its description, which is the text the model reads
- [security] Tool “authority_lookup” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 103 → 120
- [functional regression] Schema quality: 103 → 119
- [functional] MCP protocol: Implements a current MCP spec version (2026-07-28).
- [functional] MCP protocol version: 2025-11-25 → 2026-07-28
- [functional] Server version: 0.3.0 → 0.3.1
- [functional] Server version: 0.2.0 → 0.3.0
- [functional] Server version: 0.1.1 → 0.2.0
- [cosmetic] “authority_lookup” added an optional parameter “free_trial”

### 2026-11-16 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-15 (score 65)

First indexed and scored.

## MCP tools (4)

### `authority_example` (~26 tokens)

Operating Authority Sentinel: free sample

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

Output parameters:

- `data` (object|null): Datasets read live and the only fields used
- `disclaimer` (string|null): Not legal advice; not affiliated with the FMCSA; not a consumer report
- `licence` (object|null): Licence of the source data: nom, url, source (attribution if required)
- `note` (string|null): How to read found=false, notices, cancellations; which FMCSA record to check before acting
- `results` (array|null): One entry per USDOT number: usdot_number, found, state, as_of, time_zone, time_zone_known, authorities (docket, authority_type, registry_status, last_event, same_day_conflict, registry_vs_history, in…
- `rules` (array|null): Rules applied, with official URL and status

### `carrier_compliance_example` (~30 tokens)

Operating Authority Sentinel: free sample

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

Output parameters:

- `data` (object|null): The six datasets read live and the only fields used
- `disclaimer` (string|null): Not legal advice; not affiliated with the FMCSA; not a consumer report
- `enforcement` (object|null): What the FMCSA says it enforces for the biennial update, quoted
- `licence` (object|null): Licence of the source data: nom, url, source (attribution if required)
- `note` (string|null): How to read both blocks; which FMCSA records to check before acting
- `results` (array|null): One entry per USDOT number: usdot_number; authority (exactly the /v1/authority entry for the number); biennial_update (usdot_status, operation, covered_by_390_19T, as_of, time_zone, filing_month, fil…
- `rules` (array|null): Rules applied by both blocks, with official URL, status and block

### `authority_lookup` (~199 tokens)

Operating Authority Sentinel: authority lookup

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 returned. Not a consumer report under the FCRA. Price: 0.01 USDC per call (x402). Free trial: set free_trial to true (3 calls per day per caller).

Input parameters:

- `free_trial` (boolean): Set to true to ask for the free trial (3 calls per day per caller, shared with the web route, within a daily cap for the service). Without it, the tool asks for an x402 payment.
- `usdot` (string, required): 1 to 10 USDOT numbers, comma-separated

Output parameters:

- `data` (object|null): Datasets read live and the only fields used
- `disclaimer` (string|null): Not legal advice; not affiliated with the FMCSA; not a consumer report
- `licence` (object|null): Licence of the source data: nom, url, source (attribution if required)
- `note` (string|null): How to read found=false, notices, cancellations; which FMCSA record to check before acting
- `results` (array|null): One entry per USDOT number: usdot_number, found, state, as_of, time_zone, time_zone_known, authorities (docket, authority_type, registry_status, last_event, same_day_conflict, registry_vs_history, in…
- `rules` (array|null): Rules applied, with official URL and status

### `carrier_compliance_lookup` (~142 tokens)

Operating Authority Sentinel: carrier compliance lookup

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 returned. Not a consumer report under the FCRA. Price: 0.012 USDC per call (x402).

Input parameters:

- `usdot` (string, required): 1 to 10 USDOT numbers, comma-separated

Output parameters:

- `data` (object|null): The six datasets read live and the only fields used
- `disclaimer` (string|null): Not legal advice; not affiliated with the FMCSA; not a consumer report
- `enforcement` (object|null): What the FMCSA says it enforces for the biennial update, quoted
- `licence` (object|null): Licence of the source data: nom, url, source (attribution if required)
- `note` (string|null): How to read both blocks; which FMCSA records to check before acting
- `results` (array|null): One entry per USDOT number: usdot_number; authority (exactly the /v1/authority entry for the number); biennial_update (usdot_status, operation, covered_by_390_19T, as_of, time_zone, filing_month, fil…
- `rules` (array|null): Rules applied by both blocks, with official URL, status and block

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/fr-amacunia-usdot-carrier-operating-authority-insurance/authority#diagnostics

## Score history

- 2026-11-21: 68
- 2026-11-20: 67
- 2026-11-19: 67
- 2026-11-18: 66
- 2026-11-17: 66
- 2026-11-16: 66
- 2026-11-15: 65

## Common questions

### What is the USDOT Operating Authority and Insurance Status Sentinel MCP server?

USDOT Operating Authority and Insurance Status Sentinel is an MCP server listed in the public MCP registry as fr.amacunia/usdot-carrier-operating-authority-insurance. Is this US carrier's authority active, insurance on file, a suspension or an MCS-150 update due? This page covers its hosted endpoint (https://authority.amacunia.fr/mcp).

### Is the USDOT Operating Authority and Insurance Status Sentinel MCP server safe to use?

USDOT Operating Authority and Insurance Status Sentinel scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the USDOT Operating Authority and Insurance Status Sentinel MCP server expose?

USDOT Operating Authority and Insurance Status Sentinel exposes 4 tools: authority_example, carrier_compliance_example, authority_lookup, carrier_compliance_lookup. Their descriptions and schemas cost roughly 397 tokens of context every time the server is loaded.

### Does the USDOT Operating Authority and Insurance Status Sentinel MCP server require authentication?

No. We connected to USDOT Operating Authority and Insurance Status Sentinel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the USDOT Operating Authority and Insurance Status Sentinel MCP server still maintained?

USDOT Operating Authority and Insurance Status Sentinel is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the USDOT Operating Authority and Insurance Status Sentinel MCP server?

VerifyMCP ran 12 checks on USDOT Operating Authority and Insurance Status Sentinel, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about USDOT Operating Authority and Insurance Status Sentinel: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://authority.amacunia.fr/mcp
- Repository: https://github.com/Marcoco27/operating-authority-sentinel-mcp
- Website: https://authority.amacunia.fr/
- Changelog RSS feed: https://verifymcp.io/servers/fr-amacunia-usdot-carrier-operating-authority-insurance/authority.xml
- Changelog JSON feed: https://verifymcp.io/servers/fr-amacunia-usdot-carrier-operating-authority-insurance/authority/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/fr-amacunia-usdot-carrier-operating-authority-insurance/authority.json
- HTML version of this page: https://verifymcp.io/servers/fr-amacunia-usdot-carrier-operating-authority-insurance/authority
