H/M Content Credentials Evidence Verifier MCP server
net.hogarmas/content-credentialshogarmas.netstreamable-httpv1.2.0Scanned
Free C2PA 2.4 triage and reproducible official trust snapshot. No media, keys, or payment.
7 tools: 6 change things and 1 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- 4 findings
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the H/M Content Credentials Evidence Verifier MCP server can do
The H/M Content Credentials Evidence Verifier MCP server is published by hogarmas.net, a domain the MCP Registry verified. It has 7 tools. It can create or change data (6 tools: triage_c2pa_validation_statuses, run_content_credentials_self_check, verify_content_credentials_envelope, verify_content_credentials_audit and 2 more), but cannot delete data. 1 tool only reads.
1 tool reads private data (get_content_credentials_capabilities).
The fixed checks matched 4 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 21, 2026, version 1.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 6Claude Code: ask
create_content_credentials_policy_profileCreates one versioned policy profile from a fixed preset and optional rule overrides.1 finding
Why it is in this group
- The name "create_content_credentials_policy_profile" says "create": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "create_content_credentials_policy_profile" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "create_content_credentials_policy_profile" says "create": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
run_content_credentials_self_checkRuns a deterministic, zero-input check of valid evidence, tamper detection and audit-chain verification using a synthetic fixture.2 findings
Why it is in this group
- The name "run_content_credentials_self_check" says "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The title mentions "Credentials".
What this check looks forMatched text
title: "Run the Content Credentials evidence self-check"
- Warn
The server marks "run_content_credentials_self_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_content_credentials_self_check" says "run": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
triage_c2pa_validation_statusesClassifies up to 200 C2PA validation status observations against the complete 2.4 standard catalog, flags class mismatches, separates custom codes and returns bounded remediation.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
verify_content_credentials_auditChecks report identity, source-report digest and the local custody hash chain.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Checks report identity, source-report digest and the local custody hash chain. It does not prove operator identity, authorship or factual truth.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
verify_content_credentials_envelopeChecks the schema, privacy boundaries and canonical SHA-256 digest of an H/M evidence envelope.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
verify_content_credentials_policy_decisionChecks the policy checksum, decision checksum, every per-item rule outcome and aggregate counts.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
get_content_credentials_capabilitiesReturns the free tools, byte limits, privacy behavior and interpretation boundaries before any evidence JSON is submitted.Reads private data1 finding
Why it is in this group
- The name "get_content_credentials_capabilities" says "get": a word for reading.
What it can reach
- private-dataThe name "get_content_credentials_capabilities" says "get" and "credential": it reads secrets.
Findings
- Info
The title mentions "Credentials".
What this check looks forMatched text
title: "Read Content Credentials verification boundaries"
Description, as the server wrote it Returns the free tools, byte limits, privacy behavior and interpretation boundaries before any evidence JSON is submitted.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:23 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://agents.hogarmas.net/mcp/content-credentials: tools/list returned 7 tools to an anonymous client, including triage_c2pa_validation_statuses (write), run_content_credentials_self_check (write), verify_content_credentials_envelope (write), verify_content_credentials_audit (write), create_content_credentials_policy_profile (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "run_content_credentials_self_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_content_credentials_self_check" says "run": a word for a change.
The server marks "create_content_credentials_policy_profile" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "create_content_credentials_policy_profile" says "create": a word for a change.
The title mentions "Credentials".
What this check looks forMatched text
title: "Read Content Credentials verification boundaries"
The title mentions "Credentials".
What this check looks forMatched text
title: "Run the Content Credentials evidence self-check"
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http content-credentials https://agents.hogarmas.net/mcp/content-credentialsclaude mcp add --transport http content-credentials https://agents.hogarmas.net/mcp/content-credentialsRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__content-credentials__get_content_credentials_capabilities"
],
"ask": [
"mcp__content-credentials__triage_c2pa_validation_statuses",
"mcp__content-credentials__run_content_credentials_self_check",
"mcp__content-credentials__verify_content_credentials_envelope",
"mcp__content-credentials__verify_content_credentials_audit",
"mcp__content-credentials__create_content_credentials_policy_profile",
"mcp__content-credentials__verify_content_credentials_policy_decision"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as content-credentials. Review it before you use it.
Capability tags behind 1 rule
- mcp__content-credentials__get_content_credentials_capabilities private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/net.hogarmas/content-credentials/verify?hash=24a2b85e13c7f3244af95c611a27f7263d61f2fe675f2764534a12cf509039ac" | jq -e '.changed == false'Pinned hash 24a2b85e13c7, from Nov 21, 2026, 06:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/net.hogarmas/content-credentials/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/net.hogarmas/content-credentials)Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.
H/M Content Credentials Evidence Verifier MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the H/M Content Credentials Evidence Verifier MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 6 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the H/M Content Credentials Evidence Verifier MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the H/M Content Credentials Evidence Verifier MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the H/M Content Credentials Evidence Verifier MCP server have?
- 7 tools: 6 write, 1 read. triage_c2pa_validation_statuses, run_content_credentials_self_check, verify_content_credentials_envelope, verify_content_credentials_audit, create_content_credentials_policy_profile, verify_content_credentials_policy_decision and get_content_credentials_capabilities.
Does the H/M Content Credentials Evidence Verifier MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the H/M Content Credentials Evidence Verifier MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the H/M Content Credentials Evidence Verifier MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.