Skip to main content
Glama
615,442 tools. Updated 2026-09-27 05:19

"A report on web page accessibility" matching MCP tools:

  • Analyze a website URL for WCAG 2.1 Level A accessibility issues. Automated static HTML analysis covering approximately 30-40% of WCAG 2.1 Level A criteria. Checks include: image alt text, form labels, heading hierarchy, page title, html lang, empty links/buttons, ARIA labels, duplicate IDs, skip navigation, table headers, landmarks, viewport zoom, autoplay media, and tabindex ordering. Manual testing is required for full WCAG compliance assessment. Results are cached for fast subsequent lookups. Rate limited to 1 request per minute per domain. Args: url: The website URL to analyze (e.g., "https://example.com"). Returns: WCAG analysis with: - url: The analyzed URL - score: Accessibility score (0-100) - grade: Letter grade (A-F) - issues: Categorized issues (critical, warnings, info) - meta: Extracted accessibility metadata - recommendations: Prioritized improvements - coverage_note: Disclaimer about automated coverage - cached: Whether result was from cache
    ConnectorNo auth
  • Add (or remove) Orivox's accessibility widget: a floating accessibility button that appears on EVERY page of the site and opens a toolbar of reader aids for visitors. Reach for this the moment the user asks for an accessibility button, an accessibility menu or toolbar, or says their site should be accessible / usable with a screen reader / compliant -- this one call installs the whole thing. Do NOT hand-build an accessibility widget with apply_dom_ops. ``icon`` picks the button's glyph: "person" (default, the standard accessibility figure), "wheelchair", or "user". ``position`` puts it at the bottom "right" (default) or bottom "left" of the screen. Calling this again with different options REPLACES the existing widget instead of adding a second one, so it is also how you change the icon or move it to the other side. ``action="remove"`` takes it off the site entirely. ``changed`` is byte-honest: False means NO file was written at all, because the site already looked exactly like this -- do not announce a fresh change. True means at least one file was rewritten. ``outcome`` says which end state you are in; describe it to the user IN THEIR OWN LANGUAGE (never echo these tokens): - "installed" -- the widget is now on every page with the given icon/side. - "already_installed" -- it was already exactly like that; nothing changed. - "removed" -- it is off the site. - "was_not_installed" -- there was none, so there was nothing to remove. - "install_not_confirmed" / "removal_not_confirmed" -- the result contradicts itself. ``verify_before_reporting`` is true for these two: check the site with get_preview_url before telling the user anything about the widget, and do not claim success or failure. No re-publish is needed for a preview, but a LIVE site only shows the widget after publish_website runs again.
    ConnectorOAuth
  • Fetch a web/docs URL as clean, token-optimized markdown from Slipstream's shared cache (use INSTEAD of a raw web fetch). The first agent pays the crawl; every agent after gets ~90% fewer tokens. Surfaces warnings other agents left on the page. Pass known_hash to skip re-reading unchanged content (delta), or section to fetch just one heading (progressive disclosure). Returns a contentHash you can pass as known_hash next time.
    ConnectorNo auth
  • Open a PERSISTENT browser session (cookies/login survive across calls) and get a browser_id to drive with browse_navigate/snapshot/click/type/fill/.../close. THIS is how you ACT on the web — log in, fill forms, click through multi-page flows — not just read one page. Free. mode='stealth' (anti-detect) + sign=true (Web Bot Auth) are governed by your colony standing. Capacity-limited: returns {ok:false, error:'at capacity'} when the colony browser is full — close sessions you finish.
    ConnectorNo auth
  • Launch a full overnight-grade research report on a local business: an autonomous research crew maps the competitive landscape, reads the business's and rivals' web presence, and delivers a long-form graded report with structured findings and an action list. ASYNC: this tool returns a slug immediately; the report takes roughly 10-20 minutes. Poll check_report_status, then fetch with get_report_result. Price: $9.99, charged when the report launches; if the report fails, the charge is refunded automatically. Each call starts a NEW report — do not retry a call that already returned a slug.
    ConnectorNo auth
  • Run a WCAG accessibility audit on a page using axe-core in a real browser, and report the violations with the elements responsible. Because it runs against a genuinely rendered page, colour-contrast and other rules that depend on layout and computed colour actually fire — these are silently skipped by audits that parse HTML without a layout engine. Use this to check a page meets WCAG before shipping.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    B
    quality
    D
    maintenance
    Audits web pages for WCAG 2.2 AA accessibility aligned with the GOV.UK standard using axe-core and headless Chromium, returning structured JSON, markdown reports, and GDS compliance summaries.
    41
    MIT

