{"name":"io.carrierscore/carrierscore","slug":"carrierscore","title":null,"description":"FMCSA motor-carrier risk scores, monitoring, and carrier-selection evidence reports for AI agents.","url":"https://mcp.market/server/carrierscore","rating":null,"grade":"B","score":80,"certified":false,"status":"active","category":"other","tags":[],"presence":{"score":18,"stars":0,"forks":0,"downloads_week":null,"last_push_at":"2026-08-16T19:55:36.000Z","license":"MIT"},"uptime":{"percent":96,"checks":28,"ok":27,"last_checked_at":"2026-11-04T05:05:47.240Z","last_ok_at":"2026-11-04T05:05:47.240Z","latency_ms":542},"claimed":false,"transport":"remote","callable_via_gateway":true,"default_price_micros":0,"repository":"https://github.com/csprout3/carrierscore-mcp","website":"https://carrierscore.io","version":"0.1.0","remotes":[{"type":"streamable-http","url":"https://mcp.carrierscore.io/mcp"}],"packages":[],"tools":[{"name":"audit_entries","description":"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. Requires a paid CarrierScore API key.\n\nUse it to answer \"which carriers did we generate evidence for, and when?\" and to find the entry id to cite or verify for a given carrier and date. Monitor keys see the last 90 days; Compliance keys see everything ever archived.\n\nArgs:\n  - dot_number (optional): only entries for this US DOT number\n  - since (optional): YYYY-MM-DD; only entries generated on/after this date (UTC)\n  - limit (optional): 1-500, default 50\n\nReturns JSON: { tier, retention_days, total_entries, matched, count, entries: [{ entry_id, generated_at, dot_number, sha256, format_requested, scored_as_of, score_version }] }.\n\nErrors: 403 without a paid key; 400 if since is malformed.","write_action":false,"price_micros":0,"input_schema":{"type":"object","properties":{"dot_number":{"type":"string","pattern":"^\\d{1,8}$","description":"US DOT number of the carrier, digits only (e.g. \"1234567\")"},"since":{"type":"string","pattern":"^\\d{4}-\\d{2}-\\d{2}$","description":"Only entries generated on/after this date (YYYY-MM-DD, UTC)"},"limit":{"type":"integer","minimum":1,"maximum":500,"description":"Max entries to return (default 50)"}},"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"}},{"name":"carrier_lookup","description":"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.\n\nUse this first when a booking/dispatch agent needs to confirm WHO a carrier is — that a DOT number is real, active, and matches the company name on a rate confirmation. It does not return risk indices (use carrier_score for those).\n\nReturns JSON: { dot_number, legal_name, dba_name, status_code, safety_rating, power_units, total_drivers, phy_street, phy_city, phy_state, phy_zip, add_date, mcs150_date }.\n\nErrors: 404 if the DOT is not in the FMCSA census (likely a typo or a fraudulent/never-registered carrier — treat as a red flag for booking).","write_action":false,"price_micros":0,"input_schema":{"type":"object","properties":{"dot_number":{"type":"string","pattern":"^\\d{1,8}$","description":"US DOT number of the carrier, digits only (e.g. \"1234567\")"}},"required":["dot_number"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"}},{"name":"carrier_score","description":"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.\n\nThis is the core \"is this carrier safe to book?\" signal for AI booking agents. Served methodology v0.5 returns TWO indices, both population-relative and built from point-in-time public FMCSA data:\n  - inspection_risk — inspection / compliance risk: violations and out-of-service rates per roadside inspection (24-month chronic, 6-month acute). Historically validated against the carrier's future out-of-service rate (validation block on the index).\n  - crash_risk — crash risk: reportable crashes, fatal/injury crashes and tow-away crashes per roadside inspection (24 months). Historically validated against future reportable crashes (validation block on the index).\nPresent BOTH indices; do not collapse them into one number. Hard flags (active out-of-service order, no active insurance filing, high-confidence reincarnated-carrier link) add explicit surcharges — a carrier with any flag deserves extra scrutiny regardless of index values.\n\nReturns JSON: { dot_number, legal_name, inspection_risk: { label, description, score, base, surcharge, percentile_basis, band, band_note, data_sufficiency, components: { <name>: { label, value, percentile, weight } }, validation: { auc_holdout, label, holdout_origins, post_selection_origin, source, text } }, crash_risk: { ...same shape... }, legacy_composite: { score, base_score, surcharge, rule, rule_text, validated: false, note }, carrier_score (backward-compatible: == legacy_composite.score under v0.5), base_score, surcharge, score_version (\"0.5\"), methodology_note, components (flat, backward-compatible), flags: string[], data_sufficiency (0-1, share of the components resting on observed vs neutral-imputed data), scored_as_of, disclaimer }. Older opt-in methodologies keep their shapes: v0 (six components), v0.3 (sub_indices), v0.4 (indices + composite).\n\nInterpreting for booking decisions: treat the indices as documented decision-support evidence, not an approve/deny verdict. legacy_composite / carrier_score is NOT validated and is kept only so older integrations keep working — never present it as the carrier's risk score. Low data_sufficiency means limited inspection history — common for new carriers, itself a risk signal. Always relay each index's validation text and the disclaimer when presenting the result.\n\nErrors: 404 if the DOT is not in the scored population; 503 if scores have not been computed yet.","write_action":false,"price_micros":0,"input_schema":{"type":"object","properties":{"dot_number":{"type":"string","pattern":"^\\d{1,8}$","description":"US DOT number of the carrier, digits only (e.g. \"1234567\")"}},"required":["dot_number"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"}},{"name":"list_alerts","description":"Retrieve the alert history for a saved carrier list (see save_carrier_list), newest first. Requires the same paid API key that saved the list.\n\nEach alert records one change detected between consecutive daily scoring runs for one carrier: type (oos_order_activated, authority_lost, insurance_lapsed, status_changed, inspection_risk_jump, crash_risk_jump, score_jump, reincarnation_link), severity (critical / high / medium / low), the field that changed with its before/after values, the DOT and legal name, and the scoring dates compared. inspection_risk_jump / crash_risk_jump (index base up >= 10 points, medium) are the primary deterioration signals; score_jump on the legacy composite is emitted at low severity for backward compatibility. Use it to answer \"did anything change on my carrier list?\" — critical alerts (new OOS order, authority lost) mean the carrier should not be dispatched until verified; follow up with carrier_score or montgomery_file for the full picture.\n\nArgs:\n  - list_id: the lst_... id returned by save_carrier_list\n  - since (optional): YYYY-MM-DD; only alerts from scoring runs on/after this date\n\nReturns JSON: { list_id, since, count, alerts: [{ ts, as_of, prev_as_of, list_id, list_name, dot, legal_name, type, severity, field, before, after }] }. An empty alerts array means no monitored change since the given date (alerts only exist once two daily scoring runs have happened).\n\nErrors: 403 without a paid key; 404 if the list id is unknown for this key; 400 if since is not YYYY-MM-DD.","write_action":false,"price_micros":0,"input_schema":{"type":"object","properties":{"list_id":{"type":"string","pattern":"^lst_[A-Za-z0-9_-]+$","description":"Saved list id from save_carrier_list"},"since":{"type":"string","pattern":"^\\d{4}-\\d{2}-\\d{2}$","description":"Only alerts from scoring runs on/after this date (YYYY-MM-DD)"}},"required":["list_id"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"}},{"name":"monitor_carriers","description":"Batch risk check for a list of carriers by US DOT number (max 100 per call): score summary and hard flags for each.\n\nUse when an agent is screening multiple candidate carriers for a load, or re-checking a broker's active carrier roster (\"did any of my carriers pick up an out-of-service order or drop insurance?\"). For a full breakdown of any single carrier that looks risky here, follow up with carrier_score or montgomery_file.\n\nArgs:\n  - dot_numbers: array of DOT number strings, 1-100 entries\n\nReturns JSON: { scored_as_of, requested, found, carriers: [{ dot_number, legal_name, inspection_risk (0-100 inspection / compliance risk index, higher = riskier), crash_risk (0-100 crash risk index), carrier_score (legacy composite under v0.5 — backward compatibility only; use the two indices), data_sufficiency, flags: string[] }], not_found: string[], disclaimer }. DOTs in not_found are absent from the scored population — verify them with carrier_lookup; an unknown DOT on your roster is itself a red flag.\n\nErrors: 400 if the list is empty or exceeds 100 (split into batches); 503 if scores are not computed yet.","write_action":false,"price_micros":0,"input_schema":{"type":"object","properties":{"dot_numbers":{"type":"array","items":{"type":"string","pattern":"^\\d{1,8}$","description":"US DOT number of the carrier, digits only (e.g. \"1234567\")"},"minItems":1,"maxItems":100,"description":"US DOT numbers to check, 1-100 per call"}},"required":["dot_numbers"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"}},{"name":"montgomery_file","description":"Generate a timestamped Montgomery file — a carrier-selection evidence report — for a carrier by US DOT number.\n\nSince Montgomery v. Caribe Transport II (SCOTUS, May 2026), freight brokers are exposed to state-law negligent-selection claims and need documented, timestamped, safety-data-based carrier selection. This report is that artifact: the two risk indices (inspection / compliance risk and crash risk, each with its components, percentiles, activity-band context and its own historical-validation line), the legacy composite (labelled backward-compatibility only), hard flags, FMCSA safety rating, and the methodology disclaimer, dated as of the scoring run. A booking agent should generate and retain this file at the moment a carrier is selected for a load.\n\nArgs:\n  - dot_number: US DOT number, digits only\n  - format: \"text\" (default; the filing-ready plain-text report, available on the free tier) or \"json\" (structured fields; requires an API key on the monitor or compliance tier)\n\nReturns: format=\"text\" gives the plain-text report (structured field report_text); format=\"json\" gives structured fields { report, generated, dot_number, legal_name, dba_name, safety_rating, status_code, power_units, inspection_risk, crash_risk, legacy_composite (v0.5), carrier_score (backward-compatible), components, flags, data_sufficiency, score_version, scored_as_of, disclaimer } (v0.4 parquets return indices + composite instead). Every report embeds the disclaimer verbatim — keep it when storing or quoting the report.\n\nAudit archive (paid tiers): every report generated with an API key is stored immutably server-side and the result carries audit_entry_id + sha256 (SHA-256 of the plain-text report). Quote both when citing the report; later, verify_evidence(entry_id) proves the archived copy is unchanged and audit_entries lists what was generated. Monitor keys can retrieve the last 90 days (2,000 reports/month); Compliance keys have unlimited retention and reports.\n\nErrors: 403 if format=json without an API key; 404 unknown DOT; 429 if a Monitor key has used its 2,000 reports this month (upgrade hint in the message); 503 if scores are not computed yet.","write_action":false,"price_micros":0,"input_schema":{"type":"object","properties":{"dot_number":{"type":"string","pattern":"^\\d{1,8}$","description":"US DOT number of the carrier, digits only (e.g. \"1234567\")"},"format":{"type":"string","enum":["text","json"],"default":"text","description":"\"text\" = filing-ready report (free tier); \"json\" = structured fields (requires API key)"}},"required":["dot_number"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"}},{"name":"save_carrier_list","description":"Save a named list of carriers (by US DOT number) for continuous monitoring. Requires a paid CarrierScore API key (Monitor or Compliance tier) — connect with your key via OAuth (or set CARRIERSCORE_API_KEY on a self-hosted server); the free tier gets a 403 with an upgrade link.\n\nOnce saved, CarrierScore diffs every carrier on the list against the previous day's scoring run after each daily run and records alerts: new out-of-service order (critical), operating authority lost (critical), insurance filing lapsed (high), operating status leaving Active (high), risk score up 10+ points (medium), high-confidence reincarnated-carrier link appearing (medium). Alerts are always retrievable with list_alerts; optionally they are also pushed to a webhook (JSON POST, HMAC-signed via the X-CarrierScore-Signature header with the per-key secret from GET /v1/lists) and/or summarized in one daily digest email.\n\nUse this when a broker asks to \"watch\" or \"keep an eye on\" their carrier roster. Caps: 500 DOTs total across all lists on the Monitor tier, 5000 on Compliance; up to 50 lists per key. Saving the same DOT twice in one list is deduped.\n\nArgs:\n  - name: short label for the list (1-100 chars)\n  - dot_numbers: array of DOT number strings (1-8 digits each)\n  - webhook_url (optional): https URL to POST new alerts to\n  - email (optional): address for the daily digest\n\nReturns JSON: { list_id, name, dots, created, updated, webhook_url?, email? }. Keep list_id — list_alerts needs it.\n\nErrors: 403 without a paid key; 400 on invalid DOTs, empty list, or exceeding the tier cap (message says which); 401 bad key.","write_action":false,"price_micros":0,"input_schema":{"type":"object","properties":{"name":{"type":"string","minLength":1,"maxLength":100,"description":"List name, e.g. \"Active roster Q3\""},"dot_numbers":{"type":"array","items":{"type":"string","pattern":"^\\d{1,8}$","description":"US DOT number of the carrier, digits only (e.g. \"1234567\")"},"minItems":1,"maxItems":5000,"description":"US DOT numbers to monitor"},"webhook_url":{"type":"string","format":"uri","description":"Optional https URL to receive alert POSTs"},"email":{"type":"string","format":"email","description":"Optional daily digest email"}},"required":["name","dot_numbers"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"}},{"name":"verify_evidence","description":"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.g. the sha256 printed on a broker's filed copy). Requires the same paid API key that generated the report.\n\nUse it when a broker or auditor needs to prove that a filed evidence report is exactly what CarrierScore produced on the stated date. match=true means the archived report is byte-identical to what was served; match_supplied compares against the caller's own hash. Follow up with the audit_entries list to find ids, or with montgomery_file to generate a fresh report.\n\nArgs:\n  - entry_id: the audit_entry_id returned by montgomery_file (also listed by audit_entries)\n  - sha256 (optional): a 64-hex SHA-256 to compare against the archived report (text or canonical json)\n\nReturns JSON: { entry_id, dot_number, generated_at, scored_as_of, score_version, format_requested, sha256_stored, sha256_computed, match, sha256_json_stored, sha256_json_computed, match_json, sha256_supplied?, match_supplied? }.\n\nErrors: 403 without a paid key, or (Monitor tier) if the entry is older than the 90-day retrieval window; 404 if the entry id is unknown for this key.","write_action":false,"price_micros":0,"input_schema":{"type":"object","properties":{"entry_id":{"type":"string","pattern":"^\\d{1,8}_\\d{8}T\\d{12}Z_[0-9a-f]{8}$","description":"Audit entry id from montgomery_file / audit_entries"},"sha256":{"type":"string","pattern":"^[0-9a-fA-F]{64}$","description":"Optional SHA-256 to compare against the archived report"}},"required":["entry_id"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"}}],"scan":{"score":80,"grade":"B","scanned_at":"2026-10-14T17:38:30.214Z","report":{"scannerVersion":"0.1.10","scannedAt":"2026-10-14T17:38:30.167Z","components":{"code":{"score":-1,"max":25,"notes":["remote-only server, no package to scan"]},"reliability":{"score":17,"max":20,"notes":["remote reachable in 2542ms"]},"poisoning":{"score":13,"max":15,"notes":["8 tool descriptions checked"]},"auth":{"score":10,"max":15,"notes":["open endpoint, read-only tools"]},"maintenance":{"score":12,"max":15,"notes":["last push 59 days ago"]},"identity":{"score":8,"max":10,"notes":["endpoint served from the registry-verified namespace domain"]}},"findings":[{"id":"poison.long-description","severity":"low","component":"poisoning","title":"Unusually long tool description (over 2,000 characters)","evidence":"tool 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. This is the core \"is this carrier safe to book?\" signal for AI booking agents. Served methodology v0.5 returns TWO indices, both population-relative and built from point-in-time public FMCSA data: - inspection_risk — inspection / compliance risk: violations and out-of-service rates per roadside inspection (24-month chronic, 6-month acute). Historically validated against the carrier's future out-of-service rate (validation block on the index). - crash_risk — crash risk: reportable crashes, fatal/injury crashes and tow-away crashes per roadside inspection (24 months). Historically validated against future reportable crashes (validation block on the index). Present BOTH indices; do not collapse them into one number. Hard flags (active out-of-service order, no active insurance filing, high-confidence reincarnated-carrier link) add explicit surcharges — a carrier with any flag deserves extra scrutiny regardless of index values. Returns JSON: { dot_number, legal_name, inspection_risk: { label, description, score, base, surcharge, percentile_basis, band, band_note, data_sufficiency, components: { <name>: { label, value, percentile, weight } }, validation: { auc_holdout, label, holdout_origins, post_selection_origin, source, text } }, crash_risk: { ...same shape... }, legacy_composite: { score, base_score, surcharge, rule, rule_text, validated: false, note }, carrier_score (backward-compatible: == legacy_composite.score under v0.5), base_score, surcharge, score_version (\"0.5\"), methodology_note, components (flat, backward-compatible), flags: string[], data_sufficiency (0-1, share of the components resting on observed vs neutral-imputed data), scored_as_of, disclaimer }. Older opt-in methodologies keep their shapes: v0 (six components), v0.3 (sub_indices), v0.4 (indices + composite). Interpreting for booking decisions: treat the indices as documented decision-support evidence, not an approve/deny verdict. legacy_composite / carrier_score is NOT validated and is kept only so older integrations keep working — never present it as the carrier's risk score. Low data_sufficiency means limited inspection history — common for new carriers, itself a risk signal. Always relay each index's validation text and the disclaimer when presenting the result. Errors: 404 if the DOT is not in the scored population; 503 if scores have not been computed yet.…"}],"inputs":{"probes":[{"url":"https://mcp.carrierscore.io/mcp","reachable":true,"authRequired":false,"latencyMs":2542,"serverInfo":{"name":"carrierscore-mcp-server","version":"0.4.0"}}],"packages":[],"repo":{"found":true,"owner":"csprout3","repo":"carrierscore-mcp","archived":false,"pushedAt":"2026-08-16T19:55:36Z","stars":0,"forks":0,"openIssues":0,"ownerType":"User","ownerAvatarUrl":"https://avatars.githubusercontent.com/u/99996415?v=4","ownerCreatedAt":"2022-02-18T20:25:11Z","license":"MIT"},"icon":{"url":"https://carrierscore.io/icon-512.png","source":"registry","width":512,"height":512},"presence":{"stars":0,"forks":0,"downloadsWeek":null,"license":"MIT","lastPushAt":"2026-08-16T19:55:36.000Z","score":18}}}},"grade_history":[],"reviews":[]}