Maps & transport · Remote MCP server
Carso Exchange Engine
AI-native platform: cybernetic freight agents transact, verify, find services. Get verified leads.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
exchange.carso/carso-exchange-engine- Version
- 0.1.3
- Status
- Active
- Category
- maps & transport
- Transport
- Streamable HTTP
- Published
- 2026-07-30
- Updated
- 2026-07-30
- Publisher
- exchange.carso
- Namespace
- Namespace verified by the MCP Registry via the domain carso.exchange · how
- Website
- engine.carso.cloud
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://engine.carso.exchange/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
How to connect Carso Exchange Engine
Carso Exchange Engine is a remote MCP server: there is nothing to install. Its endpoint is https://engine.carso.exchange/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, engine.carso.cloud, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More maps & transport servers
| Server | Runs |
|---|---|
| Car HandshakeFind and compare live vehicle inventory from participating US dealers and contact them with consent. | Remote · HTTPLive check: ✓ handshake |
| Car Recalls MCPVehicle safety recalls from NHTSA by make, model, and year. No key required. | Local · stdio |
| CarShakeVehicle handover checklists, damage-documentation best practices, valet/rental/service FAQs. | Remote · HTTPLive check: ✓ handshake |
| CarsMultiverse - the recall recordVehicle safety recalls from four registers, matched across borders on the maker's own code. | Remote · HTTPLive check: ✓ handshake |
| Carsxe MCPMCP server for CarsXE vehicle data: VIN, specs, history, images, recalls, and OBD codes. | Remote · HTTPLive check: sign-in required |
| CARTOQuery your data warehouses, run workflows, and render maps from your CARTO workspace. | Remote · HTTP |
| Carvector MCPVehicle specs, federal recalls, complaints, TSBs, investigations and OBD-II DTC data for AI agents. | Local · stdio |
| CatalogMaritime VSAT spares: part search, fitment, supersession and quote requests for satmarin.com. | Remote · HTTPLive check: ✓ handshake |