H/M Content Credentials Evidence Verifier
REMOTE · AGENTS.HOGARMAS.NET · SCANNED AUG 3
Free C2PA 2.4 triage and reproducible official trust snapshot. No media, keys, or payment.
Available components
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 →
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability78
- 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 400 tokens (~40/item across 10 items; 5 tools + 5 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (20% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · agents.hogarmas.net
claude mcp add --transport http net-hogarmas-content-credentials https://agents.hogarmas.net/mcp/content-credentials
[mcp_servers.net-hogarmas-content-credentials] url = "https://agents.hogarmas.net/mcp/content-credentials"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-hogarmas-content-credentials": {
"type": "remote",
"url": "https://agents.hogarmas.net/mcp/content-credentials",
"enabled": true
}
}
} openclaw mcp add net-hogarmas-content-credentials --url https://agents.hogarmas.net/mcp/content-credentials --transport streamable-http
mcp_servers:
net-hogarmas-content-credentials:
url: "https://agents.hogarmas.net/mcp/content-credentials" {
"mcpServers": {
"net-hogarmas-content-credentials": {
"type": "http",
"url": "https://agents.hogarmas.net/mcp/content-credentials"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 69
First indexed and scored.
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 3 Aug 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 | 9 Jul 2026 | 7 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 70cfd0e9c007c22a13114afc0389e0e3 |
| 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 |
DNSSEC secure
Validation of agents.hogarmas.net. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| hogarmas.net. | present | 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 |
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.
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.