Back to Browse

Mcp MCP Server

Developer ToolsModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

5.2
Moderate5.2Moderate Risk

The MadTaco MCP server is well-designed with proper authentication controls, clean code structure, and appropriate input validation. The server correctly gates paid/authenticated tools behind API key requirements, and API keys are handled securely via environment variables. Permissions align well with its purpose as a verification API client. Minor code quality observations exist but do not materially impact security. Supply chain analysis found 4 known vulnerabilities in dependencies (1 critical, 3 high severity). Package verification found 1 issue.

7 files analyzed ยท 8 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

MadTaco API base URL (default: https://api.madtaco.dev/v1)Optional

Environment variable: MADTACO_API_BASE

X-Api-Key for paid checks, usage, and proposals (free tools work without it)Required

Environment variable: MADTACO_API_KEY

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "dev-madtaco-mcp": {
      "env": {
        "MADTACO_API_KEY": "your-madtaco-api-key-here",
        "MADTACO_API_BASE": "your-madtaco-api-base-here"
      },
      "args": [
        "-y",
        "@madtaco/mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

๐ŸŒฎ 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.

Reviews

No reviews yet

Be the first to review this server!