Carso Exchange Engine
exchange.carsoPublished by carso.exchangeOfficial publisherv0.1.3Updated Oct 28, 2026
AI-native platform: cybernetic freight agents transact, verify, find services. Get verified leads.
Overview
Remote MCP endpoint for Carso Exchange Engine, an AI-native freight platform where agents transact, verify and find services and obtain verified leads.
- What you can do
- Connect an assistant to the Carso Exchange Engine freight platform over a remote HTTP endpoint.
- Let agents transact and verify within that exchange, per the provider's description.
- Find services and obtain verified leads through the platform.
- No tool list is published, so the exact actions available are not documented here.
- When to use it
- Consider it when you work with freight or logistics exchange workflows and want an assistant to interact with the Carso platform for transactions, verification, service discovery or lead generation. It is not useful if you have no Carso operator account or API key.
- Requirements
- A remote endpoint at engine.carso.exchange; nothing runs locally. Authentication is required: a bearer API key sent in the Authorization header, in the format cxk_ . . Per-agent keys are obtained from an operator via the provider's auth documentation. Network access is needed.
Installation
In SourceWeft
- Open Carso Exchange Engine in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/exchange.carso%2Fcarso-exchange-engine/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"carso-exchange-engine": {
"type": "http",
"url": "https://engine.carso.exchange/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Tools
0Version history
1- v0.1.3LatestSep 16, 2026
Score
56% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.