MCP

Appearance

Free Scanner Setup Guide ​

Get started with the QualiBooth Free URL Scanner HTTP MCP server in minutes.

Overview ​

The QualiBooth Free URL Scanner is an HTTP-based MCP server that allows you to scan any website for accessibility issues without requiring an account or API key.

Quick Start ​

1. Configure Your MCP Client ​

Add the HTTP MCP server to your client configuration:

Claude Desktop ​

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent location:

json
{
  "mcpServers": {
    "qualibooth-free-scanner": {
      "transport": "http",
      "url": "https://mcp.qualibooth.com/mcp/free"
    }
  }
}

Cursor ​

Add to your MCP settings:

json
{
  "servers": {
    "qualibooth-free-scanner": {
      "transport": "http",
      "endpoint": "https://mcp.qualibooth.com/mcp/free"
    }
  }
}

Other HTTP MCP Clients ​

javascript
const mcpClient = new MCPClient({
  transport: 'http',
  endpoint: 'https://mcp.qualibooth.com/mcp/free'
});

2. Restart Your AI Client ​

Restart your AI assistant to load the new server configuration.

3. Start Scanning ​

You can now use the free_scan_url tool:

Please scan https://www.qualibooth.com for accessibility issues

Configuration Details ​

Transport Configuration ​

The server uses HTTP transport with these settings:

  • Protocol: HTTPS
  • Endpoint: https://mcp.qualibooth.com/mcp/free
  • Authentication: None required
  • Content-Type: application/json

Client-Specific Setup ​

Claude Desktop (Windows) ​

Configuration file location:

%APPDATA%\Claude\claude_desktop_config.json

Claude Desktop (Linux) ​

Configuration file location:

~/.config/claude/claude_desktop_config.json

VS Code with MCP Extension ​

Add to settings.json:

json
{
  "mcp.servers": {
    "qualibooth-free-scanner": {
      "transport": "http",
      "url": "https://mcp.qualibooth.com/mcp/free"
    }
  }
}

First Scan ​

Test the Setup ​

Try scanning a well-known website:

Scan https://qualibooth.com for accessibility issues

Expected Response ​

The AI assistant should:

  1. Call the free_scan_url tool
  2. Receive formatted results
  3. Display score badge, top fixes, and impact summary

Example Interaction ​

User: Check https://stripe.com for accessibility

Assistant Response:

🟢 Score: 89/100 — Low lawsuit risk
_Scanned: https://stripe.com_

## Top Fixes

