API Tools
panadata.net
Offers entity search and resolution APIs, allowing lookup of organizations and persons by name or RUC, with confidence scoring and real estate information.
ENDPOINT 1
https://mcp.panadata.net/mcp
MCP server metadata
- Name
- panadata-api
- Version
- 3.4.2
Access to Panadata's public-registry data for Panama, Colombia and Ecuador (v5 surface; panama live). Entities AND assets are addressed by **typed opaque ids** like `pa_own_42` (entity), `pa_finca_153` / `pa_ph_9` (real estate), `pa_entrada_88` / `pa_elemento_5` (registry dockets). Get ids from `resolve_entity` (name/ruc/cedula → ranked candidates with confidence — pick one) or `search_entities`, then pass them verbatim — the id carries the jurisdiction, so by-id tools take no country. `get_entity` returns detail (the `include` product codes unlock more sections and add cost); `get_entities_batch` fetches many ids at once. `get_real_estate` answers price-per-m² questions (per-property `precio_por_m2` + a portfolio average). `list_dockets` then `get_docket` reads a docket's OCR'd text (both accept finca/PH asset ids too, so a property's constitution / MIVI deeds are readable). Add dry_run=true to preview a call's credit cost. `request_entity_update` (owners) + `request_real_estate_update` (finca / PH assets) re-scrape stale data; `get_update_status` polls. `get_entity_records` lists one category of an entity's records (trade, licitaciones, noticias, screening, network, planillas…); `search` runs cross-entity faceted search over a dataset (facets first — e.g. top importers by HS code, spend by gov entity, businesses by industry); `search_by_role` finds the organizations where a person holds a role (agente residente/director). BUILDING A DETERMINISTIC / PRODUCTION APP (fixed queries, batch jobs, dashboards, a backend)? The SAME data, billing, and account are a plain REST API at https://api.panadata.net/v5 — use it directly (lower latency, stable contract) instead of this MCP; see the `panadata://rest-api` resource or https://api.panadata.net/v5/openapi.yml. This MCP is for agentic / runtime-LLM use and prototyping. VALUES ARE NOT WHAT THEY SEEM — figures are DECLARED / registry / customs / AWARDED values, NOT market price, amount paid, or confirmed fact; always state what a value is and its date. sanctions / screening are NAME-MATCHES, not confirmed identity. Every authed call also costs a base fee.
Known tools 14
resolve_entityResolve a name/ruc/cédula to **ranked candidate entities** — each with a typed `gid`, a `confidence` score, and `matched_on` (which field matched).
Inferred read-onlylist_docketsList an entity's Public-Registry dockets (entradas = scanned, elementos = digital).
Inferred read-onlyget_docketFetch a single docket with full metadata and its **ocr_text** — the OCR'd text of the scanned document (plus finalizacion_text when present).
Inferred read-onlysearch_by_roleRelational search: find the **organizations where a person/firm holds a role** (agente residente, director, tesorero, …).
Inferred read-onlyrequest_entity_updateTrigger an async refresh (re-scrape) of an OWNER (organization / persona).
Inferred read-onlyrequest_real_estate_updateTrigger an async re-scrape of a real-estate asset (finca / propiedad horizontal) by its typed id.
Inferred read-onlyget_update_statusPoll the status of an async update request created by request_entity_update.
Potential side effectslist_product_codesList product codes for a jurisdiction with their per-request cost and the data tags each unlocks.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.panadata-api]
url = "https://mcp.panadata.net/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"panadata-api": {
"type": "http",
"url": "https://mcp.panadata.net/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: panadata-api
Remote MCP URL: https://mcp.panadata.net/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"panadata-api": {
"url": "https://mcp.panadata.net/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"panadata-api": {
"type": "http",
"url": "https://mcp.panadata.net/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "panadata-api",
"transport": "streamable-http",
"url": "https://mcp.panadata.net/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.