# Credit Card Validate — REST API endpoint `credit-card-validate`

Validate a credit card number with the Luhn checksum and detect the brand.

- Category: finance
- MCP server: https://mcp.findutils.com/ (Streamable HTTP, no API keys, 120 req/min per IP)
- REST endpoint: POST https://api.findutils.com/api/tools/credit-card-validate/execute (no API keys, 60 req/min per IP)
- Reference page: https://findutils.com/api/credit-card-validate/
- Same tool on the other surface: https://findutils.com/mcp/credit-card-validate/

## Call the endpoint (verified example)

```bash
curl -X POST https://api.findutils.com/api/tools/credit-card-validate/execute \
  -H "Content-Type: application/json" \
  -d '{
    "number": "4111111111111111"
  }'

# Parameter schema
curl https://api.findutils.com/api/tools/credit-card-validate
```

## Input schema

| Argument | Type | Required | Description |
|---|---|---|---|
| `number` | string | yes | Card number (spaces/dashes OK). |

Example arguments (verified):

```json
{
  "number": "4111111111111111"
}
```

OpenAPI 3.1 spec: https://findutils.com/api/openapi.json · Interactive docs: https://findutils.com/api/docs/

## Also an MCP tool

```bash
claude mcp add findutils --transport http https://mcp.findutils.com/
```

Then ask the client to call `findutils:credit_card_validate`. Full MCP reference: https://findutils.com/mcp/credit-card-validate/

---
Full catalog: GET https://api.findutils.com/api/tools · https://findutils.com/api/ · https://findutils.com/llms.txt