Substradium Carrier Records MCP

An MCP server providing tools to query dated motor-carrier records, verify data integrity, and check archive coverage. It allows agents to qualify carriers for specific dates, retrieve specimen records, and access order URLs for certified Point-in-Time reports, serving as a bridge to Substradium's archival data services.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by Substradium Inc.

MCP endpoint (Streamable HTTP)

https://substradium.com/mcp

Vendor documentation

What its tools do

5 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (5)

carrier_record
carrier_record_by_docket
verify
specimen
coverage

5 of 5 have a description · 0 of 5 declare behavior hints · 0 of 4 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 6, 2026, 2:34 PM UTC
Passed Official MCP Registry namespace is tied to substradium.com · Nov 6, 2026, 1:58 PM UTC
Passed Endpoint is on the registry namespace domain · Nov 6, 2026, 1:58 PM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Qualify a carrier and date to check archive coverage
Retrieve a specimen record to verify data format
Verify record hashes for data integrity
Access order URLs for certified carrier reports

Source and maintenance

Vendor evidenceRegistry 1.0.1

mcp-registry: com.substradium/carrier-records@1.0.1 Project website

Protocol and capabilities

Server: substradium 1.1.0
MCP protocol negotiated in check: 2025-06-18
Tools: 5 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {}
}

Tools

5 advertised

carrier_record

Advertised by the server during the last successful anonymous check.

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 input schema

{
  "type": "object",
  "title": "carrier_recordArguments",
  "required": [
    "usdot",
    "as_of"
  ],
  "properties": {
    "as_of": {
      "type": "string",
      "title": "As Of"
    },
    "usdot": {
      "type": "string",
      "title": "Usdot"
    }
  }
}

carrier_record_by_docket

Advertised by the server during the last successful anonymous check.

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.

carrier_record_by_docket input schema

{
  "type": "object",
  "title": "carrier_record_by_docketArguments",
  "required": [
    "docket",
    "as_of"
  ],
  "properties": {
    "as_of": {
      "type": "string",
      "title": "As Of"
    },
    "docket": {
      "type": "string",
      "title": "Docket"
    }
  }
}

verify

Advertised by the server during the last successful anonymous check.

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.

verify input schema

{
  "type": "object",
  "title": "verifyArguments",
  "required": [
    "fingerprint"
  ],
  "properties": {
    "fingerprint": {
      "type": "string",
      "title": "Fingerprint"
    }
  }
}

specimen

Advertised by the server during the last successful anonymous check.

Return one published specimen. A specimen is a sample with the carrier withheld, not an issued record.

specimen input schema

{
  "type": "object",
  "title": "specimenArguments",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "title": "Name"
    }
  }
}

coverage

Advertised by the server during the last successful anonymous check.

Return the read surface's coverage, its limits and how the record is bought.

coverage input schema

{
  "type": "object",
  "title": "coverageArguments",
  "properties": {}
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (5 of 5 answered).

2026-11-06: 1 of 1 checks answered
2026-11-07: 2 of 2 checks answered
2026-11-09: 1 of 1 checks answered
2026-11-10: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 681 ms
95th percentile latency: 681 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 6, 2026, 2:34 PM UTC · probe · passed · 681 ms · metadata changed · 5 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

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

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add substradium-carrier-records-mcp --url https://substradium.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable substradium-carrier-records-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "substradium-carrier-records-mcp": {
      "url": "https://substradium.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "substradium-carrier-records-mcp": {
      "type": "streamableHttp",
      "url": "https://substradium.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start substradium-carrier-records-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "substradium-carrier-records-mcp": {
      "type": "http",
      "url": "https://substradium.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

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

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://substradium.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "substradium-carrier-records-mcp": {
      "serverUrl": "https://substradium.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Substradium Carrier Records MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

Do you run Substradium Carrier Records MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing