MadTaco

Verification and trust checks for AI agents: validate, screen, propose, accounts, usage.

OtherJavaScriptv1.1.0

๐ŸŒฎ MadTaco โ€” MCP Server

npm: @madtaco/mcp

smithery badge

Verification and utility API for AI agents. Validate tax IDs, screen sanctions, verify companies, inspect domains โ€” prepaid USD credits. Failed checks are never charged.

This package is a stdio MCP server that wraps the public MadTaco API at https://api.madtaco.dev/v1. Every response includes credits_charged (0 for free operations). Prefer remote HTTP instead? See HTTP MCP below.

Docs

Quick start (stdio)

npx @madtaco/mcp

Claude Desktop / Cursor

Claude Desktop config: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows).
Cursor: .cursor/mcp.json in your project or global MCP settings.

{
  "mcpServers": {
    "madtaco": {
      "command": "npx",
      "args": ["-y", "@madtaco/mcp"],
      "env": {
        "MADTACO_API_KEY": "your_api_key_here"
      }
    }
  }
}

Without an API key: validate_tax_id, validate_iban, lookup_instrument, validate_email (syntax), validate_phone (format), create_account, verify_account.

With an API key (tier registered): get_usage, propose_check.

Funded account required (tier 2): paid screening/verification tools and validate_email/validate_phone full modes. Top up via POST /v1/billing/checkout or madtaco.dev billing.

Rate limits: 50 req/day anonymous (per IP), 100 req/day registered (per API key), 500/day included once funded โ€” see llms.txt.

Try it

Validate the Chilean RUT 11.111.111-1 using MadTaco.

Check whether IBAN DE89370400440532013000 is valid.

Look up ticker CMG on exchange US.

Remote HTTP

Streamable HTTP MCP on the API subdomain โ€” no npm install required:

{
  "mcpServers": {
    "madtaco": {
      "url": "https://api.madtaco.dev/mcp",
      "headers": { "X-Api-Key": "your_api_key_here" }
    }
  }
}

Authenticate with X-Api-Key or Authorization: Bearer. Same 13 tools as this stdio package.

Environment

VariableRequiredDefault
MADTACO_API_KEYFor authenticated and paid toolsโ€”
MADTACO_API_BASENohttps://api.madtaco.dev/v1

Override for staging or local dev:

"env": { "MADTACO_API_BASE": "https://api.madtaco.dev/v1" }

Tools

All paths are relative to MADTACO_API_BASE (default https://api.madtaco.dev/v1).

ToolAPI endpointCredits
validate_tax_idPOST /validate/tax-id0
validate_ibanPOST /validate/iban0
lookup_instrumentPOST /lookup/instrument0
validate_emailPOST /validate/email0 (syntax) / 0.005 (full, tier 2)
validate_phonePOST /validate/phone0 (format) / 0.005 (full, tier 2)
screen_sanctionsPOST /screen/sanctions0.10
verify_companyPOST /verify/company0.15
inspect_domainPOST /inspect/domain0.05
screenPOST /screen + optional GET /screens/{id}?wait=60sum of completed checks
propose_checkPOST /proposepledge hold only
create_accountPOST /accounts0
verify_accountPOST /accounts/verify0
get_usageGET /usage0

Not in MCP (REST only)

Call these directly against the API โ€” see llms.txt:

  • GET /data/cl/{indicator} โ€” Chilean indicators (UF, UTM, USD, EUR, IPC)
  • GET /balance โ€” credit balance (get_usage includes balance)
  • GET /evidence/{id} โ€” signed evidence URLs
  • GET /health โ€” uptime check

Agent onboarding flow

  1. create_account with an email โ†’ account_id + pending_verification
  2. Human or agent reads the 6-digit code from email
  3. verify_account โ†’ api_key (tier registered)
  4. Fund the account via madtaco.dev billing or POST /v1/billing/checkout
  5. Set MADTACO_API_KEY and run paid checks

Credentials never transit through MCP responses for human dashboard access โ€” use POST /v1/accounts/invite-human when needed.

Development

Stdio transport only โ€” this server calls the public HTTP API; no database or secrets beyond an optional API key.

git clone https://github.com/madtaco-dev/mcp.git
cd mcp
npm install
npm test
npm run build
MADTACO_API_KEY=... npm run dev

New tools ship as minor npm releases as the API grows. See llms.txt for the current tool list.

License

MIT ยฉ ๐ŸŒฎ MadTaco ยท Built for agents, literally.

Installation

Source-derived launch command. Check the maintainerโ€™s required arguments and credentials before running:

bash
npx -y @madtaco/mcp

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "dev-madtaco-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@madtaco/mcp"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the clientโ€™s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

@madtaco/mcpnpm

Compatible MCP Clients

MadTaco works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More