ATSPI-MCP-Server

Provides an MCP server that reads Linux accessibility tree/state via ATSPI (Assistive Technology Service Provider Interface), exposing system accessibility context to an MCP client.

Evaluated Apr 04, 2026 (16d ago)
Repo ↗ Infrastructure mcp modelcontextprotocol atspi linux accessibility automation rust security-review
⚙ Agent Friendliness
38
/ 100
Can an agent use this?
🔒 Security
24
/ 100
Is it safe for agents?
⚡ Reliability
28
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
45
Documentation
40
Error Messages
0
Auth Simplicity
95
Rate Limits
0

🔒 Security

TLS Enforcement
20
Auth Strength
20
Scope Granularity
10
Dep. Hygiene
50
Secret Handling
30

Security posture is unclear from the provided materials. There is no described auth/scopes, and ATSPI access may expose sensitive information about the user interface/system state. The README notes AppArmor can block atspi communication, implying the service interacts with privileged system interfaces; such deployments should be carefully permissioned and reviewed. Dependency hygiene and secret handling cannot be verified from the provided excerpts.

⚡ Reliability

Uptime/SLA
0
Version Stability
40
Breaking Changes
50
Error Recovery
20
AF Security Reliability

Best When

You control the Linux environment and want an agent to query current accessibility state through MCP.

Avoid When

You cannot grant the necessary ATSPI/DBus accessibility permissions or need strong authentication/authorization around the MCP endpoint.

Use Cases

  • Generate or inspect accessibility tree/context for automation or UI understanding
  • Assistive-technology-aware agents that need system state
  • Debugging/observability of UI accessibility state on Linux

Not For

  • Production-grade security-sensitive deployments without review
  • Environments where ATSPI access is blocked (e.g., certain sandbox/AppArmor configurations)
  • Non-Linux platforms

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication or authorization mechanism is described in the provided README; likely depends on the MCP transport/host configuration rather than app-level auth.

Pricing

Free tier: No
Requires CC: No

No pricing information provided; appears to be open-source tooling.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • ATSPI/AT-SPI communication can be blocked by AppArmor/sandboxing; run the server outside certain sandboxed environments (README calls out Electron/VSCode scenarios).
  • Accessibility tree retrieval may be slow or fail depending on desktop accessibility services/permissions; agents should anticipate transient failures.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for ATSPI-MCP-Server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered