H/M Content Credentials Evidence Verifier MCP Server

by hogarmas Your server? Claim it

answering

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

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

Uptime history 90 days of history · worst day 91%

90 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

80 ms

Response time

average over 24h

authentication required

Access

streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 August 2026. No other catalogue keeps this.

11 Aug a tool changed version

H/M Content Credentials Evidence Verifier missed 2 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add content-credentials --transport http https://agents.hogarmas.net/mcp/content-credentials

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "content-credentials": {
      "type": "http",
      "url": "https://agents.hogarmas.net/mcp/content-credentials"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Available tools 7

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

content

create_content_credentials_policy_profile

Creates one versioned policy profile from a fixed preset and optional rule overrides. It accepts no source media or evidence and does not authenticate the policy author.

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.

verify_content_credentials_policy_decision

Checks the policy checksum, decision checksum, every per-item rule outcome and aggregate counts. It does not inspect source media, authenticate the sender or certify compliance.

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

URL	Transport	State	Latency	Checked
https://agents.hogarmas.net/mcp/content-credentials	streamable-http	needs auth	41 ms	10 min ago

Alternatives to H/M Content Credentials Evidence Verifier

same job, measured the same way

H/M Article 50 Transparency Builder

by hogarmas

Free Article 50 website scanner, notice builder, and checksum verifier. No key or payment.

4 tools answering

EMET

by dreamforgestudiollc

0.3.2. Free MIT; no account, key, or payment. Verifies record, not computation. Stable error codes.

339 installs/wk local only

SDK

by mnemopay

Trust OS for AI agents: governed memory, payments, reputation, approvals, and audit evidence.

local only

Machine Works Broker

by dailytekk

Free evidence capability discovery, quotes and durable unmet requests. No payment or spend.

6 tools answering

MUJ428 Trust Layer — Bind Approved Intent to Verified Effect

by wmujahid428-web

Payment-rail-independent intent-to-effect integrity for consequential agent actions.

2 tools answering

x402 Triage MCP

by tatelyman

MCP server for no-payment x402 surface triage, 402 Index health checks, and paid review handoff.

38 installs/wk local only

Anyway Possible Paid Agent Utilities

by anyway-possible

Paid x402 tools for merchant intelligence, Base payment readiness, and verifiable web evidence.

9 tools answering

x402 Pay — USDC API Payment Helper

by scriptmasterlabs

Pay for APIs with USDC. Read-only x402 payment discovery, verification, evidence, and status.

5 tools answering

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 7 tools, read directly from the server on our last check. Among them: create_content_credentials_policy_profile, get_content_credentials_capabilities, run_content_credentials_self_check, triage_c2pa_validation_statuses, verify_content_credentials_audit, verify_content_credentials_envelope and 1 more. 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 80 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 in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does H/M Content Credentials Evidence Verifier need an API key?

Yes. Every time we knock, H/M Content Credentials Evidence Verifier answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is H/M Content Credentials Evidence Verifier?

It answers our handshake in 80 ms on average, which is faster than 95% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.