US Import Records Buyer Finder MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token, but a call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_us_importersA | Search US customs bill of lading records by company name for importers and overseas suppliers. Returns shipment counts and last shipment dates. Set include_profiles to add trading partners, HS codes, product descriptions, and recent shipments, up to 20 a run. The search matches company names, not products. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection between competing tools. Its description also explicitly bounds its behavior (company-name search, not product search), leaving no ambiguous overlap.
The single tool follows a clear verb_noun snake_case pattern (find_us_importers) that would scale predictably if more tools were added. No mixed conventions exist.
One tool is thin for a data-lookup service, even a narrow one; it is saved by an include_profiles parameter that bundles partner, HS code, and shipment data into the same call. The surface is borderline minimal rather than clearly well-scoped.
Importer lookup by company name is covered, but the description explicitly excludes product search, and profile expansion is capped at 20 records per run with no detail-retrieval or pagination tool. Agents will hit dead ends whenever they need product-based discovery or bulk results.