Find real importers and exporters from customs data, from inside the assistant you already use.
The connector answers trade questions from customs shipment records: who imports a product, who exports it, on which corridors and at what volume — then enriches those companies and screens them before you reach out. Rankings are computed over the whole matching corpus rather than a sample, and every answer states the scope it counted.
| Server URL | https://mcp.eximagent.ai/mcp |
|---|---|
| Transport | streamable HTTP |
| Authentication | OAuth 2.1 — dynamic client registration and PKCE. Sign in with Google; no key to paste, and access is revocable at any time. |
| Same URL for everyone | Yes — there is no per-user endpoint. |
claude mcp add --transport http eximagent https://mcp.eximagent.ai/mcp --scope user, then
/mcp to sign in.codex mcp add eximagent --url https://mcp.eximagent.ai/mcp, then
codex mcp login eximagent.Sign-in opens a browser, and a sandboxed session cannot launch one — the attempt fails before the flow starts, which reads as the connector rejecting you rather than as a blocked launch. The connector itself is unaffected: it needs no sandbox network change, and once signed in it works sandboxed exactly as it does otherwise.
Two ways through, neither of which weakens the sandbox. Run
claude mcp login eximagent --no-browser, which prints the URL for you to open in any
browser and takes the redirect back. Or run eximagent connect from the command-line
client, which signs in by device code — no browser launch and no local callback at all — writes the
connector entry for you, and then verifies it by listing the tools and printing the account it
resolved to.
Your assistant cannot add a connector on your own behalf — the steps above are yours to run once, after which the trade verbs appear as tools.
There is also a command-line client. Both reach the same server, the same corpus and the same response envelope; they differ only in transport. The command line runs inside the assistant's sandbox and needs network access granted there, while this connector runs from the assistant itself and needs no sandbox change — so it is the right choice when egress is blocked or nothing may be installed. Running this connector never requires weakening your assistant's sandbox; the one step that wants a browser is the initial sign-in, and the section above gives two ways to complete it without one.
Most tools are read-only lookups over trade data and are annotated as such, so a host can run them without prompting. Tools that change something — saving a list, drafting or sending outreach, starting a paid discovery run — are annotated as writes, and the destructive ones are marked separately so your assistant asks first. Sending is refused outright for a sanctions-screened recipient.
The connector reads the account you sign in with and the trade corpus. It does not read your files, your mail or your other connectors.