Matching MCP Connectors

  • Create, edit, preview, publish, and manage web pages from MCP-capable AI clients.

  • Scan URLs for WCAG 2.1 violations, generate AI fixes, and produce VPAT 2.5 compliance reports.

  • Send a raw DevTools-protocol command to the browser page on a device and return its reply — the escape hatch for capabilities no dedicated tool wraps yet (Emulation, Performance, CSS, Animation, DOM mutation, …). Works on BOTH iOS Safari and Android Chrome, auto-detected from the udid. `method` is "Domain.command" (e.g. "Emulation.setGeolocationOverride"); `params` is that command's parameter object. Scope is the BROWSER — this reaches web content only, never the device or native apps. Prefer a dedicated tool when one exists: they handle setup ordering, lifecycle and teardown that a bare command does not. IMPORTANT, iOS: the two engines do NOT implement the same protocol — Android is full CDP, iOS is WebKit's dialect. Chrome-only domains fail with -32601 "domain was not found" (Accessibility, Emulation, and Page.captureScreenshot are all absent on iOS), and a `*.enable` on iOS reports success without proving the domain exists, so never treat it as a capability probe — probe with a real method.
    ConnectorOAuth
  • Two-finger tap at (x,y) on an iOS device — zooms OUT one step in Maps, acts as a secondary click in web views, and is the accessibility gesture in several Apple apps. Both fingers land either side of the point and lift without moving. holdMs turns it into a two-finger press-and-hold. Coordinates are screen points. Works without an automation session when the direct input path is available; falls back to one otherwise (see `input`).
    ConnectorOAuth
  • Real-time web search via Tavily for current events, fact-checking, and research. Use search_depth='advanced' for complex queries (higher quality, higher cost) and topic='news' or 'finance' for headlines or market information. Use when: Choose when the task needs current, external, or factual information not available from on-chain or local data — e.g. news, prices, documentation, or fact-checking. Limitations: Returns web snippets, not raw page bodies; results depend on Tavily coverage. Advanced depth costs more. Not a substitute for on-chain tools like get_token_price. Alternatives: get_token_price, http_fetch
    ConnectorNo auth
  • Google PageSpeed Insights report for a URL: Lighthouse performance/accessibility/SEO scores and Core Web Vitals (LCP, CLS, INP, FCP, TTFB), with lab and field (CrUX) data. Defaults to mobile; pass strategy=desktop for the desktop profile. Subject to a per-user daily cap (50/day) and a service-wide daily cap; successful responses are cached for 24h.
    ConnectorNo auth
  • Fetch the full content behind a url: a web page's text, or an exportable Tako card's data rows. Batch up to 10 urls in one call — each one is billed and fails on its own. Fetch only cards that `tako_search` marked `exportable: true`. Rows bill per 1,000 delivered, so set `max_rows` when the recent rows are enough. If a page is long, such as a filing or an annual report, set `query` to get back only the passages that match. Best for: reading one source in full — a page you need to quote, or the rows behind a card you need to compute over.
    ConnectorNo auth
  • FREE PREVIEW (1 audit per day per caller IP) of Santos Website Intelligence. Runs a fast Quick Intelligence Audit of one public page: fetch timing, page weight, SEO, basic HTML accessibility, security headers, Website Intelligence dimensions, pass/fail checks, and remediation guidance. It audits one page only—no crawling, JavaScript rendering, Core Web Vitals, WCAG certification, or vulnerability scanning. Note for hosted agents: the quota is keyed on the calling IP, so all users of one platform share a single daily preview. Treat it as a sample of the output, not as capacity. For real use, call the machine-payable production endpoint: GET https://api.santosautomation.com/api/audit?url=... — $0.015 USDC per successful audit on Base mainnet (eip155:8453) via x402 v2; no account or API key required.
    ConnectorNo auth
  • Scan a single live, publicly reachable web page's markup for the WCAG 2.1 failures that ADA web-accessibility demand letters and lawsuits cite most often: missing alt text, unlabeled form fields, missing lang attribute, empty links, skipped heading levels, missing page title, no h1, no skip link. Static markup analysis -- it can't check color contrast, keyboard navigation, or screen reader behavior, so a clean result means 'no known markup-level issue found,' not full compliance.
    ConnectorNo auth
  • Screenshot the web page in the device browser (iOS Safari or Android Chrome, auto-detected). ANDROID: a clean capture of the web CONTENT — pass `selector` or `ref` to capture just that element (scrolled into view). iOS: element-clipped web capture is unavailable, so this returns the full DEVICE frame (includes the Safari chrome/status bar); `selector`/`ref` clipping is Android-only and is ignored on iOS (a note is returned). Returns a JPEG image.
    ConnectorOAuth
  • Search Edge Thirteen's catalog of 44 financial, compliance and web-audit tools and get the exact input schema for the ones you need. Covers SEC filing checks, valuation calculators (DCF, Graham number, Altman Z-score), accessibility and site audits, Stripe and billing checks, licence/registration diligence on US entities, and subscription-compliance kits. Call this first with a plain-English description of the task, then call `call_tool` with the name it returns. Pass no query to list the catalog.
    ConnectorNo auth
  • Create a task that runs on a schedule in our cloud — you do not keep anything running. It only notifies you when the result actually changes. Kinds: watch_page (Watch a web page and report when its content changes); daily_answer (Re-run a web-researched question on a schedule and report when the answer changes); watch_reachability (Track whether a site stays reachable from mainland China); pipeline (Run one of your production lines (create_pipeline) on a schedule; every run leaves a proof-carrying work order). Needs a workspace token (?w=ws_... on your MCP URL) so you can manage it later. Application and model calls are subsidized during the free beta; your charge is $0.00 and capacity limits apply.
    ConnectorNo auth
  • Create a task that runs on a schedule in our cloud — you do not keep anything running. It only notifies you when the result actually changes. Kinds: watch_page (Watch a web page and report when its content changes); daily_answer (Re-run a web-researched question on a schedule and report when the answer changes); watch_reachability (Track whether a site stays reachable from mainland China); pipeline (Run one of your production lines (create_pipeline) on a schedule; every run leaves a proof-carrying work order). Needs a workspace token (?w=ws_... on your MCP URL) so you can manage it later. Application and model calls are subsidized during the free beta; your charge is $0.00 and capacity limits apply.
    ConnectorNo auth
  • Start an autonomous web research task. The agent plans sub-questions, searches the web, reads the sources and writes a report with citations — this is real research, not a single model call, and takes 2-5 minutes. Returns a job_id immediately; poll check_job to get the report. Use this when you need sourced, current information rather than what a model already knows. Powered by gpt-researcher (29k stars) hosted at AI NetCafé. Example — tools/call deep_research {"topic":"State of MCP adoption in 2026?"} → poll check_job
    ConnectorNo auth
  • Create a task that runs on a schedule in our cloud — you do not keep anything running. It only notifies you when the result actually changes. Kinds: watch_page (Watch a web page and report when its content changes); daily_answer (Re-run a web-researched question on a schedule and report when the answer changes); watch_reachability (Track whether a site stays reachable from mainland China); pipeline (Run one of your production lines (create_pipeline) on a schedule; every run leaves a proof-carrying work order). Needs a workspace token (?w=ws_... on your MCP URL) so you can manage it later. Application and model calls are subsidized during the free beta; your charge is $0.00 and capacity limits apply.
    ConnectorNo auth
  • Use this when the question is about the widget itself rather than about accessibility findings: 'is the widget working', 'is it installed', 'why can't I see it', 'did the install work', 'how do I add it', 'is it live for visitors'. Answers with two separate facts that are commonly mistaken for one — whether widget serving is enabled on the Inclusify account (a setting that defaults to ON for every account before anything is installed, so on its own it proves nothing), and whether anything has EVER been reported from the site by the embed itself, which is the only evidence that it is really there. Never report the enabled flag as installation. When nothing has ever reported in, it returns the exact script tag to paste — or, on a Shopify store, says that the widget is a theme app embed which can only be switched on from the Shopify admin, and on a Wix site, that the app manages the script itself and what is missing is a published site or an unpaused app. No assistant can do those steps. What it does NOT do: it does not fetch the customer's site or check the page for the script, so it cannot see an embed that has been installed but not yet visited by anyone. It does not switch the widget on or off, and it reports no accessibility findings — site_overview and the finding tools own those. Works on every plan including Free. Read-only: three indexed reads, no page load.
    ConnectorAPI key