mcpbeat

H/M Content Credentials Evidence Verifier MCP Server

net.hogarmas/content-credentials
answering

H/M Content Credentials Evidence Verifier is answering right now. Last checked 13 min ago. It exposes 5 tools.

Free C2PA 2.4 triage and reproducible official trust snapshot. No media, keys, or payment.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
214 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add content-credentials --transport http https://agents.hogarmas.net/mcp/content-credentials
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "content-credentials": {
      "url": "https://agents.hogarmas.net/mcp/content-credentials"
    }
  }
}
~/.codex/config.toml
[mcp_servers.content-credentials]
url = "https://agents.hogarmas.net/mcp/content-credentials"
.cursor/mcp.json
{
  "mcpServers": {
    "content-credentials": {
      "url": "https://agents.hogarmas.net/mcp/content-credentials"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "content-credentials": {
      "url": "https://agents.hogarmas.net/mcp/content-credentials"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

content
get_content_credentials_capabilities
Returns the free tools, byte limits, privacy behavior and interpretation boundaries before any evidence JSON is submitted.
run_content_credentials_self_check
Runs a deterministic, zero-input check of valid evidence, tamper detection and audit-chain verification using a synthetic fixture. No source media or caller data is used.
verify
verify_content_credentials_audit
Checks report identity, source-report digest and the local custody hash chain. It does not prove operator identity, authorship or factual truth.
verify_content_credentials_envelope
Checks the schema, privacy boundaries and canonical SHA-256 digest of an H/M evidence envelope. It does not inspect source media or authenticate an issuer.
triage
triage_c2pa_validation_statuses
Classifies up to 200 C2PA validation status observations against the complete 2.4 standard catalog, flags class mismatches, separates custom codes and returns bounded remediation. Accepts codes or crJSON-style status groups; no media, URL fetching, authentication or payment.

Endpoints

URLTransportStateLatencyChecked
https://agents.hogarmas.net/mcp/content-credentials streamable-http answering 494 ms 13 min ago

H/M Content Credentials Evidence Verifier — questions

Answers built from our own checks of this server.

What can H/M Content Credentials Evidence Verifier do?
It exposes 5 tools, read directly from the server on our last check. Among them: get_content_credentials_capabilities, run_content_credentials_self_check, triage_c2pa_validation_statuses, verify_content_credentials_audit, verify_content_credentials_envelope. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is H/M Content Credentials Evidence Verifier mostly used for?
Its tools cluster around content and verify. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is H/M Content Credentials Evidence Verifier working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 214 ms. The bar chart above shows every period we have measured.
How do I connect H/M Content Credentials Evidence Verifier?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does H/M Content Credentials Evidence Verifier need an API key?
No. H/M Content Credentials Evidence Verifier completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is H/M Content Credentials Evidence Verifier?
It answers our handshake in 214 ms on average, which is faster than 59% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.