Analytics

carrierscore.io

Provides risk assessment and monitoring services for motor carriers using FMCSA data.

1 endpoint8 known toolsFirst detected August 17, 2026Last detected September 17, 2026

ENDPOINT 1

https://mcp.carrierscore.io/mcp

No auth detected

MCP server metadata

Name: carrierscore-mcp-server
Version: 0.4.0

Capabilities

tools.listChanged

Known tools 8

carrier_lookup

Look up an FMCSA-registered motor carrier's identity by US DOT number: legal name, DBA, operating status, FMCSA safety rating, fleet size (power units, drivers), physical address, and registration dates.

Inferred read-only

carrier_score

Get the CarrierScore risk indices for a carrier by US DOT number: two first-class, separately validated indices (0-100, HIGHER = RISKIER), each with a full component breakdown.

Inferred read-only

montgomery_file

Generate a timestamped Montgomery file — a carrier-selection evidence report — for a carrier by US DOT number.

Inferred read-only

monitor_carriers

Batch risk check for a list of carriers by US DOT number (max 100 per call): score summary and hard flags for each.

Inferred read-only

save_carrier_list

Save a named list of carriers (by US DOT number) for continuous monitoring.

Inferred read-only

list_alerts

Retrieve the alert history for a saved carrier list (see save_carrier_list), newest first.

Inferred read-only

audit_entries

List the immutable audit-archive entries for the caller's API key: every Montgomery evidence report the key generated (text or json), newest first, each with its entry id, generation timestamp, DOT number, scoring date, methodology version and the SHA-256 of the archived report text.

Inferred read-only

verify_evidence

Verify an archived Montgomery evidence report by its audit entry id: CarrierScore re-reads the immutable stored copy, recomputes its SHA-256 and reports whether it matches the hash recorded at generation time (and, optionally, a hash the caller supplies — e.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.carrierscore-mcp-server]
url = "https://mcp.carrierscore.io/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "carrierscore-mcp-server": {
      "type": "http",
      "url": "https://mcp.carrierscore.io/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: carrierscore-mcp-server
Remote MCP URL: https://mcp.carrierscore.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "carrierscore-mcp-server": {
      "url": "https://mcp.carrierscore.io/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "carrierscore-mcp-server": {
      "type": "http",
      "url": "https://mcp.carrierscore.io/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "carrierscore-mcp-server",
  "transport": "streamable-http",
  "url": "https://mcp.carrierscore.io/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for carrierscore.io was fetched 2026-08-21T23:18:01.702Z and is being refreshed.

Trust status Neutral

carrierscore.io is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.