mcpbeat

H/M Article 50 Transparency Builder MCP Server

net.hogarmas/ai-transparency
answering

H/M Article 50 Transparency Builder is answering right now. Last checked 13 min ago. It exposes 4 tools.

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

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
194 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add ai-transparency --transport http https://agents.hogarmas.net/mcp/ai-transparency
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ai-transparency": {
      "url": "https://agents.hogarmas.net/mcp/ai-transparency"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ai-transparency]
url = "https://agents.hogarmas.net/mcp/ai-transparency"
.cursor/mcp.json
{
  "mcpServers": {
    "ai-transparency": {
      "url": "https://agents.hogarmas.net/mcp/ai-transparency"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ai-transparency": {
      "url": "https://agents.hogarmas.net/mcp/ai-transparency"
    }
  }
}

Available tools 4

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

build
build_ai_transparency_notice
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.
scan
scan_ai_transparency_surface
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.
transparency
get_ai_transparency_capabilities
Returns the free tools, accepted bounded facts, privacy behavior, source ruleset and truth boundaries before a scenario is submitted.
verify
verify_ai_transparency_manifest
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.

Endpoints

URLTransportStateLatencyChecked
https://agents.hogarmas.net/mcp/ai-transparency streamable-http answering 418 ms 13 min ago

H/M Article 50 Transparency Builder — questions

Answers built from our own checks of this server.

What can H/M Article 50 Transparency Builder do?
It exposes 4 tools, read directly from the server on our last check. Among them: build_ai_transparency_notice, get_ai_transparency_capabilities, scan_ai_transparency_surface, verify_ai_transparency_manifest. 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 →
Is H/M Article 50 Transparency Builder 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 194 ms. The bar chart above shows every period we have measured.
How do I connect H/M Article 50 Transparency Builder?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does H/M Article 50 Transparency Builder need an API key?
No. H/M Article 50 Transparency Builder completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is H/M Article 50 Transparency Builder?
It answers our handshake in 194 ms on average, which is faster than 64% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.