# H/M C2PA Validation Status Code Interpreter

Browser-local and agent-callable triage for C2PA Content Credentials 2.4 validation status codes.

## Human tool

- Page: https://hogarmas.net/content-credentials/status-codes/
- Static catalog: https://hogarmas.net/content-credentials/status-code-catalog.json
- Result schema: https://hogarmas.net/content-credentials/status-code-triage-schema.json
- Standard source: https://spec.c2pa.org/specifications/specifications/2.4/specs/ContentCredentials.html#_standard_status_codes
- crJSON source: https://spec.c2pa.org/specifications/specifications/2.4/crJSON/crjson-format.html

The catalog contains the complete C2PA 2.4 status tables:

- 16 success codes
- 15 informational codes
- 84 failure codes
- 115 standard codes total

Custom codes are permitted by C2PA but are emitter-defined, so this tool never invents a standard meaning for an unknown namespace.

## Focused MCP

- Endpoint: `https://agents.hogarmas.net/mcp/content-credentials`
- Server Card: `https://agents.hogarmas.net/.well-known/mcp/content-credentials/server-card.json`
- Tool: `triage_c2pa_validation_statuses`
- Prompt: `triage-c2pa-statuses`
- Authentication: none
- Payment: none
- Source media accepted: false

Call with an unclassified list:

```json
{
  "codes": [
    "claimSignature.validated",
    "algorithm.deprecated",
    "assertion.dataHash.mismatch"
  ]
}
```

Or preserve crJSON grouping:

```json
{
  "statusCodes": {
    "success": [
      { "code": "claimSignature.validated" }
    ],
    "informational": [
      { "code": "algorithm.deprecated" }
    ],
    "failure": [
      { "code": "assertion.dataHash.mismatch" }
    ]
  }
}
```

The result includes:

1. Overall observed state.
2. Counts by standard class.
3. Standard, custom or invalid-format classification.
4. Reported-class mismatch detection.
5. Evidence domain and official English meaning.
6. Bounded next action.
7. Explicit privacy and interpretation limits.

URLs and caller-supplied explanations are not returned. Aggregate MCP invocation and declared-client metrics may be retained without raw IP addresses or submitted status-code content.

## Interpretation boundaries

- This tool does not validate an asset or manifest.
- This tool does not inspect source media.
- This tool does not verify a claim signature.
- This tool does not establish signer or timestamp-authority trust.
- This tool does not detect AI generation.
- This tool does not determine factual truth.
- Missing failure codes do not prove that full validation ran.
- A custom code remains emitter-defined until its namespace documentation is consulted.