Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Polystate

REMOTE · POLYSTATE-MCP-SERVER.SHY-SURF-2FDF.WORKERS.DEV

Relocation, residency, visa, company-formation and crypto-tax data for about 170 countries.

+3 this week 73 Trust /100

Last scanned (21 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability89
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 18478 tokens (~52/item across 355 items; 15 tools + 340 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1
    • Server version: 0.3.0 → 0.3.1 functional
  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 +41
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Authorization: fail → partial ▲ security
    • First check of Judged manipulation: pass security
    • MCP protocol: unverified → pass ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 100 functional
  • 11 Nov 26 28

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://polystate-mcp-server.shy-surf-2fdf.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=shy-surf-2fdf.workers.dev CN=YE2,O=Let's Encrypt,C=US 11 Nov 2026 9 Feb 2027 ECDSA 256 ECDSA-SHA384 622d30e7d714c8f74aae84a2725e10fd037
SANs: *.shy-surf-2fdf.workers.dev, shy-surf-2fdf.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of polystate-mcp-server.shy-surf-2fdf.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://polystate-mcp-server.shy-surf-2fdf.workers.dev/mcp Verified 200
http (plaintext) http://polystate-mcp-server.shy-surf-2fdf.workers.dev/mcp Inconclusive 406
MCP tools · 15 exposed · ~4,923 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
book_service ~274

Use when the person has decided to buy a Polystate service — e.g. 'book the Wyoming LLC', 'start my Paraguay residency'. With a Polystate API key it starts a checkout and returns the link; without a key it returns the polystate.io page where the person books instead, and no checkout is created. No payment is taken until the person completes it. Give the service `id` (most reliable) or the `service` name from list_services (case, accents and hyphens are ignored), optionally narrowed by `country`. A partial or ambiguous name returns candidates instead of booking. Returns checkoutUrl/sessionId/totalAmount/currency for card-checkout services, or ctaUrl/note for services handled by a partner. Confirm with the person before calling.

NameTypeReqDescription
categoryinteger–Internal numeric service category id. Rarely needed.
countrystring–Narrow the match to one country: ISO-3166 alpha-2/alpha-3 code or English name, e.g. 'PY' or 'Paraguay'.
country_idinteger–Internal numeric country id. Prefer `country`.
servicestringyesExact service name or id as returned by list_services, e.g. 'Wyoming LLC Formation'. A partial name returns candidates instead of booking.

No output schema declared.

No examples provided.

check_eligibility ~189

Use for 'can I, as a citizen of X, get this Polystate service' — e.g. 'can a US citizen buy Paraguay Temporary Residence'. Give `nationality` (ISO-3166 code or English name) and the `service` id or name as returned by list_services (case, accents and hyphens are ignored). Returns the service's formal requirements and whether any nationality restriction applies; services are treated as eligible until a structured restriction is recorded. A partial or ambiguous name returns candidates instead of guessing. Free: never consumes quota.

NameTypeReqDescription
nationalitystringyesApplicant's nationality: ISO-3166 alpha-2/alpha-3 code or English name, e.g. 'US', 'USA', 'United States'.
servicestringyesService name or id exactly as returned by list_services, e.g. 'Paraguay Temporary Residence'.

No output schema declared.

No examples provided.

check_licensed_agent ~405

Use for 'is this agent / firm licensed for citizenship or residency by investment' or 'who are the authorised agents for X' — e.g. 'is Arton Capital an authorised agent for Saint Lucia', 'licensed agents for the St Kitts CBI', 'check licence RES-ACCA'. Searches the official government lists of licensed / authorised agents for St Kitts and Nevis, Antigua and Barbuda, Dominica, Grenada, Saint Lucia, Malta (MPRP residency), Vanuatu and Nauru. Optional `name` (firm, person or licence number; word order, accents, punctuation and company endings ignored) and optional `country` (ISO-3166 code or English name); omit both to get the 8 lists with entry counts and official source URLs. Returns matches with list section, licence number (only Saint Lucia and Malta publish them), website, authority and the official `source_url`, plus `checked_at`. No emails or phone numbers. A country outside the 8 returns `list_available: false`. A name matches when every query word is a whole word of it, so compare the exact name and licence number before telling someone a firm is listed: a similarly named firm is not the same firm. Not finding a name does not prove a firm is unlicensed — say so and point to `source_url`.

NameTypeReqDescription
countrystring–Programme country: ISO-3166 alpha-2/alpha-3 code or English name, e.g. 'St Kitts and Nevis', 'GD', 'Malta'. Omit to search all lists.
limitinteger–Maximum matches to return (1-50, default 20).
namestring–Firm or person name, or a licence number, e.g. 'Arton Capital', 'Nuri Katz', 'RES-ACCA'. Word order, accents, punctuation and company endings (Ltd, Inc) are ignored.

No output schema declared.

No examples provided.

compare_jurisdictions ~474

Use when the question is 'which country is best/safest/cheapest for X' or any ranked multi-country comparison — e.g. 'compare Portugal vs Paraguay vs UAE for relocation', 'safest low-tax countries', 'rank countries by cost of living and banking access'. Scores jurisdictions on an 8-dimension weighted model (tax, safety, healthcare, institutions, business_ease, privacy, cost_of_living, banking_access). Pass `countries` (2–50 ISO-3166 codes or English names) to compare a specific set, or omit to rank all available countries (cap with `limit`). Pass `weights` (0–100 per dimension) to match the user's stated priorities. The `tax` score reflects how an individual's crypto is taxed, not salary income tax. `tax_basis` on each row gives the estimate it is computed from and the source's two rule wordings (capital gains, income on crypto): when a wording is a range or has conditions the score rests on an estimate, so quote the wording. Where that estimate is 0%, `zero_tax_rate` on the row says whether the zero is `firm` (scores 10) or `conditional` (holds only under conditions such as a holding period or foreign-source income; scores 9.5), so check get_crypto_tax_treatment before quoting a conditional zero; it is null for any other estimate. The overall `score` is led by the crypto tier, so a row can outrank another with a better `tax` score. For goal-driven relocation shortlists that also weigh residency terms, crypto-tax tier, and passport power, use optimize_relocation instead.

NameTypeReqDescription
countriesarray–2-50 countries to compare, each an ISO-3166 alpha-2/alpha-3 code or English name, e.g. ['PT', 'Paraguay', 'UAE']. Omit to rank every country.
limitinteger–How many countries to return when `countries` is omitted (default 20).
weightsobject–Importance of each dimension, 0-100: tax, safety, healthcare, institutions, business_ease, privacy, cost_of_living, banking_access. Omitted dimensions keep their default weight.

No output schema declared.

No examples provided.

get_company_formation ~214

Use for 'set up / incorporate / register a company in X' — e.g. 'Wyoming LLC formation cost' (country US), 'Dubai free zone company requirements' (country AE), 'Prospera LLC' (country Honduras or Prospera). Give the country (ISO-3166 code or English name; a US state resolves to the US, 'Prospera' to Honduras), optional `entity_type` filter (for example: llc, corporation, free_zone, ibc). Returns formation requirements, minimum investment, annual cost, time-to-formation, benefits, and tax notes.

NameTypeReqDescription
countrystringyesCountry to incorporate in: ISO-3166 alpha-2/alpha-3 code or English name, e.g. 'US', 'USA', 'United States'.
entity_typestring–Exact entity type to filter on, e.g. 'llc', 'corporation', 'free_zone', 'ibc'. Omit to list every structure on file.

No output schema declared.

No examples provided.

get_crypto_tax_treatment ~156

Use for 'how is crypto taxed in X' — e.g. 'is crypto tax-free in Portugal', 'Germany 1-year holding rule', 'crypto capital gains in UAE', 'do I pay tax selling bitcoin in Slovakia'. Give the country (ISO-3166 code or English name). Returns the country's crypto tier, summary, effective individual rate, capital gains, income tax on crypto, corporate tax, VAT, and supporting details, with data_as_of and sources. For two-country crypto comparisons use tax_compare.

NameTypeReqDescription
countrystringyesCountry to look up: ISO-3166 alpha-2/alpha-3 code or English name, e.g. 'DE', 'DEU', 'Germany'.

No output schema declared.

No examples provided.

get_legal_changes ~432

Use for 'what changed recently / any new laws in X' — e.g. 'new crypto regulation in Portugal 2026', 'recent visa rule changes Thailand', 'what changed in Paraguay immigration law this year'. Returns legal and regulatory change records, sorted newest first. Filter by `country` (single) or `countries` (array, up to 50), optional `categories` (array), and either a `from_date`/`to_date` range or a `month`/`year` pair (mutually exclusive). Supports `limit` (1–100) and `offset` for pagination. Each record carries title, summary, category, date and sources; pass `include_full_content: true` only when the full text is needed.

NameTypeReqDescription
categoriesarray–Exact category names to filter on, e.g. ['Corporate Taxation']. Each result's `category` field shows the valid values.
countriesarray–Several countries to filter on (up to 50), same formats as `country`.
countrystring–Single country to filter on: ISO-3166 alpha-2/alpha-3 code or English name, e.g. 'PT' or 'Portugal'.
from_datestring–Start of a date range, YYYY-MM-DD. Must be given together with `to_date`.
include_full_contentboolean–Set true to include each record's full text (several thousand characters each). Default false returns title, summary and sources only.
limitinteger–How many records to return (1-100, default 20).
monthinteger–Calendar month 1-12. Must be given together with `year`.
offsetinteger–Records to skip, for paging. Use the response's `next_offset`.
to_datestring–End of a date range, YYYY-MM-DD. Must be given together with `from_date`.
yearinteger–Four-digit year, e.g. 2026. Must be given together with `month`.

No output schema declared.

No examples provided.

get_residency_programs ~290

Use for 'how do I get residency in X' — e.g. 'Paraguay tax residency requirements', 'Portugal golden visa program', 'UAE digital nomad residency', 'Prospera tax residency'. Give the country (ISO-3166 code or English name; 'Prospera' resolves to Honduras and returns the Próspera zone program when `category` is omitted), optional `category` filter (`temporary` | `permanent` | `investor` | `digital_nomad`). Returns program names, requirements, benefits, cost, time to citizenship, minimum presence, and tax implications, with sources, last_verified and a confidence level per program. Cost: `minimum_investment` and `annual_cost` are the source's wording (an investment or income threshold, often in local currency) and are what to quote; `fees.setup` and `fees.recurring` are USD numbers only for the few programs that publish their own fees, and null otherwise (null is not zero).

NameTypeReqDescription
categorystring–Return only programs of this kind. Omit to get every program on file.
countrystringyesCountry to get residency programs for: ISO-3166 alpha-2/alpha-3 code or English name, e.g. 'PY', 'PRY', 'Paraguay'. 'Prospera' resolves to Honduras.

No output schema declared.

No examples provided.

get_tax_rates ~473

Use for 'how are crypto gains and company profits taxed in X' — e.g. 'tax on selling bitcoin in Portugal', 'corporate tax rate in Paraguay', 'special tax regimes Italy'. Give the country (ISO-3166 code or English name), optional `tax_type` filter (`income` | `corporate` | `vat` | `capital_gains` | `crypto`). Returns, per rate, the source's own wording in `as_reported`, its first percentage as `rate`, a `conditional` flag (true when the wording is a range or has conditions — quote `as_reported` then) and an `applies_to` label; plus special regimes, crypto tier, last_verified and sources. `territorial_vs_worldwide` is set only for the few countries the dataset flags as territorial; null means not flagged, not 'worldwide'. Scope: `corporate` is the headline company rate; the other figures describe how CRYPTO is taxed. General salary/employment income tax brackets and the consumer VAT rate are NOT in this dataset — tell the person that rather than quoting these numbers as such. Separately, `general_rates` gives the OECD's general statutory rates where the OECD covers the country: `corporate_income_tax` (the combined company rate: central plus a representative sub-national rate and surcharges, so it can differ from the crypto source's `corporate`) and `top_personal_income_tax`, each with `rate`, `year`, `measure` and the OECD citation in `source`; null means not covered by the OECD table, or held back because the source value looks wrong (then listed under `general_rates.withheld` with the reason), never zero; `vat` is always null. These are national figures and do not describe a particular state or region. `found: false` means no crypto-tax rows for the country; `general_rates` can still be filled. For side-by-side country comparisons use tax_compare.

NameTypeReqDescription
countrystringyesCountry to look up: ISO-3166 alpha-2/alpha-3 code or English name, e.g. 'PT', 'PRT', 'Portugal'.
tax_typestring–Return only this rate. Omit to get all five.

No output schema declared.

No examples provided.

get_tax_treaties ~164

Use for 'does X have a tax treaty / double taxation agreement with Y' or 'which countries does X have DTAs with' — e.g. 'France tax treaty partners', 'does Georgia have a DTA with Germany'. Give one country (ISO-3166 code or English name). Returns the treaty count and the list of treaty partners (code and name). Treaty data exists for about half the countries: when `data_available` is false the count is null, which means no data on file, not that the country has no treaties.

NameTypeReqDescription
countrystringyesCountry whose treaty partners to list: ISO-3166 alpha-2/alpha-3 code or English name, e.g. 'GE', 'GEO', 'Georgia'.

No output schema declared.

No examples provided.

get_visa_requirements ~275

Use for 'what are the requirements/documents for a visa to X' — e.g. 'Paraguay residency visa requirements for US citizens', 'Thailand DTV requirements', 'what do I need for a Portugal D7'. Give `passport_country` and `destination_country` (ISO-3166 code or English name), optional `visa_type` filter. Uses passport-specific data when available and falls back to destination program data otherwise. Each result carries `official_link` and `data_as_of` (the date the row was last loaded, not a check of the rule; null when undated). To discover and rank which visa options exist for a route, use visa_check first.

NameTypeReqDescription
destination_countrystringyesCountry being travelled to: ISO-3166 alpha-2/alpha-3 code or English name, e.g. 'TH', 'THA', 'Thailand'.
passport_countrystringyesCountry of the traveller's passport: ISO-3166 alpha-2/alpha-3 code or English name, e.g. 'SK', 'SVK', 'Slovakia'.
visa_typestring–Keyword filter on the visa type, e.g. 'digital nomad', 'work', 'visa_free'. Omit to get every option on file.

No output schema declared.

No examples provided.

list_services ~262

Use for 'what can Polystate do for me in X' or to find the exact service name before checking eligibility or booking — e.g. 'what residency services do you sell for Paraguay', 'do you offer a Wyoming LLC', 'list bank account services'. Optional `country` (ISO-3166 code or English name) and `search` keyword (case and accents ignored); omit both to list the whole catalog. Returns each service's id, exact name, description, list price and processing time. Free: never consumes quota. For program facts about countries Polystate does not sell in, use get_residency_programs or get_company_formation.

NameTypeReqDescription
countrystring–Only services for this country: ISO-3166 alpha-2/alpha-3 code or English name, e.g. 'PY' or 'Paraguay'.
limitinteger–How many services to return (1-50, default 25).
offsetinteger–Services to skip, for paging. Use the response's `next_offset`.
searchstring–Keyword that must appear in the service name, e.g. 'residence', 'LLC', 'bank', 'prospera'. Case and accents are ignored.

No output schema declared.

No examples provided.

optimize_relocation ~544

Use for open-ended 'where should I move / relocate / base myself' questions — e.g. 'best country for a crypto founder with a German passport', 'where can I get residency fast, pay no tax on foreign income, and reach citizenship in under 5 years', 'territorial-tax countries with easy residency'. Returns a ranked jurisdiction shortlist fusing tax + crypto-tax tier + residency-program terms + passport power. Provide goal `weights` (0–100 across tax, safety, healthcare, institutions, business_ease, privacy, cost_of_living, banking_access, crypto_tax, residency_ease, passport_power), optional `passport_country` (enables the passport_power dimension — visa-free destination count for the held passport), and optional hard `filters` (crypto_tier_in, max_time_to_citizenship_years, max_minimum_presence_days_per_year, territorial_tax_only, requires_bookable_service, countries). Each result carries a fit score, per-dimension breakdown, plain-language `why`, provenance (last_verified/sources/confidence), and a lead-gen handoff link. `tax_basis` on a result gives the estimate its `tax` score is computed from and the source's two rule wordings (quote the wording when it is a range or has conditions), and `crypto_tax.zero_rate` says whether a 0% estimate is `firm` or `conditional` (null when the estimate is not 0%). Returns program terms and eligibility only — no prices. For a plain scored comparison of named countries use compare_jurisdictions.

NameTypeReqDescription
filtersobject–Hard requirements that exclude countries: crypto_tier_in (HEAVEN best to HELL worst), max_time_to_citizenship_years, max_minimum_presence_days_per_year, territorial_tax_only, requires_bookable_servic…
goal_tagstring–Short label for the person's goal, e.g. 'crypto_tax'. Only tags the follow-up link.
limitinteger–How many ranked countries to return (1-50, default 10).
passport_countrystring–Passport the person holds: ISO-3166 alpha-2/alpha-3 code or English name, e.g. 'DE' or 'Germany'. Enables the passport_power dimension.
weightsobject–Importance of each goal, 0-100: tax, safety, healthcare, institutions, business_ease, privacy, cost_of_living, banking_access, crypto_tax, residency_ease, passport_power. Set the ones the person care…

No output schema declared.

No examples provided.

tax_compare ~435

Use for head-to-head 'X vs Y' questions about crypto and company taxes — e.g. 'crypto taxes Germany vs Czechia', 'is Dubai or Singapore better for corporate tax', 'Portugal vs Spain for a crypto investor'. Give two countries `country1` and `country2` (ISO-3166 code or English name). Returns side-by-side headline rates with the source's wording per rate in `rates_detail`, treaty counts, crypto tier, and the tax-only scoring dimension (`tax_score`, with `zero_tax_rate` saying whether a 0% estimate is `firm` or `conditional`). A comparison answers `depends_on_conditions` instead of naming a winner when either rate is a range or conditional. The income and capital-gains figures describe how CRYPTO is taxed and `corporate` is the headline company rate; salary income tax brackets are not covered (see `coverage_note`). Each country also carries `general_rates`: the OECD's combined statutory company income tax rate and top personal income tax rate with year and citation, null where the OECD does not cover the country or the figure is held back (then listed under `withheld` with the reason). Company tax is compared twice and the answers can differ: `comparison.lower_corporate_tax` uses the crypto source's `corporate` figure (sometimes the central-government rate alone, sometimes simply older), `comparison.lower_corporate_tax_oecd` uses the OECD's combined rate; for a general company tax question use the OECD one. `tax_found: false` means no crypto-tax rows for that country; its `general_rates` can still be filled. A null treaty_count means no data on file. To rank more than two countries use compare_jurisdictions.

NameTypeReqDescription
country1stringyesFirst country: ISO-3166 alpha-2/alpha-3 code or English name, e.g. 'PT' or 'Portugal'.
country2stringyesSecond country: ISO-3166 alpha-2/alpha-3 code or English name, e.g. 'ES' or 'Spain'.

No output schema declared.

No examples provided.

visa_check ~336

Use for 'can I go / work / stay in X with a Y passport' questions — e.g. 'Slovakia to Thailand visa', 'US citizen digital nomad visa Japan', 'do Indian passport holders need a visa for Georgia'. Give the passport country and destination (ISO-3166 code or English name), optional `visa_type` keyword filter (e.g. 'digital nomad', 'work', 'tourist') and `max_alternatives` (0–20). Returns the best-matching visa option, ranked alternatives, source, passport-specificity flag, and a concise recommendation. Each option carries `official_link` and `data_as_of` (the date the row was last loaded, not a check of the rule; null when undated). For the detailed requirements/documents of a specific route use get_visa_requirements.

NameTypeReqDescription
destination_countrystringyesCountry being travelled to: ISO-3166 alpha-2/alpha-3 code or English name, e.g. 'TH', 'THA', 'Thailand'.
max_alternativesinteger–How many alternative visa options to return after the best match (0-20, default 5).
passport_countrystringyesCountry of the traveller's passport: ISO-3166 alpha-2/alpha-3 code or English name, e.g. 'SK', 'SVK', 'Slovakia'.
visa_typestring–Keyword filter on the visa type, e.g. 'digital nomad', 'work', 'visa_free'. Omit to get every option on file.

No output schema declared.

No examples provided.

Install

How do I install the Polystate MCP server?

Polystate is a hosted endpoint at https://polystate-mcp-server.shy-surf-2fdf.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · polystate-mcp-server.shy-surf-2fdf.workers.dev

# add to Claude Code
claude mcp add --transport http io-polystate-mcp 'https://polystate-mcp-server.shy-surf-2fdf.workers.dev/mcp'
Common questions

What is the Polystate MCP server?

Polystate is an MCP server listed in the public MCP registry as io.polystate/mcp. Relocation, residency, visa, company-formation and crypto-tax data for about 170 countries. This page covers its hosted endpoint (https://polystate-mcp-server.shy-surf-2fdf.workers.dev/mcp).

Is the Polystate MCP server safe to use?

Polystate scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Polystate MCP server expose?

Polystate exposes 15 tools: compare_jurisdictions, optimize_relocation, visa_check, check_eligibility, list_services, and 10 more. Their descriptions and schemas cost roughly 4,923 tokens of context every time the server is loaded.

Does the Polystate MCP server require authentication?

No. We connected to Polystate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Polystate MCP server still maintained?

Polystate is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Polystate MCP server?

VerifyMCP ran 12 checks on Polystate, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Polystate: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.