com.substradium/carrier-records
REMOTE · SUBSTRADIUM.COM
Dated motor-carrier records with receipts, verification, and specimens, from a records custodian.
Available components
Last scanned (7 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 25 Oct 2026.
Category Documents and Files
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 378 tokens (~75/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +50
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- 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. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 −43
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.47 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- 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. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Sept 26 +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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 21 Sept 26 0
- 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 security
- Schema quality: 26 → 75 ▼ functional
- 14 Sept 26 0
- Server version: 1.0.1 → 1.1.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Probed https://substradium.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=substradium.com | CN=WE1,O=Google Trust Services,C=US | 12 Sept 2026 | 11 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 2c616cd07cb7618a13cd2c6d9283f986 |
| SANs: substradium.com, www.substradium.com, *.www.substradium.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of substradium.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| substradium.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://substradium.com/mcp | Verified | 200 | |
| http (plaintext) | http://substradium.com/mcp | HTTPS enforced | 301 | https://substradium.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
carrier_record ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| usdot | string | yes | – |
No output schema declared.
No examples provided.
carrier_record_by_docket ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| docket | string | yes | – |
No output schema declared.
No examples provided.
coverage ~23
Return the read surface's coverage, its limits and how the record is bought.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
specimen ~34
Return one published specimen. A specimen is a sample with the carrier withheld, not an issued record.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
verify ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fingerprint | string | yes | – |
No output schema declared.
No examples provided.
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.
remote · substradium.com
claude mcp add --transport http com-substradium-carrier-records 'https://substradium.com/mcp'
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.