Skip to main content
Glama

USDOT MCS-150 Biennial Update Deadline Sentinel

Server Details

When is a USDOT number's next MCS-150 biennial update due, and was the last one missed?

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Marcoco27/biennial-update-sentinel-mcp
GitHub Stars
0
Server Listing
Biennial Update Sentinel
ChatGPT
–
Claude
–

TDQS

A3.5/5.0

Scored across 2 tools

Disambiguation4/5

The two tools are mostly distinct: mcs150_example is explicitly a free sample, while mcs150_lookup performs the real lookup. There is minor potential confusion because both return the same shape and share the mcs150 prefix, but the descriptions make the boundary clear.

Naming Consistency4/5

Both names use a consistent mcs150_ prefix and snake_case, making them predictable as a pair. The suffixes differ slightly in style (example as a noun, lookup as an action), but this is a minor deviation.

Tool Count3/5

The server has only two tools, and one is a sample rather than a full operation. This is thin for the stated purpose, though the narrow deadline-checking scope makes it borderline acceptable.

Completeness4/5

The lookup covers the core domain well: deadlines, overdue status, USDOT status, and enforcement details for 1 to 10 carriers. Minor gaps exist, such as no larger batch support, but agents can work around them.

Available Tools

2 tools
mcs150_exampleMCS-150 biennial update deadline: free sampleB
Read-onlyIdempotent
Inspect

Free sample: a real answer for one carrier, same shape as mcs150_lookup.

Inputs: no named parameters. Returns: data, note, rules, licence, +3 more

mcs150_lookupMCS-150 biennial update deadline lookup (USDOT)A
Read-onlyIdempotent
Inspect

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, USDOT status, and deactivation enforcement: the FMCSA suspended it for updates due since 2026-06-01 and is unclear on earlier ones (notice, quote and read date returned). No personal data. Not a consumer report under the FCRA. Price: 0.005 USDC per call (x402). Free trial: set free_trial to true (3 calls per day per caller).

Inputs: usdot (required), free_trial. Returns: data, note, rules, licence, +3 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides keyless access to US FMCSA motor-carrier registry data, enabling lookup of DOT/MC numbers, names, operating authority, and safety information.
      311 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Real-time LTL freight fuel surcharge rates for 9 US carriers and US state ABC liquor license compliance lookups (CA, TX, NY, FL). Every response includes a verifiability block with extraction confidence and source URL so agents can assess data quality before acting.
      6
      33 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI assistants 20 read-only tools that answer safety and regulatory questions — hours-of-service violations, driver qualification files, OSHA recordability and injury rates, 811 dig timing, CSA score explanations, DOT random selections, SDS checks, pipeline MAOP, mariner rest hours, and vessel records — plus full-text lookup of federal regulations from the official eCFR. Every answer is drawn from rule text or government data and cites the governing citation.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.