cityparity MCP Server

The cityparity MCP Server is a durably named, independently usable remote offering for city and relocation comparisons. The official product page at https://cityparity.com/mcp/ describes six tools, and the official machine-readable documentation names the canonical HTTPS endpoint https://mcp.cityparity.com/mcp. The subdomain target is also confirmed by the official cityparity website and the provider repository. Smithery lists bissell-skyler/cityparity as remote and deployed and links the same repository and product page. Smithery verification is not enabled, but the identity is traceable through several provider-controlled or provider-linked sources and an explicit endpoint mapping. The repository names Skyler Bissell in its MIT license, describes the MCP server, and points to cityparity.com. This makes the candidate an independently useful product rather than a temporary demo or directory-only record.

Purpose and tools

According to the provider, compare_cities compares two cities for a household scenario. Its result includes take-home pay, cost categories, an equivalent target salary, quality-of-life differences, and a composite quality score. list_cities discovers valid city slugs grouped by country. get_city_summary provides a city profile covering tax shape, headline costs, safety-net values, and the data year range. rank_cities ranks cities by a weighted quality score and supports regional or country filters. get_safety_net returns parental leave, paid portions, vacation, public holidays, and a healthcare indicator. get_inbound_tax_regime describes modeled regimes for selected countries. These tools support orientation and scenarios, not binding tax, property, or relocation advice.

Data provenance and freshness

The provider website explains that the calculation combines tax rules, city-median rent and living costs, childcare, healthcare, vacation, and parental leave. According to the provider, each figure carries a source and update date, while most underlying data is refreshed annually. The machine-readable documentation describes progressive tax schedules, government subsidies, safety-net calculations, and a cached exchange-rate request. The public MCP repository contains the MCP surface and a forwarding bridge, but not the complete dataset or the full calculation engine. Source quality therefore remains a review responsibility: users should inspect primary sources, dates, geographic coverage, assumptions, and currency. A result may be stale, modeled, or unsuitable for a particular person. Local primary sources and qualified advice are especially important for property, company, and relocation decisions.

Authorization, privacy, and data sharing

The provider documents public access without an API key and edge rate limiting. This does not promise unlimited use and does not replace review of current terms. Inputs can reveal salary, household composition, children’s ages, housing mode, and relocation intent. Users should therefore send only necessary, non-identifying scenarios; names, precise addresses, personal location data, and confidential company information do not belong in requests. According to the provider, queries reach the remote endpoint and are not sent to additional MCP destinations. The MCP client, model provider, network operators, hosting logs, or a proxy may nevertheless process data. Roles, retention, deletion, storage region, subprocessors, and log access must be clarified before production use. This catalog stores no credentials, secrets, tokens, or API keys.

Access limits, risks, and write access

The documented tools calculate and read data; they are not an interface for changing city, property, or company registries. No external-account write access is described. An agent can still transfer results into files, spreadsheets, tickets, reports, or publications. Those destinations need their own roles, least-privilege permissions, allowlisting, and approvals. City and location data is not automatically complete or current. Untrusted inputs, model assumptions, and possible prompt injection in responses must be isolated by the client and reviewed before decisions. TLS, timeouts, response-size limits, and human oversight remain appropriate. The provider does not claim governmental, tax, or financial authority. The E-E-A-T basis of this entry is, according to the provider, the official product page, official documentation, provider website, and published repository; Smithery adds deployment metadata, not proof that every number is correct.

An MCP-compatible client with HTTPS access; requests to the official remote endpoint remain subject to provider limits and current terms.

Add https://mcp.cityparity.com/mcp as a remote server in the MCP client. Before production use, review the endpoint, privacy, limits, and model-provider sharing.

https://mcp.cityparity.com/mcp

According to the provider, no API key is required. Public access does not mean unlimited use; verify current limits and terms.

Read-oriented access to modeled city, tax, cost, and safety-net data; no documented write permissions for external accounts or registries.

Queries are sent to https://mcp.cityparity.com/mcp. Do not transmit personal location data or confidential company information. The MCP client, model provider, and hosting logs may add processing.

Remote service with rate-limited public access. Results are modeled and may become stale. Review prompt injection, untrusted responses, and model-provider sharing before decisions.