Skip to content

HALPII Tax ID MCP server

com.halpii/latam-tax-apihalpii.comstreamable-httpv0.7.0Scanned

Tax IDs in 135 countries: official registry check in 51 (Peru, Brazil, Chile, EU VIES, UK, Japan).

6 tools: 6 only read.

Tools: 0 delete, 0 irreversible, 0 write, 6 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the HALPII Tax ID MCP server can do

The HALPII Tax ID MCP server is published by halpii.com, a domain the MCP Registry verified. It has 6 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

3 tools bring in text other people can write (validate_colombia_nit, validate_costa_rica_cedula and validate_tax_id).

The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 4 times since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 0.7.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Only reads 6Show 6 read-only tools
  • validate_colombia_nitValidate 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…Reads text others writeNo findings

    Why it is in this group

    • The name "validate_colombia_nit" says "validate": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Validate Colombia NIT (tax ID)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • validate_costa_rica_cedulaCheck a Costa Rican tax ID (cédula física, cédula jurídica, DIMEX or NITE) live against the Ministerio de Hacienda.Reads text others writeNo findings

    Why it is in this group

    • The name "validate_costa_rica_cedula" says "validate": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Validate Costa Rica cédula (tax ID, beta)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • validate_mexico_rfcCheck 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…No findings

    Why it is in this group

    • The name "validate_mexico_rfc" says "validate": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check Mexico RFC (tax ID)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • validate_peru_rucValidate a Peruvian RUC (11-digit tax ID) and look up the company in the SUNAT registry.No findings

    Why it is in this group

    • The name "validate_peru_ruc" says "validate": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Validate Peru RUC (tax ID)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • validate_tax_idValidate a business tax or registry ID for any supported country with the deepest check available for it.Reads text others write1 finding

    Why it is in this group

    • The name "validate_tax_id" says "validate": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 5,044 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...review). When one of these sources is down, the answer is HTTP 503 (not billed)."

      What this check looks for
    Description, as the server wrote it
    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 CNPJ is checked against the Receita Federal CNPJ register (monthly): legal name, legal nature and the head office's situação cadastral (ATIVA = pass, SUSPENSA = review, INAPTA, BAIXADA or NULA = fail); a branch never gets a pass on its own, and individual entrepreneurs (MEI) get their status only. For sole proprietorships (Norway ENK, French entrepreneurs individuels, Finnish sole traders) only the status is returned, without name or address. EU VAT numbers of 24 member states (all but Finland, France and Ireland, which have the registries above) are checked live in VIES, the VAT Information Exchange System of the European Commission: pass = the VAT number is registered for intra-EU transactions today, fail = it is not. VIES is not the trade register, so a valid VAT number does not show that the company is solvent or still registered; the name VIES returns is given only to API-key holders, and Germany and Spain share no name (legal_name null). Czechia (ARES), Latvia (Enterprise Register) and Romania (ANAF) add the legal name and status from the national register, and the company number (id_type "ico") is checked in ARES for Czechia and RPO for Slovakia. Switzerland UID (UID register, live), Israel company number (Companies Register, updated daily) and Singapore UEN (ACRA, updated monthly) are official-registry checks too. United Kingdom company numbers (id_type "crn") are checked live against the Companies House register (name, status, type, incorporation date, registered office; dissolved = fail, liquidation or administration = review); a UK VAT number gets the format check only. If VIES or a register does not answer, the tool returns an error and the call is not billed. Peru, Mexico, Colombia and Costa Rica are answered by the same lookups as their own tools. Every other covered country (including India, and Brazil, Australia, Japan and the United States while their registry switches are off) gets the offline format check with verification_level "format", which never returns pass. Also checked against official data: Australia ABN (Australian Business Register, updated weekly: active or cancelled, entity type, GST; individuals get status only); Japan corporate number (National Tax Agency, updated monthly: name, address, closure); United States EIN as a PARTIAL official source (IRS exempt organizations and SEC filers only; not found = review, never fail). Also checked against official sources: Moldova IDNO (State Register of Legal Units, updated weekly: name, legal form, liquidation; individual enterprises status only); Guernsey Registry number (live: name, type, status); Zambia TPIN (live, Zambia Revenue Authority: status, taxes incl. VAT; individuals status only); Angola NIF (live, AGT: status, in default or not, VAT regime; individuals status only); Mali NIF (live DGI list of ACTIVE taxpayers; not found = review); Seychelles TIN (live, Seychelles Revenue Commission: VAT-registered businesses only; not found = review). When one of these sources is down, the answer is HTTP 503 (not billed).

    Annotations the server declares

    • title: Validate a business tax ID (any supported country)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • validate_tax_id_formatCheck 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…No findings

    Why it is in this group

    • The name "validate_tax_id_format" says "validate": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check tax ID format (more than 100 countries and territories)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:18 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description is 5,044 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...review). When one of these sources is down, the answer is HTTP 503 (not billed)."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools4 changed.~4 changedView diff
  2. Tools1 changed.~1 changedView diff
  3. Tools2 changed.~2 changedView diff
  4. Tools5 added, 1 changed.+5 added~1 changedView diff

Install

Pinned to version 0.7.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http latam-tax-api https://taxid.halpii.com/mcp
claude mcp add --transport http latam-tax-api https://taxid.halpii.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__latam-tax-api__validate_peru_ruc",
      "mcp__latam-tax-api__validate_mexico_rfc",
      "mcp__latam-tax-api__validate_colombia_nit",
      "mcp__latam-tax-api__validate_costa_rica_cedula",
      "mcp__latam-tax-api__validate_tax_id_format",
      "mcp__latam-tax-api__validate_tax_id"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as latam-tax-api. Review it before you use it.

Capability tags behind 3 rules
  • mcp__latam-tax-api__validate_colombia_nit untrusted-input
  • mcp__latam-tax-api__validate_costa_rica_cedula untrusted-input
  • mcp__latam-tax-api__validate_tax_id untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.halpii/latam-tax-api/verify?hash=f049d538c6e3df7de94699de42a9c356a45c0a3ed2a0019460d829ca3052da76" | jq -e '.changed == false'

Pinned hash f049d538c6e3, from Nov 21, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.halpii/latam-tax-api/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.halpii/latam-tax-api
[![Anlyon Radar](https://radar.anlyon.com/badge/com.halpii/latam-tax-api.svg)](https://radar.anlyon.com/servers/com.halpii/latam-tax-api)

Source: MCP Registry. Synced Nov 21, 2026, 13:17 UTC.

HALPII Tax ID MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the HALPII Tax ID MCP server safe?

No scan can promise that. What its definitions show: 6 tools, all of which only read, and 1 finding from fixed checks. Read-only tools can still pass private data to a model.

Can the HALPII Tax ID MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the HALPII Tax ID MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the HALPII Tax ID MCP server have?

6 tools: 6 read. validate_peru_ruc, validate_mexico_rfc, validate_colombia_nit, validate_costa_rica_cedula, validate_tax_id_format and validate_tax_id.

Does the HALPII Tax ID MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the HALPII Tax ID MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the HALPII Tax ID MCP server changed its tools?

Yes, 4 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.