← Back to directory

MexCheck

MexCheck (Adrian Rangel, founder) · Compliance, Risk & Regulatory

MCP ServerCommunity

MexCheck is a hosted MCP server for Mexican identity and tax checks, including RFC validation, SAT blacklist checks, CFDI invoice status, CURP lookup, INE status and CFE receipt verification. Advisory onboarding and compliance teams could use it for checks on Mexican clients and suppliers, while accounting staff could use its taxpayer and invoice checks. It also exposes integration documentation and tools for account management, API key creation and billing.

mexicoidentity verificationtax validationkycsupplier due diligenceinvoice verification
Status
Community
Auth
OAuth
Hosting
Remote
Community rating
Not rated yet
Role

Provides one system's data and actions. Reads and writes inside a single product of record; it can act, but only within its own walls. More on System servers → All seven roles →

Open documentation →

Caveats

  • The vendor reports that lookups query government registries directly. Registry access, accuracy and coverage have not been independently verified; the pricing policy acknowledges upstream outages and requests that produce no answer.
  • The listed checks cover Mexican registries and identifiers. The source does not establish coverage outside Mexico or that these checks alone satisfy an advisory firm's KYC obligations.
  • This is not a read-only connection: vendor-listed tools can create API keys, initiate plan or balance checkouts and charge a saved card. No securities order-placement capability is listed.
  • The vendor hosts the service, so client identity and tax queries are sent to MexCheck rather than processed solely within the advisory firm. The fetched page does not specify retention, data residency or deletion policies.
  • The repository contains documentation and client configuration only, licensed under MIT. The vendor states that server source is not public and that the hosted service has separate terms.
  • Vendor-reported pricing is $0.015 USD per credit or plans starting at $99 USD per month. Lookups consume account credits; the page does not specify the credit cost of each check.
  • Start with read-only scopes and keep client-side approval prompts on until the connection is proven.
Rate this server

How to connect MexCheck

Step 1

Remote server: paste a URL

MexCheck publishes a remote (Streamable HTTP) endpoint, so nothing is installed locally. Add it as a custom connector in Claude, ChatGPT or your IDE and paste the endpoint below.

Endpoint

https://mexcheck.com/mcp

Client config snippet

{
  "mcpServers": {
    "1cd65e63-81e4-47d6-84a0-94df939c66b9": {
      "url": "https://mexcheck.com/mcp"
    }
  }
}

Step 2

Authenticate with OAuth

Your client opens a browser sign-in with the vendor. Approve only the scopes you need, and use a read-only account first when the platform offers one.

Step 3

Verify, then widen access

Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.

Prompts that use this server

Starter prompts from the Practice Stacks that rely on Compliance, Risk & Regulatory.

Compliance history and diligence file

The regulatory record a buyer's counsel will request.

Sell / M&A ReadinessCompliance, Risk & RegulatoryAdvisor & Firm Intelligence / Prospecting

Read-only: assemble my firm's regulatory record from two directions, my internal compliance or GRC systems for what they actually hold (policy versions, control testing, vendor diligence, open findings and remediation status) and the public regulatory and firm-intelligence sources for registration history, ADV disclosures and complaints. Show them side by side and flag anything disclosed publicly with no internal record, or internally tracked that the public record does not reflect. List exam findings and correspondence separately as 'to gather offline' unless a connected system genuinely holds them. Cite each source and mark anything unverified as 'to confirm'. Do not file, submit or amend anything.

Guardrail · Read-only. The internal half of this record usually lives outside any connected tool, and filings are amended through official channels only.

Diligence readiness checklist

A gap list before you open a data room.

Sell / M&A ReadinessCRMCompliance, Risk & RegulatoryAccounting & Tax

Build a diligence readiness checklist across client, financial, custody and compliance records. For each item say whether it exists today, where it lives, and what work is needed. Use read-only access, keep client identities out of the output, and do not create or share a data room or upload any document.

Guardrail · Read-only. Never let a tool export client data to an external destination.

Annual compliance review prep

A gap list against your compliance calendar.

Compliance & Audit ReadinessCompliance, Risk & RegulatoryCRM

Read-only: review my annual compliance calendar against what my connected systems can actually evidence. Use the compliance or GRC platform for the items it genuinely holds, such as policy versions, control testing, vendor diligence and open findings, and use CRM for the client-facing items, disclosure delivery, agreement dates, suitability updates and contact records for the sample under review. List Item / Owner / Due / Status / Evidence location / Source tool, and mark any calendar item that no connected system covers as 'no connected source' rather than inferring its status. Do not mark anything complete, edit records or file anything.

Guardrail · Read-only. Most servers in this category cover firm security and GRC rather than adviser books and records, so expect gaps a person has to fill.

Read the full connection guide →