Hosted Model Context Protocol server exposing 2.7M U.S. motor carriers as 30+ tools. Connect Claude Desktop, Cursor, Windsurf, or any MCP-compatible client. Bearer token authentication, sub-100ms response times, no SDK required.
Three ways in. No SDK to install for Claude Desktop. Python, TypeScript, and curl examples below.
// Add this to your Claude Desktop config { "mcpServers": { "alphaloops": { "type": "url", "url": "https://mcp-freight.runalphaloops.com/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } } # Restart Claude Desktop. The 30+ AlphaLoops tools appear automatically.
Every facet of carrier intelligence exposed as discrete tools an LLM can call. Each tool has typed inputs and structured outputs.
Resolve any DOT or MC. Full operational profile, authority history, BMC-91 filings.
Filter the carrier graph by fleet size, geography, equipment, technology, growth, authority age.
Rank by similarity to a reference set or natural-language criteria. ICP fit, risk, displacement value.
CSA BASICs, inspection history, crash records, OOS rates, VIN-level equipment, full tech stack.
Chameleon detection, MC sale watchlist, equipment sale signals, federal litigation, AI-flagged signals.
Verified emails and phones for owners, ops VPs, IT directors, CFOs across 2.7M carriers.
Bearer token authentication. Free tier for evaluation, paid tiers for production.
1,000 requests per month. Single API key. Best for evaluation and small-scale agent prototypes.
Get a key →100K requests per month. Multiple API keys. Webhooks. SLA. Best for production agent workflows and embedded vendor use.
See pricing →Unlimited requests. Multi-tenant key management. Volume pricing. Custom data agreements.
Talk to sales →Technical questions about the AlphaLoops MCP server.
The AlphaLoops MCP server endpoint is https://mcp-freight.runalphaloops.com/mcp. Authentication uses a Bearer token in the Authorization header. You'll need an AlphaLoops API key to connect.
Any MCP-compatible client works: Claude Desktop, Claude Code, Cursor, Windsurf, VS Code with GitHub Copilot, Clay (via Claygent), and custom AI agents. The server uses standard MCP URL transport with Bearer token authentication, so any compliant client connects without custom configuration.
HTTPS with Server-Sent Events (SSE) for streaming responses, following the standard MCP URL transport specification. Streamable HTTP transport is supported for Python and TypeScript SDK clients.
The server returns standard JSON-RPC error codes plus AlphaLoops-specific codes for rate limiting (429), authentication (401), insufficient credits (402), and validation errors (400). Errors include a human-readable message and a stable error code for programmatic handling.
Tool schemas are header-pinned via the X-AlphaLoops-Version header. Without the header, you receive the latest version. Breaking changes are released under a new version with a 90-day deprecation window for the prior version. Additive changes ship continuously without a version bump.
Yes. The Enterprise tier supports multi-tenant key management, volume pricing, and custom data agreements for embedded vendor and OEM use cases. Talk to sales for terms.
Yes. FMCSA data is a core layer — DOT numbers, MC authority status, safety ratings, CSA BASIC scores, inspection records, violation history, crash history, and insurance filings. AlphaLoops extends raw FMCSA with technology stack detection, fleet growth signals, contact data, and AI-powered risk monitoring.
Free tier available. Bearer token. Connected in two minutes.