updated 2026-10-18 00:07 UTC

MCP Accessibility Scanner

Repository

An MCP (Model Context Protocol) server for performing accessibility audits on webpages using axe-core.

MCP Servers TypeScript Listed MIT

Is MCP Accessibility Scanner safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.1 / 10
Provenance None
Signed commits 94%
Last push yesterday
Advisories None known
Compare MCP Accessibility Scanner

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: MCP Accessibility Scanner scores 70.2/100 (Grade B), ranked #350 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.1/10; 94% of recent commits are signed; no published advisory affects its latest release (mcp-accessibility-scanner); last pushed 2026-10-17. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Accessibility Scanner could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships MCP Accessibility Scanner and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/JustasMonkev/mcp-accessibility-scanner, MIT, last pushed 2026-10-17. 94% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.1/10 (scanned Oct 13, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies6
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 8
    CII-Best-Practices 0
    Code-Review 0
    Contributors 6
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 6
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 10
    Vulnerabilities 10

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: mcp-accessibility-scanner 4.0.1. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

  • 2026-08-29 OSSF Scorecard: 4.9/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues MCP Accessibility Scanner’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How MCP Accessibility Scanner compares in MCP Servers

  1. #203 Cronometer MCP 70.7 +0.5
  2. #204 Reddit MCP Buddy 70.7 +0.5
  3. #205 MCP Accessibility Scanner 70.2 this agent
  4. #206 SmartBear MCP 70.0 −0.2
  5. #207 Activitypub MCP 69.9 −0.3

Bars show each HVTrust score; the tick marks MCP Accessibility Scanner’s 70.2.

Where the 70.2 comes from

HVTrust dimensions vs the MCP Servers average

70.2 / 100 · 100.0% confidence

MCP Accessibility Scanner MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.3 / 25
1.7 above avg 10.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.8 below avg 13.6
Transparency50% declared license · 50% OSSF Scorecard
13.7 / 17
1.4 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.7 above avg 12.2
AdoptionLog-scaled stars · package downloads
8.8 / 20
1.4 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-12
Rank Moved
Rank rose 11 spots (#349 → #338)
2026-10-09
Rank Moved
Rank dropped 10 spots (#343 → #353)
2026-10-07
Rank Moved
Rank rose 22 spots (#364 → #342)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.1/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent Get email alerts for MCP Accessibility Scanner View MCP Servers Report missing data
66.2
Activity sub-score · out of 100
#205
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-18 00:07 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars
57
Forks
15
Last Push
2026-10-17
yesterday
Commits (4 wk)
176
Downloads (7d)
2,492
npm
HN mentions (30d)
—
Open Issues
7
Rank Change
=
was #350

Analysis

Activity Inputs

66.2 / 100
StarsRepository reach
10.6 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
5.6 / 20

Common questions about MCP Accessibility Scanner

MCP Accessibility Scanner has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does MCP Accessibility Scanner publish package provenance?
No published build provenance is currently detected for MCP Accessibility Scanner. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MCP Accessibility Scanner have an OpenSSF Scorecard?
MCP Accessibility Scanner has an OpenSSF Scorecard score of 6.1/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is MCP Accessibility Scanner actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does MCP Accessibility Scanner use?
MCP Accessibility Scanner ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Accessibility Scanner's commits signed?
94% of the last 100 commits to MCP Accessibility Scanner are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
MCP Accessibility Scanner appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • browser
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to MCP Accessibility Scanner's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain MCP Accessibility Scanner?

For maintainers

HVTrust scores MCP Accessibility Scanner from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 31HVTrust 3Listed 2Grade 2Scorecard 1Delisted 1MCP 1
2026-10-12
Rank Moved
Rank rose 11 spots (#349 → #338)
2026-10-09
Rank Moved
Rank dropped 10 spots (#343 → #353)
2026-10-07
Rank Moved
Rank rose 22 spots (#364 → #342)
2026-10-05
Rank Moved
Rank rose 11 spots (#374 → #363)
2026-10-01
Rank Moved
Rank rose 19 spots (#380 → #361)
2026-09-28
Rank Moved
Rank dropped 26 spots (#359 → #385)
2026-09-27
Rank Moved
Rank rose 10 spots (#369 → #359)
2026-09-24
Rank Moved
Rank rose 70 spots (#433 → #363)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 302 spots (#735 → #433)
2026-09-23
HVTrust Changed
HVTrust up 35.9pts (30.2 → 66.1)
2026-09-22
Newly Listed
First tracked at rank #735
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank rose 10 spots (#426 → #416)
2026-09-17
Rank Moved
Rank dropped 24 spots (#402 → #426)
2026-09-11
Grade Changed
Trust grade D → B
2026-09-11
Rank Moved
Rank rose 689 spots (#1089 → #400)
2026-09-11
HVTrust Changed
HVTrust up 23.5pts (43.2 → 66.7)
2026-09-09
Rank Moved
Rank dropped 14 spots (#1082 → #1096)
2026-09-07
Rank Moved
Rank dropped 32 spots (#1043 → #1075)
2026-09-06
Rank Moved
Rank dropped 15 spots (#1028 → #1043)
2026-09-05
Rank Moved
Rank dropped 42 spots (#986 → #1028)
2026-09-04
Rank Moved
Rank dropped 24 spots (#962 → #986)
2026-09-03
Rank Moved
Rank dropped 63 spots (#899 → #962)
2026-09-02
Rank Moved
Rank dropped 65 spots (#834 → #899)
2026-09-01
Rank Moved
Rank dropped 28 spots (#806 → #834)
2026-08-31
Rank Moved
Rank dropped 35 spots (#771 → #806)
2026-08-30
Rank Moved
Rank dropped 26 spots (#745 → #771)
2026-08-29
Scorecard Added
OSSF Scorecard: 4.9/10
2026-08-29
Rank Moved
Rank rose 282 spots (#1027 → #745)
2026-08-29
HVTrust Changed
HVTrust up 19.8pts (24.1 → 43.9)
2026-08-28
Rank Moved
Rank dropped 33 spots (#994 → #1027)
2026-08-27
Rank Moved
Rank dropped 24 spots (#970 → #994)
2026-08-26
Rank Moved
Rank dropped 99 spots (#871 → #970)
2026-08-22
Rank Moved
Rank rose 11 spots (#873 → #862)
2026-08-17
Rank Moved
Rank rose 11 spots (#879 → #868)
2026-08-16
Rank Moved
Rank dropped 20 spots (#859 → #879)
2026-08-12
Rank Moved
Rank rose 10 spots (#867 → #857)
2026-08-10
Rank Moved
Rank dropped 49 spots (#814 → #863)
2026-08-08
Newly Listed
First tracked at rank #810
GitHub → npm: mcp-accessibility-scanner

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 70.2 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/mcp-accessibility-scanner.svg)](https://hvtracker.net/agents/mcp-accessibility-scanner)
HTML:
<a href="https://hvtracker.net/agents/mcp-accessibility-scanner"><img src="https://hvtracker.net/badge/mcp-accessibility-scanner.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON