ParseAPI

What parseAPI MCP server does

The parseAPI MCP server gives an MCP-compatible agent access to structured lookup operations across internet, business, geographic, and time-related data. The available names include stack for website technologies and versions, domain for registration status, dns and mx for DNS records, asn for autonomous-system data, and mac for MAC address lookup. Other tools cover payment-card BINs, healthcare providers, countries and states, addresses, companies, and time.

Business-directory operations can search for companies, retrieve a selected company by ID, look up national company numbers, and inspect directory coverage. Geographic operations include address search, timezone search, and elevation queries. The API also exposes email, phone, weather, currency, date, and related lookup categories in its broader tool set.

How it works

The parseAPI MCP server supports two deployment patterns. The hosted service uses https://mcp.parseapi.com, so an MCP client can connect by URL and complete browser sign-in once. Headless and CI configurations can send an X-API-Key header instead. The local option starts parseapi-mcp with npx and passes the key through the PARSEAPI_KEY environment variable.

Tool calls use named arguments appropriate to the lookup. For example, company_search accepts a search query and country, address_search accepts a query plus geographic filters, and time can use a timezone, coordinates, or UTC defaults. Elevation accepts one coordinate, a list of points, or a sampled path. Each lookup returns the API's JSON response.

Since package version 1.0.0, local and hosted requests use the API contract identified by Parse-Version: 2.0.0. Local deployments should pin the package version and test upgrades before rollout. The hosted service selects the contract supported by its deployed release.

Setup and configuration

For hosted use, add the MCP URL to the client configuration:

{
  "mcpServers": {
    "parseAPI": { "url": "https://mcp.parseapi.com" }
  }
}

For a key-based hosted configuration, add the X-API-Key header. For local stdio, configure npx -y parseapi-mcp and set PARSEAPI_KEY to a key obtained from parseapi.com. The repository also provides a Cursor installation link. The hosted service requires no package installation.

Tools and capabilities

The parseAPI MCP server includes lookup names such as:

• stack, domain, dns, mx, asn, and mac
• card, provider, country_states, address_search, and elevation
• company, company_search, company_id, and company_coverage
• time, time_zones, and date

Full mode provides 68 local lookup tools and 67 hosted lookup tools, with discover available for local metadata and preflight for authenticated task estimates. ip_self is local-only. Company searches can be followed by company_id after reviewing candidates. Deep company, domain, provider, and other records depend on the relevant plan.

Limitations and notes

Time conversion has explicit handling for repeated or skipped local times. The disambiguation option can choose an earlier or later instant, use the compatible default, or reject an ambiguous or nonexistent time. Elevation limits point lists and paths, and paths require a sample count. Australian postal results provide geographic locality choices rather than mailing-address verification.

Older MCP package releases use the team's default API contract. Rolling back to a release without the version header only restores the previous contract if that default has not changed. Local deployments should therefore keep their package version controlled and validate changes before production use.