EximAgent connector

Find real importers and exporters from customs data, from inside the assistant you already use.

What it does

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.

Connection

Server URLhttps://mcp.eximagent.ai/mcp
Transportstreamable HTTP
AuthenticationOAuth 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 everyoneYes — there is no per-user endpoint.

Adding it

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.

Two doors, one service

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. Adding this connector never requires weakening your assistant's sandbox.

What it reads and writes

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.

Privacy, terms and support