H/M Article 50 Transparency Builder
REMOTE · AGENTS.HOGARMAS.NET · SCANNED SEP 20
Free Article 50 website scanner, notice builder, and checksum verifier. No key 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 → 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. 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 Usability79
- 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 509 tokens (~63/item across 8 items; 4 tools + 4 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 12% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the H/M Article 50 Transparency Builder MCP server?
H/M Article 50 Transparency Builder is a hosted endpoint at https://agents.hogarmas.net/mcp/ai-transparency, 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-ai-transparency 'https://agents.hogarmas.net/mcp/ai-transparency'
{
"mcpServers": {
"net-hogarmas-ai-transparency": {
"url": "https://agents.hogarmas.net/mcp/ai-transparency"
}
}
} {
"servers": {
"net-hogarmas-ai-transparency": {
"type": "http",
"url": "https://agents.hogarmas.net/mcp/ai-transparency"
}
}
} [mcp_servers.net-hogarmas-ai-transparency] url = "https://agents.hogarmas.net/mcp/ai-transparency"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-hogarmas-ai-transparency": {
"type": "remote",
"url": "https://agents.hogarmas.net/mcp/ai-transparency",
"enabled": true
}
}
} openclaw mcp add net-hogarmas-ai-transparency --url 'https://agents.hogarmas.net/mcp/ai-transparency' --transport streamable-http
mcp_servers:
net-hogarmas-ai-transparency:
url: "https://agents.hogarmas.net/mcp/ai-transparency" {
"McpServers": {
"net-hogarmas-ai-transparency": {
"Transport": "http",
"Url": "https://agents.hogarmas.net/mcp/ai-transparency"
}
}
} assistant mcp add net-hogarmas-ai-transparency -t streamable-http -u 'https://agents.hogarmas.net/mcp/ai-transparency'
{
"mcpServers": {
"net-hogarmas-ai-transparency": {
"type": "http",
"url": "https://agents.hogarmas.net/mcp/ai-transparency"
}
}
} 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.
- 31 Aug 26 +1
- Stability: 0.97 → pass security
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 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
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 20 Sept 2026 · Probed https://agents.hogarmas.net/mcp/ai-transparency
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 | 6 Sept 2026 | 5 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 437398d9600040ab0e5bd171842448ba |
| 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. | 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 |
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/ai-transparency | Verified | 200 | |
| http (plaintext) | http://agents.hogarmas.net/mcp/ai-transparency | HTTPS enforced | 301 | https://agents.hogarmas.net/mcp/ai-transparency |
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 →
build_ai_transparency_notice Build an EU AI Act Article 50 notice ~268
Maps bounded deployment facts to a review-oriented Article 50 assessment and returns deployable HTML plus a privacy-minimized checksummed manifest. Omitted facts are treated as unsure. No names, model identifiers or free text are accepted.
| Name | Type | Req | Description |
|---|---|---|---|
| accessibleDisclosureTested | string | – | – |
| contentTypes | array | – | – |
| deepfake | string | – | – |
| detectionTested | string | – | – |
| directInteraction | string | – | – |
| editorialResponsibility | string | – | – |
| emotionOrBiometric | string | – | – |
| euExposure | string | – | – |
| humanExposure | string | – | – |
| humanOversightLevel | string | – | – |
| interactionObvious | string | – | – |
| locale | string | – | Output language. Defaults to English. |
| machineReadableMarkImplemented | string | – | – |
| marketEntryDateDocumented | string | – | – |
| placedOnMarketBefore20260802 | string | – | – |
| professionalUse | string | – | – |
| publicInterestText | string | – | – |
| recordsMaintained | string | – | – |
| role | string | – | – |
| standardEditingOnly | string | – | – |
| substantiveHumanReview | string | – | – |
| syntheticContent | string | – | – |
| visibleDisclosureImplemented | string | – | – |
No output schema declared.
No examples provided.
get_ai_transparency_capabilities Read Article 50 notice-builder boundaries ~36
Returns the free tools, accepted bounded facts, privacy behavior, source ruleset and truth boundaries before a scenario is submitted.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_ai_transparency_surface Scan observable Article 50 evidence on a public website ~73
Reads bounded static homepage signals from one public HTTP or HTTPS website. Returns observed, not-observed and manual-review evidence without source text, a compliance score or legal certification. Private and local networks are blocked.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public HTTP or HTTPS website to scan, for example https://example.com |
No output schema declared.
No examples provided.
verify_ai_transparency_manifest Verify an H/M AI transparency manifest checksum ~54
Checks the schema and canonical SHA-256 digest of an H/M AI transparency deployment manifest. It does not authenticate an issuer or certify legal compliance.
| Name | Type | Req | Description |
|---|---|---|---|
| manifest | object | yes | H/M AI transparency deployment manifest JSON. |
No output schema declared.
No examples provided.
What is the H/M Article 50 Transparency Builder MCP server?
H/M Article 50 Transparency Builder is an MCP server listed in the public MCP registry as net.hogarmas/ai-transparency. Free Article 50 website scanner, notice builder, and checksum verifier. No key or payment. This page covers its hosted endpoint (https://agents.hogarmas.net/mcp/ai-transparency).
Is the H/M Article 50 Transparency Builder MCP server safe to use?
H/M Article 50 Transparency Builder scores 85 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 Article 50 Transparency Builder MCP server expose?
H/M Article 50 Transparency Builder exposes 4 tools: get_ai_transparency_capabilities, scan_ai_transparency_surface, build_ai_transparency_notice, verify_ai_transparency_manifest. Their descriptions and schemas cost roughly 431 tokens of context every time the server is loaded.
Does the H/M Article 50 Transparency Builder MCP server require authentication?
No. We connected to H/M Article 50 Transparency Builder without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the H/M Article 50 Transparency Builder MCP server still maintained?
H/M Article 50 Transparency Builder is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.