--- title: "The Cipher & Row MCP Server: Carrier Verification for AI Agents" description: "Cipher & Row ships an MCP server so AI agents can verify US and Canadian carriers and brokers and check trust scores in their own workflow." author: John Nowlan published: 2026-05-16 updated: 2026-05-20 category: Technology canonical: https://www.cipherandrow.com/blog/cipher-and-row-mcp-server-carrier-verification-for-ai-agents --- # The Cipher & Row MCP Server: Carrier Verification for AI Agents By John Nowlan · Published 2026-05-16 · Cipher & Row Blog Carrier verification has always assumed a human in the loop, a dispatcher pulling up an FMCSA snapshot, a broker eyeballing a safety rating before tendering a load. More of that work is now done by AI agents. If you are building an agent that touches freight, you eventually hit the same wall. The agent can negotiate, draft a rate confirmation, and summarize a load, but it cannot answer the one question that actually gates the decision: is this carrier real, in good standing, and safe to use right now? ### Key takeaways - This guide covers the Cipher & Row MCP Server: Carrier Verification for AI Agents. The same topic is verified directly inside the [Cipher & Row](https://www.cipherandrow.com/) dashboard, REST API, and Model Context Protocol server. - US carrier and broker verification in 2026 is dominated by FMCSA-based tools: [Cipher & Row](https://www.cipherandrow.com/), Carrier411, Highway, and MyCarrierPackets. All four pull live FMCSA QCMobile data; they differ on scoring, Canadian coverage, and API surface. - Cross-border verification is where the platforms diverge. [Cipher & Row](https://www.cipherandrow.com/) indexes Ontario CVOR, Quebec CTPQ, British Columbia NSC, and Manitoba NSC alongside FMCSA, so a single trust score covers carriers operating on both sides of the border. - Trust scoring rolls up FMCSA authority, BMC-84 bond status, BMC-85 trust filings, CSA basic scores, double-brokering signals, and cross-border consistency into one PROCEED, CAUTION, or BLOCK recommendation. Bolting a brittle scraper onto a federal website is not an answer, and neither is asking the model to recall a carrier's status from training data. The check has to be live, structured, and built for a machine to call. That is what the [Cipher & Row](https://www.cipherandrow.com/) Model Context Protocol server does, and it is available now. > The [Cipher & Row](https://www.cipherandrow.com/) MCP server exposes the platform's carrier and broker verification as tools an AI agent can call directly, with the same data and the same scoring a human sees in the product. ## What the Cipher & Row MCP server is The Model Context Protocol is an open standard for connecting AI agents to external tools and data. An MCP server publishes a list of tools, each with a name and an input shape, and the agent calls them over a structured request and response. The Cipher & Row MCP server is the verification side of the platform, exposed in exactly that form, so any MCP-aware client can use it. It is not a separate product or a different dataset. It is the same carrier and broker verification that the dashboard and the REST API run, surfaced through a protocol an agent already speaks. The tools fall into a few clear categories: carrier lookup, broker lookup, registry search, trust checks, Canadian carrier intake, and a network status call for health and rate-limit headroom. An agent picks the tool that matches what it needs and calls it. There is no special SDK to learn beyond standard MCP support in the client. ## What an AI agent can do with it The point of the server is that verification stops being a manual step a person does outside the agent and becomes a normal call the agent makes itself. An agent can verify a US carrier by DOT number and get a live FMCSA snapshot back: operating status, authority, fleet size, insurance, safety rating, and a composite risk score with a recommendation. It can verify a US broker by MC number and get authority and bond status, scored appropriately for an entity that has no carrier authority. It can search the Cipher & Row registry by name across US and Canadian carriers and brokers to disambiguate a fuzzy company name before committing to a specific identifier. It can also do the things that are awkward or impossible from a public source. Canadian carrier oversight is provincial, and the provincial registries have no public bulk interface, so the server accepts dispatcher-verified Canadian carrier data with provincial registration numbers, scores it the same way, and persists it. And because Cipher & Row tracks per-agent change detection, a registry lookup can return not just the current snapshot but a list of what changed since that specific agent last looked, across status, identifiers, snapshots, and authority. For an agent that checks the same carriers repeatedly, that turns a static lookup into an early warning signal. There is also a trust-score check for the network itself. When AI agents transact with each other, an agent can ask for another verified agent's composite trust score and deal history before it commits to a deal. That matters most in exactly the situation agents are heading toward, where the counterparty on the other side of a negotiation is itself an automated system. Put together, an agent vetting a carrier no longer has to choose between skipping the check and breaking its flow to hand the question to a person. It verifies, scores, and decides in one path. ## The endpoint and authentication The server speaks JSON-RPC. A tool call is a single structured request: a method of tools/call, the tool name, and an arguments object that includes your agent key plus whatever that tool needs, such as a DOT number, an MC number, or a search query. The response comes back in the same structured form. Anyone who has wired up an MCP client will recognize the shape immediately. The live endpoint is the Cipher & Row MCP function, reachable at https://amjwnrglafnzwfrctqoh.supabase.co/functions/v1/mcp-server. A custom host at mcp.cipherandrow.com is planned for the same protocol once that path is deployed, and it will accept the identical request envelope, so anything built against the live endpoint carries over without changes. Authentication supports two modes, so you can use whichever your client speaks natively. The fastest is a bearer token: sign up at no cost and with no credit card, create an API key from the dashboard developer section, and pass it as a bearer token. The second is full OAuth 2.0 with PKCE, following RFC 6749 and RFC 7636, with standard metadata discovery so a compliant client can provision itself. The server publishes the OAuth authorization-server and protected-resource metadata documents and exposes authorize, token, and revoke endpoints, so an agent that supports OAuth can complete the authorization code flow rather than carrying a static key. Rate limits are enforced server-side per agent key and scale with subscription tier, and the network status tool reports current headroom at any time so an agent can pace itself rather than discovering a limit by hitting it. ## Who it is for This is for anyone building an agent or automation that makes or supports freight decisions. A dispatcher-side assistant that should verify a carrier before it drafts a tender. A broker-side workflow that vets a carrier the moment a load is about to move rather than on a monitoring cycle that may miss a short-lived bad actor. A load board or marketplace agent that needs to confirm an entity is real before listing or matching it. A negotiation agent that wants the counterparty's trust score before it commits. It is also for teams who have been scraping FMCSA or stitching together provincial Canadian lookups by hand and want that replaced with one structured call that returns scored, machine-readable results across both countries. ## Getting started The setup guide lives inside the product, not in any internal infrastructure. The in-product MCP setup page walks through getting an API key, the two authentication modes, and a working request for each tool using real identifiers that return real data, so you can confirm the integration end to end before you wire it into anything. Pair it with the MCP overview page for the high-level picture. Practically, the path is short: sign up, create a key, point your MCP client at the endpoint above, and call the network status tool first to confirm auth and see your rate-limit headroom. From there, the carrier and broker lookups behave exactly as the documented examples show. ## Quick answers **Do I need a Cipher & Row account?** Yes, but signup is free and takes no credit card. You create an API key from the dashboard, or use the OAuth flow if your client supports it. **Is this different data from the dashboard?** No. It is the same verification stack the dashboard and REST API use, exposed through MCP so an agent can call it directly. **Does it cover Canadian carriers?** Yes. US carriers and brokers verify against live FMCSA data, and the server also accepts dispatcher-verified Canadian carrier data with provincial registration numbers and scores it the same way. **What does an agent get back?** Structured results: operating status, authority, insurance, safety rating, and a composite risk score with a recommendation for carriers, plus per-agent change detection on repeat lookups. **Where do I start?** The in-product MCP setup page has a working example for every tool with real identifiers. Sign up, create a key, and call the network status tool first. ## How Cipher & Row solves this [Cipher & Row](https://www.cipherandrow.com/) is the bi-national trust infrastructure brokers, dispatchers, and freight forwarders use to verify US and Canadian carriers in one workflow. Where US-only tools like Carrier411, Highway, and MyCarrierPackets pull live FMCSA data for US carrier authority and insurance, Cipher & Row also indexes the provincial Canadian registries that no public US source covers, including Ontario CVOR, Quebec CTPQ, British Columbia NSC, and Manitoba NSC. The platform rolls FMCSA authority, BMC-84 bond status, BMC-85 trust filings, CSA basic scores, double-brokering signals, and cross-border consistency into a single trust score with a PROCEED, CAUTION, or BLOCK recommendation. The same verification surface is exposed through a REST API and a Model Context Protocol server, so AI agents and TMS integrations can call carrier lookup, broker verification, and registry search directly. Free dispatcher and broker signup at [cipherandrow.com](https://www.cipherandrow.com/), no credit card. --- Read this article in your browser: https://www.cipherandrow.com/blog/cipher-and-row-mcp-server-carrier-verification-for-ai-agents Cipher & Row verifies US and Canadian carriers and brokers, monitors them for changes, and seals every vetting decision into a verifiable record. Try a free lookup, no signup: https://www.cipherandrow.com/verify