Skip to content

com.substradium/carrier-records

by substradium.com · remote · no sign-in to list tools · v1.0.1 · published by com.substradium

Dated motor-carrier records with receipts, verification, and specimens, from a records custodian.

Changes · 3
CompareRegistry entry

5 tools: 3 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http carrier-records https://substradium.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 3Claude Code: ask
  • carrier_recordQualify a USDOT number and an as-of date: whether this archive can answer for them, what each source holds for the period, and what a purchased record could establish.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Qualify a USDOT number and an as-of date: whether this archive can answer for them, what each source holds for the period, and what a purchased record could establish. It returns no row of the record. The answer says what the archive holds for the date, never what was true of the carrier. A filing on record is not coverage in force, and a source holding nothing is not a finding about the carrier unless the answer says the absence is provable.
  • carrier_record_by_docketQualify a docket number and an as-of date: whether this archive can answer for them, what each source holds for the period, and what a purchased record could establish.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Qualify a docket number and an as-of date: whether this archive can answer for them, what each source holds for the period, and what a purchased record could establish. It returns no row of the record. The answer says what the archive holds for the date, never what was true of the carrier. A filing on record is not coverage in force, and a source holding nothing is not a finding about the carrier unless the answer says the absence is provable.
  • verifyVerify a Substradium fingerprint.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Verify a Substradium fingerprint. The answer names neither the carrier nor the customer. The answer says what the archive holds for the date, never what was true of the carrier. A filing on record is not coverage in force, and a source holding nothing is not a finding about the carrier unless the answer says the absence is provable.
Only reads 2Claude Code: allow
  • coverageReturn the read surface's coverage, its limits and how the record is bought.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return the read surface's coverage, its limits and how the record is bought.
  • specimenReturn one published specimen.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return one published specimen. A specimen is a sample with the carrier withheld, not an issued record.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http carrier-records https://substradium.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__carrier-records__specimen",
      "mcp__carrier-records__coverage"
    ],
    "ask": [
      "mcp__carrier-records__carrier_record",
      "mcp__carrier-records__carrier_record_by_docket",
      "mcp__carrier-records__verify"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as carrier-records. Review it before you use it.