← Registry

General Tools

epkproperties.com

Provides general-purpose tools through the Model Context Protocol.

1 endpoint6 known toolsFirst detected September 17, 2026Last detected September 17, 2026

ENDPOINT 1

https://mcp.epkproperties.com/mcp

No auth detected

MCP server metadata

Name
epk-properties-public
Version
2.2.8
Capabilities
tools.listChangedresources.listChangedprompts.listChangedlogging
Server instructions

Use this server only for EPK Properties information that is already public: published listings and public guides for Panama and the Dominican Republic. Cite canonical URLs. Treat prices and availability as changeable, and guide content as informational rather than legal, tax, financial, or immigration advice. No private client, owner, workspace, admin, or write data is available.

Known tools 6

search

Use this for EPK public knowledge searches and always when one request combines property listings with guides, regulations, taxes, residency, relocation, or due diligence.

Inferred read-only
fetch

Use this when the user wants the full public property or guide document identified by a stable public EPK document ID or a prior search result.

Inferred read-only
search_properties

Use this when the user wants only public EPK Properties listings with explicit country, sale/rent, property type, price, bedroom, bathroom, area, location, or descriptive-keyword filters.

Inferred read-only
get_property

Use this when the user supplies a public EPK property UUID or wants full public details for a result returned by search_properties.

Inferred read-only
search_guides

Use this when the user asks only for EPK public guidance about buying, taxation, regulations, residency, locations, rental management, relocation, or due diligence in Panama or the Dominican Republic.

Inferred read-only
get_guide_section

Use this when the user supplies a public EPK guide section ID or wants the complete section identified by search_guides.

Inferred read-only

CONNECT 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.epk-properties-public]
url = "https://mcp.epkproperties.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "epk-properties-public": {
      "type": "http",
      "url": "https://mcp.epkproperties.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: epk-properties-public
Remote MCP URL: https://mcp.epkproperties.com/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": {
    "epk-properties-public": {
      "url": "https://mcp.epkproperties.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "epk-properties-public": {
      "type": "http",
      "url": "https://mcp.epkproperties.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "epk-properties-public",
  "transport": "streamable-http",
  "url": "https://mcp.epkproperties.com/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.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.