MCP Docs
FAQ
Pangolinfo MCP setup, config, auth, and troubleshooting FAQ — MCP vs REST API / empty tool list / 401 auth failure / API Key rotation.
Same data, just two different ways to access it for different scenarios.
| Dimension | 🌟 MCP (Streamable HTTP) | 🛠 REST API |
|---|---|---|
| Use case | Direct invocation inside AI Agent conversation | Scripts / CI / batch automation |
| Setup cost | One URL + Key | Write an HTTP client per script |
| Response shape | AI-friendly structured objects | Standard REST JSON |
| Credential management | Configure once in client | Inject Key per project |
| Network | Must reach mcp.pangolinfo.com | Must reach api.pangolinfo.com |
Rule of thumb: daily conversation / product research / IP screening → MCP; batch automation → REST API. Both use the same API Key and billing.
Check in order:
- Did you really restart the client? Most clients don’t re-establish MCP connections on config reload — you need a full process restart.
- URL spelling — must be
https://mcp.pangolinfo.com/mcp(note the trailing/mcppath, don’t omit it). - Field names — different clients use different fields (
url/serverUrl/endpoint/transportType). Reference the Client Setup snippet for your specific client. - Transport type — Claude Code needs
"type": "http", Cline needs"transportType": "streamableHttp". Without these, the client tries stdio and fails. - Config file location — project-level config overrides global. Confirm which one is actually active.
- Client logs — most clients expose MCP debug logs (Cursor under Output → MCP, Claude Code at
~/.claude/logs/). Check the actual error message.
- Check that it’s a Permanent Key: Short-term tokens expire in 7 or 14 days. Go to Pangolinfo Console → Profile → API Key and grab a Permanent Key.
- Check header format: Must be
Authorization: Bearer <YOUR_API_KEY>— note the single space betweenBearerand the key, no quotes around the key. - Check if the Key was revoked: Account suspension or key revocation by you / a teammate also causes 401.
- Check account balance: Zero credits also rejects auth. Recharge or activate a subscription.
- AI got the tool name wrong: have the AI call
pangolinfo_capabilities()to fetch the current list, then call by exact name. - Client cached old schema: restart the client + refresh the MCP panel.
- Pangolinfo temporarily disabled a tool: occasionally we disable individual tools due to upstream data source issues (usually restored within hours).
pangolinfo_capabilities()again will reflect the latest state.
Recommended approach:
- One Permanent Key per person: generate independent Permanent Keys per teammate in the Pangolinfo Console (per-user usage + billing).
- Where to store the config: have teammates put their Key in user-level config files (
~/.cursor/mcp.json,~/.claude.json) — never commit project-level.mcp.jsonto Git. - If you must share project-level config: add
.mcp.jsonto.gitignoreand commit a placeholder.mcp.example.jsoninstead. - Revoke a Key: when a teammate leaves, revoke their Key in the console. It becomes invalid immediately without affecting others.
- Use a corporate proxy: most clients respect the
HTTPS_PROXYenvironment variable. In the terminal that launches the AI client, runexport HTTPS_PROXY=http://your-proxy:port. - Check DNS poisoning:
nslookup mcp.pangolinfo.comto confirm it resolves to a valid IP. - Fall back to REST API: if remote MCP is fully blocked but
api.pangolinfo.comis reachable, switch to the REST API and call it from a script. - Contact us: for fully air-gapped enterprise networks, open a ticket in the Pangolinfo Console to discuss a dedicated line.
Identical — MCP is a semantic wrapper around the REST API. Each successful call deducts the same credits as the corresponding REST endpoint. Per-tool credit costs are in Tool Reference.
Usage view: Pangolinfo Console → Profile → Usage Stats, filterable by tool / time range / API Key.
- Narrow the scope: have the AI use more specific parameters (e.g.
page=1instead of scraping all reviews). - Multi-step chain: take summary fields first, drill down as needed. E.g. start with
search_amazonfor an overview, thenget_amazon_producton the interesting ASIN. - Client context window: if it’s the client model’s own context limit (not MCP truncation), switch to a larger-context model.
- Availability: MCP server shares infrastructure with the REST API. Availability per official SLA.
- Data freshness: Amazon products / reviews / search results are scraped live (each call re-scrapes, not cached); Trends data has the official ~24h delay; WIPO has the official DB’s weekly delay.
- Status monitoring: service incidents are posted at the top of the Pangolinfo Console. You can also subscribe to status-page email notifications.
Still stuck?
- Check the field details for your specific client in Client Setup
- Or open a ticket in the Pangolinfo Console with your MCP client logs. We usually respond within 24h.
On this page