# com.substradium/carrier-records (remote · substradium.com)

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

- Trust score: 73/100 (medium)
- Change this week: +50
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `substradium.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-substradium-carrier-records/substradium.md), [page](https://verifymcp.io/servers/com-substradium-carrier-records/substradium)

## Channel facts

- Endpoint: `https://substradium.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-10-25.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 378 tokens (~75/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 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**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the com.substradium/carrier-records MCP server?

com.substradium/carrier-records is a hosted endpoint at https://substradium.com/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 com-substradium-carrier-records 'https://substradium.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.com-substradium-carrier-records]
url = "https://substradium.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-substradium-carrier-records": {
      "type": "remote",
      "url": "https://substradium.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-substradium-carrier-records --url 'https://substradium.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-substradium-carrier-records:
    url: "https://substradium.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-substradium-carrier-records": {
      "Transport": "http",
      "Url": "https://substradium.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-substradium-carrier-records -t streamable-http -u 'https://substradium.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-substradium-carrier-records": {
      "type": "http",
      "url": "https://substradium.com/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-10-22 (score 73, +50)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Stability: unverified → pass
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100

### 2026-09-28 (score 23, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 23, −43)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.47 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-26 (score 66, +1)

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

### 2026-09-25 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 65, +1)

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

### 2026-09-21 (score 0)

- [security] Tool “carrier_record” rewrote its description, which is the text the model reads
- [security] Tool “carrier_record_by_docket” rewrote its description, which is the text the model reads
- [security] Tool “coverage” rewrote its description, which is the text the model reads
- [security] Tool “specimen” rewrote its description, which is the text the model reads
- [security] Tool “verify” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 26 → 75

### 2026-09-14 (score 0)

- [functional] Server version: 1.0.1 → 1.1.0

## MCP tools (5)

### `carrier_record` (~119 tokens)

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.

Input parameters:

- `as_of` (string, required)
- `usdot` (string, required)

### `carrier_record_by_docket` (~120 tokens)

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.

Input parameters:

- `as_of` (string, required)
- `docket` (string, required)

### `verify` (~82 tokens)

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.

Input parameters:

- `fingerprint` (string, required)

### `specimen` (~34 tokens)

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

Input parameters:

- `name` (string, required)

### `coverage` (~23 tokens)

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-substradium-carrier-records/substradium#diagnostics

## Score history

- 2026-10-25: 73
- 2026-10-24: 73
- 2026-10-23: 73
- 2026-10-22: 73
- 2026-10-21: 23
- 2026-10-20: 23
- 2026-10-19: 23
- 2026-10-18: 23
- 2026-10-17: 23
- 2026-10-16: 23
- 2026-10-15: 23
- 2026-10-14: 23
- 2026-10-13: 23
- 2026-10-12: 23
- 2026-10-10: 23
- 2026-10-07: 23
- 2026-10-05: 23
- 2026-10-04: 23
- 2026-10-03: 23
- 2026-10-02: 23
- 2026-10-01: 23
- 2026-09-30: 23
- 2026-09-29: 23
- 2026-09-28: 23
- 2026-09-27: 23
- 2026-09-26: 66
- 2026-09-25: 65
- 2026-09-24: 65
- 2026-09-23: 64
- 2026-09-22: 64

## Common questions

### What is the com.substradium/carrier-records MCP server?

com.substradium/carrier-records is an MCP server listed in the public MCP registry as com.substradium/carrier-records. Dated motor-carrier records with receipts, verification, and specimens, from a records custodian. This page covers its hosted endpoint (https://substradium.com/mcp).

### Is the com.substradium/carrier-records MCP server safe to use?

com.substradium/carrier-records scores 73 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 com.substradium/carrier-records MCP server expose?

com.substradium/carrier-records exposes 5 tools: carrier_record, carrier_record_by_docket, verify, specimen, coverage. Their descriptions and schemas cost roughly 378 tokens of context every time the server is loaded.

### Does the com.substradium/carrier-records MCP server require authentication?

No. We connected to com.substradium/carrier-records without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the com.substradium/carrier-records MCP server still maintained?

com.substradium/carrier-records is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://substradium.com/mcp
- Website: https://substradium.com/agents/
- Changelog RSS feed: https://verifymcp.io/servers/com-substradium-carrier-records/substradium.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-substradium-carrier-records/substradium.json
- HTML version of this page: https://verifymcp.io/servers/com-substradium-carrier-records/substradium