# secure-api MCP server

> Injects secrets into commands and API calls at runtime while sanitizing outputs to prevent sensitive data exposure to AI clients.

- Repository: https://github.com/than/secure-api-mcp
- Page: https://hostedmcp.org/servers/than/secure-api-mcp
- Transport: —
- Stars: 5

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `SECURE_API_ALLOWED_HOSTS` | no | no |  |

## Tools (5)

- `get_env_keys`
- `run_with_env`
- `api_call`
- `read_mycnf`
- `sync_env_example`

## FAQ

### How does the server protect my secrets from being seen by Claude?

The server injects secrets into commands and API calls at runtime and then sanitizes the output to strip secret values before they reach the AI's context.

### Is the sanitization of shell command output guaranteed?

No, sanitization for shell commands is best-effort. A command could potentially re-encode or transform a secret so the sanitizer does not recognize it.

### Can I restrict which hosts the api_call tool can send secrets to?

Yes, you can set the SECURE_API_ALLOWED_HOSTS environment variable to a comma-separated list of permitted hosts to gate requests that inject secrets.
