US motor carrier MCS-150 biennial update: next deadline, overdue flag, USDOT status.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Free sample: a real answer for one carrier, same shape as mcs150_lookup.
This tool takes no arguments.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http biennial-update-sentinel https://mcs150.amacunia.fr/mcp
Free sample: a real answer for one carrier, same shape as mcs150_lookup.
No arguments.
{
"type": "object",
"title": "mcs150_exampleArguments",
"properties": {}
}Use this when you need to know whether a US motor carrier's biennial MCS-150 update is due or overdue. For 1 to 10 USDOT numbers: next and last filing deadline (49 CFR 390.19T), days left in the carrier's state time zone, overdue flag, deactivation exposure, USDOT status. No personal data. Not a consumer report under the FCRA. Price: 0.005 USDC per call (x402).
| Argument | Type | Description |
|---|---|---|
| usdot* | string |
{
"type": "object",
"title": "mcs150_lookupArguments",
"required": [
"usdot"
],
"properties": {
"usdot": {
"type": "string",
"title": "Usdot"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 10, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.