VERIFYGRID REGISTRY TOOL // VERIFY_CARRIER_FMCSA
FMCSA MC Docket & Broker Bond Verification.
Instant programmatic verification of Motor Carrier (MC) and Freight Forwarder (FF) docket numbers, BMC-84 surety bonds, and active process agent designations.
Live Edge Endpoint & Schema
- REST ENDPOINT
- GET /v1/verify/carrier?dot=4429108&mc=MC-1589204
- MCP TOOL
- verify_carrier_fmcsa
- CREDIT COST
- 2 CREDITS / CALL
- AUTHORITY FEED
- FMCSA L&I Active Broker & Carrier Docket Feed
- SAMPLE INPUT
- MC-1589204
Deterministic JSON Response Fields
mc_numberdot_numberlegal_nameallowed_to_operatebipd_insurance_on_file_usdboc3_on_file
Instant cURL & MCP Execution
# 1. Direct REST Verification
curl -s "https://www.verifygrid.io/v1/verify/carrier?dot=4429108&mc=MC-1589204" \
-H "Authorization: Bearer vg_test_sandbox"
# 2. Streamable HTTP Remote MCP Call
curl -s -X POST "https://www.verifygrid.io/mcp" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "verify_carrier_fmcsa",
"arguments": {}
}
}'
// FAQREGISTRY & INTEGRATION SPECIFICATIONS
Can freight brokers automate carrier onboarding with this endpoint?
Yes. Freight broker TMS systems and AI agents call GET /v1/verify/carrier or MCP tool verify_carrier_fmcsa before dispatching load tenders.