1. 🟡 **focus-order-semantics** — Focus order doesn't follow semantic order (4 elements) — [Learn more](https://dequeuniversity.com/rules/axe/4.8/focus-order-semantics)
2. 🟢 **label-title-only** — Form elements use title attribute for labeling (2 elements) — [Learn more](https://dequeuniversity.com/rules/axe/4.8/label-title-only)
3. 🟢 **bypass** — Multiple ways to navigate to main content missing (1 element) — [Learn more](https://dequeuniversity.com/rules/axe/4.8/bypass)

**Impact Summary:** 🔴 Critical: 0 · 🟠 High: 0 · 🟡 Medium: 4 · 🟢 Low: 3

📸 [View page screenshot](https://screenshots.qualibooth.com/stripe.png)

> _Want more scans, scheduled monitoring, and full dashboards? [Subscribe to QualiBooth](https://qualibooth.com)_

Troubleshooting Setup ​

Common Issues ​

Server Not Found ​

Symptoms: "Unable to connect to MCP server" errors

Solutions:

  1. Verify the URL: https://mcp.qualibooth.com/mcp/free
  2. Check internet connectivity
  3. Ensure HTTPS is accessible (no firewall blocking)

Configuration Errors ​

Symptoms: Server appears but tools not available

Solutions:

  1. Validate JSON syntax in configuration
  2. Ensure transport: "http" is specified
  3. Restart the AI client completely

Permission Errors ​

Symptoms: Can't edit configuration files

Solutions:

  1. Run editor with appropriate permissions
  2. Check file ownership and permissions
  3. Use administrator access if required

Testing Connection ​

You can test the MCP server endpoint directly:

bash
curl -X POST https://mcp.qualibooth.com/mcp/free \
  -H "Content-Type: application/json" \
  -d '{"method":"tools/list"}'

Expected response:

json
{
  "tools": [
    {
      "name": "free_scan_url",
      "description": "Scan a website for accessibility violations..."
    }
  ]
}

Advanced Configuration ​

Custom Headers ​

Some clients allow custom headers:

json
{
  "mcpServers": {
    "qualibooth-free-scanner": {
      "transport": "http",
      "url": "https://mcp.qualibooth.com/mcp/free",
      "headers": {
        "User-Agent": "My-MCP-Client/1.0"
      }
    }
  }
}

Timeout Settings ​

Configure request timeouts for slow connections:

json
{
  "mcpServers": {
    "qualibooth-free-scanner": {
      "transport": "http",
      "url": "https://mcp.qualibooth.com/mcp/free",
      "timeout": 30000
    }
  }
}

Retry Configuration ​

For unreliable networks:

json
{
  "mcpServers": {
    "qualibooth-free-scanner": {
      "transport": "http",
      "url": "https://mcp.qualibooth.com/mcp/free",
      "retries": 3,
      "retryDelay": 1000
    }
  }
}

Rate Limiting ​

Free Tier Limits ​

  • 5 scans per hour per IP address
  • 1 concurrent scan per IP
  • 24-hour data retention for scan results

Handling Rate Limits ​

When rate limited, you'll see:

Error: Free scan limit exceeded. Please try again later or upgrade to QualiBooth Pro.

Strategies:

  1. Prioritize scans - Test most important pages first
  2. Spread scans - Use across the hour, not all at once
  3. Upgrade - Consider Pro plan for unlimited scans

Best Practices ​

Effective Scanning ​

  1. Start Small - Test individual pages, not entire sites
  2. Focus Critical Paths - Checkout, login, main content pages
  3. Iterative Testing - Fix issues, then re-scan
  4. Document Results - Keep track of accessibility scores over time

URL Selection ​

Good candidates:

  • Landing pages
  • Checkout flows
  • User registration
  • Main navigation pages
  • Contact forms

Avoid:

  • Admin dashboards (require authentication)
  • Very large pages (timeout risk)
  • Dynamic single-page apps (may not render fully)

Integration Workflows ​

Development Workflow ​

  1. Initial Scan: Establish baseline accessibility score
  2. Fix Issues: Address high-impact violations first
  3. Re-scan: Verify improvements
  4. Monitor: Regular scans on key pages

Content Management ​

  1. Pre-publish: Scan new pages before going live
  2. Template Testing: Check design templates
  3. Component Testing: Verify reusable components
  4. Regression Testing: Ensure changes don't break accessibility

Next Steps ​

After Setup ​

  1. Test Key Pages: Scan your most important user journeys
  2. Establish Baselines: Document current accessibility scores
  3. Create Action Plan: Prioritize fixes based on impact
  4. Set Monitoring: Schedule regular scans for critical pages

Advanced Features ​

Consider upgrading for:

  • More scans - No hourly limits
  • Historical data - Track accessibility over time
  • Scheduled monitoring - Automated regular scans
  • Team collaboration - Multiple users, shared results
  • Advanced reporting - Detailed analytics and exports

Support Resources ​

Documentation ​

Getting Help ​

Troubleshooting Checklist ​

  • [ ] Configuration JSON is valid
  • [ ] HTTPS endpoint is accessible
  • [ ] AI client has been restarted
  • [ ] Rate limit not exceeded
  • [ ] URL being scanned is publicly accessible
  • [ ] No firewall blocking outbound HTTPS

Migration from Other Tools ​

If you're switching from other accessibility scanners:

Lighthouse Integration ​

The QualiBooth scanner uses axe-core, similar to Lighthouse's accessibility audit. Results should be comparable.

axe-core Direct Usage ​

If you currently use axe-core directly, the MCP server provides:

  • Same engine - Consistent results
  • Simplified interface - No setup required
  • Formatted output - Ready-to-display results
  • Screenshot integration - Visual context for issues

Browser Extensions ​

Unlike browser extensions that work on loaded pages, the MCP server:

  • Server-side rendering - More consistent results
  • No browser setup - Works from any environment
  • API integration - Can be automated and scripted
  • Historical tracking - Compare results over time

Copyright © 2025 QualiBooth