H/M Content Credentials Evidence Verifier
REMOTE · AGENTS.HOGARMAS.NET
Free C2PA 2.4 triage and reproducible official trust snapshot. No media, keys, or payment.
Available components
Last scanned (11 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 572 tokens (~44/item across 13 items; 7 tools + 6 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
- Structured output schemas are declared (14% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Aug 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 12 Aug 26 0
- Server version: 2.34.0 → 2.35.0 functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- Server version: 2.33.0 → 2.34.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://agents.hogarmas.net/mcp/content-credentials
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hogarmas.net | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 2350b9bd64da80a31330f41faa265e9f |
| SANs: hogarmas.net, agents.hogarmas.net, *.agents.hogarmas.net | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of agents.hogarmas.net. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| net. | DS published | 37331 | 13 | Verified |
| hogarmas.net. | DS published | 2371 | 13 | Verified |
| agents.hogarmas.net. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agents.hogarmas.net/mcp/content-credentials | Verified | 200 | |
| http (plaintext) | http://agents.hogarmas.net/mcp/content-credentials | HTTPS enforced | 301 | https://agents.hogarmas.net/mcp/content-credentials |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_content_credentials_policy_profile Create a checksum-bound evidence policy profile ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| actions | object | – | Optional allow, review or hold overrides keyed by a published policy rule ID |
| name | string | – | – |
| preset | string | – | – |
| purpose | string | – | – |
No output schema declared.
No examples provided.
get_content_credentials_capabilities Read Content Credentials verification boundaries ~31
Returns the free tools, byte limits, privacy behavior and interpretation boundaries before any evidence JSON is submitted.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_content_credentials_self_check Run the Content Credentials evidence self-check ~43
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
triage_c2pa_validation_statuses Interpret C2PA 2.4 validation status codes ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| codes | array | – | Unclassified C2PA status code strings |
| statusCodes | object | – | crJSON-style success, informational and failure arrays |
| Name | Type | Req | Description |
|---|---|---|---|
| affectedDomains | array | yes | – |
| counts | object | yes | – |
| items | array | yes | – |
| limitations | object | yes | – |
| privacy | object | yes | – |
| ruleset | string | yes | – |
| schema | string | yes | – |
| source | object | yes | – |
| state | string | yes | – |
| summary | string | yes | – |
No examples provided.
verify_content_credentials_audit Verify an H/M audit evidence envelope ~59
Checks report identity, source-report digest and the local custody hash chain. It does not prove operator identity, authorship or factual truth.
| Name | Type | Req | Description |
|---|---|---|---|
| envelope | object | yes | Privacy-minimized H/M evidence JSON envelope. Source media is not accepted. |
No output schema declared.
No examples provided.
verify_content_credentials_envelope Verify an H/M evidence envelope checksum ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| envelope | object | yes | Privacy-minimized H/M evidence JSON envelope. Source media is not accepted. |
No output schema declared.
No examples provided.
verify_content_credentials_policy_decision Verify an H/M evidence policy decision ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| decision | object | yes | H/M policy decision JSON exported by the browser-local Evidence Policy Lab |
No output schema declared.
No examples provided.
How do I install the H/M Content Credentials Evidence Verifier MCP server?
H/M Content Credentials Evidence Verifier is a hosted endpoint at https://agents.hogarmas.net/mcp/content-credentials, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agents.hogarmas.net
claude mcp add --transport http net-hogarmas-content-credentials 'https://agents.hogarmas.net/mcp/content-credentials'
What is the H/M Content Credentials Evidence Verifier MCP server?
H/M Content Credentials Evidence Verifier is an MCP server listed in the public MCP registry as net.hogarmas/content-credentials. Free C2PA 2.4 triage and reproducible official trust snapshot. No media, keys, or payment. This page covers its hosted endpoint (https://agents.hogarmas.net/mcp/content-credentials).
Is the H/M Content Credentials Evidence Verifier MCP server safe to use?
H/M Content Credentials Evidence Verifier scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the H/M Content Credentials Evidence Verifier MCP server expose?
H/M Content Credentials Evidence Verifier exposes 7 tools: get_content_credentials_capabilities, triage_c2pa_validation_statuses, run_content_credentials_self_check, verify_content_credentials_envelope, verify_content_credentials_audit, and 2 more. Their descriptions and schemas cost roughly 442 tokens of context every time the server is loaded.
Does the H/M Content Credentials Evidence Verifier MCP server require authentication?
No. We connected to H/M Content Credentials Evidence Verifier without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the H/M Content Credentials Evidence Verifier MCP server still maintained?
H/M Content Credentials Evidence Verifier is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the H/M Content Credentials Evidence Verifier MCP server?
VerifyMCP ran 13 checks on H/M Content Credentials Evidence Verifier, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.