# Pem Decoder — REST API endpoint `pem-decoder`

Parse PEM certificates, CSRs, and keys in the browser-equivalent decoder. Returns type, DER length, subject, issuer, dates, SAN, and algorithm. Private key bits are not returned.

- Category: encoding
- 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/pem-decoder/execute (no API keys, 60 req/min per IP)
- Reference page: https://findutils.com/api/pem-decoder/
- Same tool on the other surface: https://findutils.com/mcp/pem-decoder/

## Call the endpoint (verified example)

```bash
curl -X POST https://api.findutils.com/api/tools/pem-decoder/execute \
  -H "Content-Type: application/json" \
  -d '{
    "pem": "-----BEGIN CERTIFICATE-----\nMIIB\n-----END CERTIFICATE-----"
  }'

# Parameter schema
curl https://api.findutils.com/api/tools/pem-decoder
```

## Input schema

| Argument | Type | Required | Description |
|---|---|---|---|
| `pem` | string | yes | One or more PEM blocks including BEGIN and END lines. |

Example arguments (verified):

```json
{
  "pem": "-----BEGIN CERTIFICATE-----\nMIIB\n-----END CERTIFICATE-----"
}
```

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:pem_decoder`. Full MCP reference: https://findutils.com/mcp/pem-decoder/

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