HALPII Tax ID
REMOTE · TAXID.HALPII.COM
Tax IDs in 135 countries: official registry check in 51 (Peru, Brazil, Chile, EU VIES, UK, Japan).
Available components
Last scanned (9 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security80
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2847 tokens (~474/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 21 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “validate_colombia_nit” rewrote its description, which is the text the model reads security
- Tool “validate_costa_rica_cedula” rewrote its description, which is the text the model reads security
- Tool “validate_peru_ruc” rewrote its description, which is the text the model reads security
- Tool “validate_tax_id” rewrote its description, which is the text the model reads security
- Tool “validate_tax_id_format” rewrote its description, which is the text the model reads security
- Schema quality: 345 → 474 ▼ functional
- Schema quality: 345 → 401 ▼ functional
- “validate_tax_id” reworded the description of “country” cosmetic
- “validate_tax_id” reworded the description of “id_type” cosmetic
- 20 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “validate_tax_id_format” rewrote its description, which is the text the model reads security
- Tool “validate_tax_id_format” changed its title: Check tax ID format (about 50 countries) → Check tax ID format (more than 100 countries and territories) cosmetic
- 19 Nov 26 +1
- “validate_colombia_nit” reworded the description of “nit” cosmetic
- “validate_costa_rica_cedula” reworded the description of “cedula” cosmetic
- “validate_mexico_rfc” reworded the description of “rfc” cosmetic
- “validate_peru_ruc” reworded the description of “ruc” cosmetic
- “validate_tax_id” reworded the description of “id” cosmetic
- “validate_tax_id_format” reworded the description of “id” cosmetic
6 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 17 Nov 26 +3
- HSTS header: fail → pass ▲ security
- 16 Nov 26 −2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “validate_peru_ruc” rewrote its description, which is the text the model reads security
- Schema quality: 231 → 335 ▼ functional
- Server version: 0.1.0 → 0.4.0 functional
- New tool “validate_colombia_nit” functional
- New tool “validate_costa_rica_cedula” functional
- New tool “validate_mexico_rfc” functional
- New tool “validate_tax_id” functional
- New tool “validate_tax_id_format” functional
- 15 Nov 26 −6
- Authorization: pass → partial ▼ security
- Tool “validate_peru_ruc” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 14 Nov 26 78
First indexed and scored.
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://taxid.halpii.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=halpii.com | CN=WE1,O=Google Trust Services,C=US | 14 Nov 2026 | 12 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | b6811e363387101e13fa57a30c270f09 |
| SANs: halpii.com, taxid.halpii.com, *.taxid.halpii.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of taxid.halpii.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| halpii.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), serial=(), hid=(), bluetooth=(), midi=(), accelerometer=(), gyroscope=(), magnetometer=(), display-capture=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://taxid.halpii.com/mcp | Verified | 200 | |
| http (plaintext) | http://taxid.halpii.com/mcp | HTTPS enforced | 301 | https://taxid.halpii.com/mcp |
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 →
validate_colombia_nit Validate Colombia NIT (tax ID) ~171
Validate a Colombian NIT with the DIAN check-digit algorithm and look it up live in the RUES commercial registry kept by the chambers of commerce (Confecámaras, licensed CC BY-SA 4.0). Returns the computed check digit, legal name, registration status (active, cancelled and others), last renewal year, registration dates, chamber of commerce, legal form, CIIU activity codes and a pass/review/fail assessment with reasons. This is the commercial registry, not DIAN tax status. For individuals only the check digit and registration status are returned, without name or address.
| Name | Type | Req | Description |
|---|---|---|---|
| nit | string | yes | Colombian NIT with or without the check digit, e.g. "899999068-1" or "899999068". Dots and spaces are ignored. |
No output schema declared.
No examples provided.
validate_costa_rica_cedula Validate Costa Rica cédula (tax ID, beta) ~179
Check a Costa Rican tax ID (cédula física, cédula jurídica, DIMEX or NITE) live against the Ministerio de Hacienda. Returns the ID type, taxpayer status (registered or not), tax regime, delinquent (moroso) and non-filer (omiso) flags, tax administration office, registered economic activities and a pass/review/fail assessment with reasons. Beta: the meaning of some Hacienda fields is not formally documented. Names are returned only for legal entities; for individuals the name is withheld.
| Name | Type | Req | Description |
|---|---|---|---|
| cedula | string | yes | Costa Rican ID: 9 digits (cédula física), 10 digits (cédula jurídica or NITE) or 11-12 digits (DIMEX), e.g. "2-100-042005". Dashes are ignored. |
No output schema declared.
No examples provided.
validate_mexico_rfc Check Mexico RFC (tax ID) ~192
Check a Mexican RFC (12 characters for companies, 13 for individuals): structure, encoded date and SAT check digit, plus whether it appears on SAT's public lists under article 69-B of the Código Fiscal de la Federación (taxpayers presumed or confirmed to invoice non-existent operations, also called EFOS) and article 69 (not located, unpaid or cancelled tax debts, tax-crime convictions). Returns the list status with publication dates and a review/fail assessment with reasons. Mexico publishes no RFC registry, so the result never confirms that an RFC is registered or active and never returns pass. Company names are returned only when a SAT list carries them; individuals get list status only, without name or birth date.
| Name | Type | Req | Description |
|---|---|---|---|
| rfc | string | yes | Mexican RFC, 12 or 13 characters, e.g. "SAT970701NN3". Case, spaces and dashes are ignored. |
No output schema declared.
No examples provided.
validate_peru_ruc Validate Peru RUC (tax ID) ~233
Validate a Peruvian RUC (11-digit tax ID) and look up the company in the SUNAT registry. Returns check-digit validity, legal name, taxpayer status (active or not), fiscal-address condition (HABIDO / NO HABIDO), fiscal address with district, and a pass/review/fail vendor assessment with reasons. Full data is returned for company RUCs (prefix 20). For natural-person RUCs (prefix 10, 15, 16, 17) the taxpayer status and address condition are returned; the holder's name is returned only when the connector is used with an API key (?api_key=... or Authorization header), for supplier and customer verification; never the DNI or address (privacy, Ley 29733). If that registry data is unavailable the answer is a check-digit validation with verification_level "format". Typical use: checking a Peruvian supplier or customer before paying, invoicing or onboarding it.
| Name | Type | Req | Description |
|---|---|---|---|
| ruc | string | yes | 11-digit Peru RUC, e.g. "20615614841". Spaces and dashes are ignored. |
No output schema declared.
No examples provided.
validate_tax_id Validate a business tax ID (any supported country) ~1,347
Validate a business tax or registry ID for any supported country with the deepest check available for it. Norway (organisation number), Finland (Y-tunnus or VAT), France (SIREN, SIRET or VAT), Ireland (CRO company number) and Taiwan (unified business number) are checked live against the official registry: legal name, status (active, dissolved, bankrupt, struck off and others), address, key dates, the source with its licence and the date of the data, verification_level "official_registry" and a pass/review/fail assessment with reasons. Ireland comes from CRO data updated daily, not a live query. Dominican Republic RNC (9 digits) is checked against the DGII RNC register, updated daily (legal and trade name, status, activity, payment regime); an 11-digit cédula of a natural person gets the format check only, without any name. Chile RUT is checked against the SII register of legal entities (updated a few times a year: see source.data_as_of): name, legal form, start date and término de giro (closure = fail). Canada BN (9 digits, or with a program account such as RT0001) is checked against the Corporations Canada register of federal corporations, updated daily (Open Government Licence – Canada): name, status, registered office, dates; it covers federal corporations only, so a BN not found is review, never fail. Argentina CUIT (legal entities, prefixes 30, 33, 34) is checked against the ARCA register of tax conditions: name and registration in Ganancias and IVA (registered, active or exempt, in either = pass; ARCA states no active flag). Paraguay RUC is checked against the DNIT RUC register (monthly): status, plus the name of legal entities only (natural persons: status only). Ecuador RUC (companies and other entities, third digit 6 or 9) is checked against the SRI RUC register (monthly): name, status (ACTIVO = pass, SUSPENDIDO = review, PASIVO = fail), class and dates. Natural persons of Argentina and Ecuador get the format check only (review), without any name. Brazil C…
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code, e.g. "NO", "FI", "FR", "IE", "TW", "DO", "CL", "AR", "PY", "EC", "BR", "CA", "DE", "IT", "CH", "SG", "GB", "PE". "EL" is accepted for Greece and "UK" for the United K… |
| id | string | yes | The ID as written, with or without the country prefix, spaces, dots or dashes, e.g. "974761076", "1003521-5", "FR90130004955", "98788", "03741302". |
| id_type | string | – | Optional ID type when the country has several, e.g. "siren", "siret", "vat", "ytunnus", "cro", "orgnr", "ubn", "rnc", "cedula", "rut", "bn", "ico", "uid", "uen", "crn". Detected from the input when o… |
No output schema declared.
No examples provided.
validate_tax_id_format Check tax ID format (more than 100 countries and territories) ~463
Check the format of a business tax or registry ID offline: structure and, where the issuing authority publishes one, the check digit (VIES and the registries are never queried here). Covers EU VAT numbers for all 27 member states (plus Spain NIF, France SIREN/SIRET, Finland Y-tunnus, Sweden organisationsnummer), United Kingdom VAT and company number, Switzerland UID, Norway, Iceland, Türkiye, United States EIN (structure only), Canada BN, Brazil CNPJ (including the alphanumeric format), Argentina, Chile RUT, Ecuador, Uruguay, Paraguay, Bolivia, Guatemala, Panama, Dominican Republic (RNC and cédula), Venezuela, Australia ABN/ACN, New Zealand NZBN/IRD, India GSTIN/PAN, Japan, South Korea, Taiwan, Singapore, Israel and South Africa, and 63 more countries and territories (among them China, Russia, Ukraine, Indonesia, Thailand, Vietnam, Kazakhstan, Morocco, Ghana, Kenya, Nigeria, the United Arab Emirates and Saudi Arabia; some of those have no published check digit, so only the structure is checked). Returns the normalized ID, format and check-digit validity, verification_level "format", a review/fail assessment with reasons and, when one exists, the URL of the free official lookup. No registry is queried, so the result never confirms that the business exists or is active and never returns pass.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code, e.g. "DE", "FR", "BR", "GB". "EL" is accepted for Greece and "UK" for the United Kingdom. |
| id | string | yes | The ID as written, with or without the country prefix, spaces, dots or dashes, e.g. "DE 123 456 807" or "12.345.678/9013-11". |
| id_type | string | – | Optional ID type when the country has several, e.g. "vat", "siren", "siret", "nif", "crn", "abn", "acn", "gstin", "pan", "nzbn", "ird". Detected from the input when omitted. |
No output schema declared.
No examples provided.
How do I install the HALPII Tax ID MCP server?
HALPII Tax ID is a hosted endpoint at https://taxid.halpii.com/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 · taxid.halpii.com
claude mcp add --transport http com-halpii-latam-tax-api 'https://taxid.halpii.com/mcp'
What is the HALPII Tax ID MCP server?
HALPII Tax ID is an MCP server listed in the public MCP registry as com.halpii/latam-tax-api. Tax IDs in 135 countries: official registry check in 51 (Peru, Brazil, Chile, EU VIES, UK, Japan). This page covers its hosted endpoint (https://taxid.halpii.com/mcp).
Is the HALPII Tax ID MCP server safe to use?
HALPII Tax ID scores 74 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 HALPII Tax ID MCP server expose?
HALPII Tax ID exposes 6 tools: validate_peru_ruc, validate_mexico_rfc, validate_colombia_nit, validate_costa_rica_cedula, validate_tax_id_format, validate_tax_id. Their descriptions and schemas cost roughly 2,585 tokens of context every time the server is loaded.
Does the HALPII Tax ID MCP server require authentication?
No. We connected to HALPII Tax ID without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HALPII Tax ID MCP server still maintained?
HALPII Tax ID 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 HALPII Tax ID MCP server?
VerifyMCP ran 13 checks on HALPII Tax ID, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.