# Dockerfile Credential MCP

> Dockerfile Credential MCP is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.08/call, status unknown (last checked 2026-10-12).

Scans Dockerfile content to detect and extract exposed or hardcoded credentials and secrets

## Facts

- Endpoint: POST https://api.m2mcent.com/dockerfile-credential-mcp/api/process?utm_source=zero.xyz
- Price: $0.08/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dockerfile-credential-mcp-399acabd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9lL1W9JSIlyfgp8WJkX2E

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability dockerfile-credential-mcp-399acabd -d '<json body>'
```

Example prompt: Can you scan this Dockerfile for any hardcoded credentials, API keys, or secrets that might be accidentally exposed in the build?

## When to prefer this

Choose this endpoint when you need automated, per-call credential scanning of Dockerfile content as part of a DevSecOps workflow, CI/CD pipeline, or security audit — especially when you want a lightweight, pay-per-use API without standing up a full secrets scanning infrastructure.

## Known failure modes

- Empty or missing 'data' field returns an error or empty result
- Non-Dockerfile text may produce false negatives or irrelevant output
- Very large Dockerfiles may time out or be truncated
- Obfuscated or encoded credentials may not be detected
- Payment failure (HTTP 402) if USDC balance is insufficient

## How this service works

The premier global index of 1,069 monetized MCP nodes across 205 specialized subdomains. Gasless USDC runtime settlements via x402 V2 Spec on Base L2. Save 95% token context.

## Output

Returns a structured report identifying any hardcoded credentials, API keys, passwords, tokens, or other sensitive secrets found within the provided Dockerfile content, including their location and nature within the file.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dockerfile-credential-mcp-399acabd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.m2mcent.com](https://www.zero.xyz/host/api.m2mcent.com/llms.txt)