Site Scanner MCP Server — Claude Code setup guide

Use Evinced Site Scanner MCP from Claude Code and ask about your accessibility scan results without leaving the terminal. Claude Code uses the Evinced Site Scanner connector of the Claude organization you sign in with, so there’s nothing to install.

The setup at a glance

Part 1 · Before you start

Once per organization, then once each

1. Get the connector
2. Sign in to Claude Code

Part 2 · Start using it

Everyone, once each

3. Connect your Evinced account
4. Confirm the connection
5. Ask a real question

You need a Claude Pro, Max, Team or Enterprise plan, an up-to-date Claude Code (claude update), an Evinced Site Scanner account, and about 5 minutes.

Don't add the server with claude mcp add

Evinced’s sign-in accepts Claude Code only through claude.ai. If you add https://site-scanner-mcp.evinced.io/mcp directly with claude mcp add, signing in fails with Callback URL mismatch. Use the connector, as below.

Part 1 · Before you start

Step 1 · Get the connector

Claude Code uses the connectors of the Claude organization you’re signed in to, so Evinced Site Scanner must be one of them.

• Claude Team or Enterprise: an Owner adds it once for everyone. Follow Part 1 of the Claude setup guide.

• Claude Pro or Max: add it yourself on claude.ai.

  1. Open Customize › Connectors and choose Add › Add custom connector.

  2. Name: Evinced Site Scanner

  3. MCP server URL:

     https://site-scanner-mcp.evinced.io/mcp

  4. Click Continue, keep the sign-in settings claude.ai detects, and click Add.

Step 2 · Sign in to Claude Code

Claude Code loads your organization’s connectors only when it’s signed in with your claude.ai account, not with an API key or through a cloud provider such as Amazon Bedrock.

1. Check how Claude Code is signed in:

   claude auth status

   Look for "authMethod": "claude.ai", and for the organization that has the connector in orgName.

2. If it shows something else, sign in with your claude.ai account:

   claude auth login

   If authMethod still isn’t claude.ai, for example third_party, a setting in your environment such as ANTHROPIC_API_KEY or CLAUDE_CODE_USE_BEDROCK points Claude Code elsewhere. Remove it and check again.

Part 2 · Start using it

Everyone does this once, each with their own Evinced account.

Step 3 · Connect your Evinced account

Tip

Already connected the connector on claude.ai (step 6 of the Claude guide)? Then it’s connected in Claude Code too once you restart it, and you can skip this step.

1. List your MCP servers:

   claude mcp list

   The connector shows up with a claude.ai prefix:

   claude.ai Evinced Site Scanner: https://site-scanner-mcp.evinced.io/mcp - ! Needs authentication

2. Start the sign-in:

   claude mcp login "claude.ai Evinced Site Scanner"

   Your browser opens a claude.ai page that takes you to the Evinced sign-in. On a machine without a browser, such as over SSH, add --no-browser and follow the prompts.

3. Sign in with your Evinced account.

4. If Claude Code is running, restart it. claude mcp list now shows the connector as ✔ Connected.

Step 4 · Confirm the connection

The whoami tool only reads. It’s the quickest way to check which account Claude Code is using.

1. Start Claude Code in any folder and ask:

   Use the Evinced Site Scanner connector to run its whoami tool.

2. Claude Code asks before it uses the tool. Choose Yes, or Yes, and don’t ask again for tools you trust.

3. Claude Code replies with your Evinced account and tenant.

Step 5 · Ask a real question

Ask in plain language. Claude Code picks the Site Scanner tool that fits.

1. Ask about your sites, for example:

   List my Evinced Site Scanner properties with their latest scan date and score.

2. Claude Code runs the matching tool and answers from your live Site Scanner data.

Good to know

• Every tool only reads your Evinced data except Create Property, which adds a property to your account.
• Everyone signs in as themselves. Claude Code sees only what your Evinced account can access.

If something goes wrong

What you see	What to do
Evinced Site Scanner isn’t in claude mcp list	Claude Code isn’t signed in with a claude.ai account whose organization has the connector. Check step 1 and step 2. On Team or Enterprise, ask an Owner to check the connector’s Roles with access. Claude Code also skips connectors when ENABLE_CLAUDEAI_MCP_SERVERS is false or the disableClaudeAiConnectors setting is on.
The connector shows ! Needs authentication	Connect your Evinced account (step 3).
“Callback URL mismatch” when you sign in	The server was added with claude mcp add. Remove it with claude mcp remove <name> and use the connector instead.
Wrong Evinced account	On claude.ai, open the connector in Customize › Connectors, choose ⋮ › Disconnect, then connect again and restart Claude Code. The sign-in asks for your credentials each time. Don’t choose Remove from your team: that removes it for everyone.

Still stuck?

Email support@evinced.com and include the connector URL, https://site-scanner-mcp.evinced.io/mcp.

That’s it

Evinced Site Scanner is ready in Claude Code. Each person connects their own Evinced account once.

How to use itWhat to ask once it's connected, with example prompts.

Claude setup guideAdd the connector to your Claude organization.

Privacy policyWhat the Site Scanner MCP Server handles, and why.