Carrier Ledger MCP server
dev.workers.neoaethel.carrier-ledger/carrier-ledgercarrier-ledger.neoaethel.workers.devstreamable-httpv1.3.1Scanned
Check U.S. trucking carriers and freight brokers in FMCSA records: authority, insurance, notices.
3 tools: 3 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Carrier Ledger MCP server can do
The Carrier Ledger MCP server is published by carrier-ledger.neoaethel.workers.dev, a domain the MCP Registry verified. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
3 tools bring in text other people can write (lookup_carrier, check_carrier_list and recent_suspension_notices).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 1.3.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Only reads 3Show 3 read-only tools
check_carrier_listChecks up to 25 U.S.Reads text others writeNo findings
Why it is in this group
- The name "check_carrier_list" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Checks up to 25 U.S. carriers or brokers at once (USDOT numbers; MC numbers also accepted, up to 10) and returns each one's most important red flag from FMCSA public records, urgent ones first. Use to screen a carrier list or a load board shortlist.
Annotations the server declares
- title: Check a list of carriers
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
lookup_carrierLooks up a U.S.Reads text others writeNo findings
Why it is in this group
- The name "lookup_carrier" says "lookup": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Looks up a U.S. motor carrier or freight broker in FMCSA public records by USDOT number or MC number. Returns its operating authority, liability insurance and bond on file, suspension or revocation notices, and plain-English red flags, each citing the FMCSA dataset it came from. Use before booking or paying a carrier or broker. Not a rating or a vetting decision.
Annotations the server declares
- title: Check a trucking company or freight broker
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
recent_suspension_noticesLists carriers and brokers FMCSA recently served an involuntary suspension notice (usually because insurance was cancelled), with the date each suspension takes effect.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Lists carriers and brokers FMCSA recently served an involuntary suspension notice (usually because insurance was cancelled), with the date each suspension takes effect. Until that date FMCSA still shows the company as "Active".
Annotations the server declares
- title: Recent FMCSA suspension notices
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:53 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.3.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http carrier-ledger https://carrierledger.steellantern.com/mcpclaude mcp add --transport http carrier-ledger https://carrierledger.steellantern.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__carrier-ledger__lookup_carrier",
"mcp__carrier-ledger__check_carrier_list",
"mcp__carrier-ledger__recent_suspension_notices"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as carrier-ledger. Review it before you use it.
Capability tags behind 3 rules
- mcp__carrier-ledger__lookup_carrier untrusted-input
- mcp__carrier-ledger__check_carrier_list untrusted-input
- mcp__carrier-ledger__recent_suspension_notices untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.workers.neoaethel.carrier-ledger/carrier-ledger/verify?hash=d808519be73abb06fe0f810309c46da581a75acf848b933e5ef8ed0fe5de5519" | jq -e '.changed == false'Pinned hash d808519be73a, from Nov 13, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.workers.neoaethel.carrier-ledger/carrier-ledger/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.workers.neoaethel.carrier-ledger/carrier-ledger)Source: MCP Registry · repository. Synced Oct 31, 2026, 05:17 UTC.
Carrier Ledger MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Carrier Ledger MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Carrier Ledger MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Carrier Ledger MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Carrier Ledger MCP server have?
- 3 tools: 3 read. lookup_carrier, check_carrier_list and recent_suspension_notices.
Does the Carrier Ledger MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Carrier Ledger MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Carrier Ledger MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.