Accessibility pre-checks (WCAG/BFSG) in a real browser + statement drafts. Pay per call.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://a11y-api.dropcoin.workers.dev/mcp2 tools · 641msscan_accessibilityAutomated technical accessibility pre-check (WCAG 2.1/2.2 AA via axe-core) for one public https:// URL, rendered in a real headless browser, mapped to German BFSG requirements. Catches roughly 57% of WCAG violations — NOT a substitute for a manual audit and never a conformity proof. Results are cac…Automated technical accessibility pre-check (WCAG 2.1/2.2 AA via axe-core) for one public https:// URL, rendered in a real headless browser, mapped to German BFSG requirements. Catches roughly 57% of WCAG violations — NOT a substitute for a manual audit and never a conformity proof. Results are cac…
| Parameter | Type | Description |
|---|---|---|
| url* | string | — |
| standard | string | — |
| includePasses | boolean | — |
| waitMs | integer | — |
draft_statementDraft a German accessibility statement (Erklärung zur Barrierefreiheit) for a website, optionally enriched with a previous scan_accessibility result. Missing legally-required facts come back as [[PLACEHOLDERS]] you must fill in; the draft needs legal review before publication. Pure text generation,…Draft a German accessibility statement (Erklärung zur Barrierefreiheit) for a website, optionally enriched with a previous scan_accessibility result. Missing legally-required facts come back as [[PLACEHOLDERS]] you must fill in; the draft needs legal review before publication. Pure text generation,…
| Parameter | Type | Description |
|---|---|---|
| url* | string | — |
| organisation | string | — |
| contactEmail | string | — |
| scanResult | object | — |
2 of 2 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Accessibility pre-checks (WCAG/BFSG) in a real browser + statement drafts. Pay per call.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.