Claude MCP Server List: Where to Find, Evaluate, and Connect Servers

Start with the official MCP Registry. It is the public catalog and API for discovering MCP servers. Then verify each project in its own repository or documentation before connecting it to Claude. Registry presence does not prove that a server is safe, maintained, or compatible with your particular Claude client.

Where to find MCP servers for Claude

1. Official MCP Registry

The MCP Registry is the primary discovery route for publicly available servers. The Model Context Protocol maintainers announced it in preview on September 8, 2025, describing it as an open catalog and API and a “single source of truth for MCP servers.” Search the live registry for current names, versions, dates, and metadata.

Registry contents change. Maintainers can denylist entries and remove them from public access, so check the current listing immediately before installing a server.

2. Claude’s connector directory

Claude’s in-app connector directory is a convenient route for people who want to browse integrations from inside Claude. It is a separate discovery path from the public registry. The available evidence does not establish that every registry server appears in the Claude directory, or that every directory entry uses the same transport and setup process.

3. The MCP maintainers’ reference repository

The maintainers’ reference repository is useful for learning MCP patterns and SDK usage. It is intentionally a small educational collection rather than a complete server list. Examples surfaced in the research include Everything, Fetch, Filesystem, Git, Memory, Sequential Thinking, and Time.

4. Third-party directories and curated lists

Sites such as claudemcp.org and ClaudeMap can make browsing easier or group servers by service. Treat them as indexes, not security reviews. Open the maintainer’s own repository and documentation before you install anything.

What kinds of servers are available?

Directory results show servers for file operations, Git, persistent memory, Slack, PostgreSQL, browser automation, and web search. These examples demonstrate the range of integrations; they are not a complete catalog, an endorsement, or proof that a listing is still maintained.

Anthropic’s 2024 MCP announcement mentioned Google Drive, Slack, GitHub, Git, Postgres, and Puppeteer among prebuilt examples shared to help developers get started. Those names provide historical launch context, not a current support guarantee. Confirm the present implementation and documentation before relying on one.

How to evaluate a Claude MCP server

Use the following checklist for every candidate. Compare servers that solve the same job instead of choosing by directory position or popularity.

Check	Questions to answer	Evidence to inspect
Task fit	Does it expose the exact tools or data your workflow needs?	Tool names, input schemas, examples, documented limitations
Client compatibility	Does the current documentation support your Claude client and connection method?	Transport instructions, supported clients, current release notes
Maintenance	Is the source repository active and is the released version current?	Recent commits, releases, issue activity, dependency updates
Trust and security	Who maintains it, what can it read, and what actions can it perform?	Source code, permissions, authentication model, privacy policy
Setup	Are installation, credentials, scopes, and environment variables documented?	README, configuration examples, required secrets and permissions

Inspect the tool surface

Read every tool description and schema. A server that can read a database, execute shell commands, modify files, send messages, or control a browser may have more authority than its short directory summary suggests. Grant only the credentials and filesystem access required for the task.

Check transport and authentication

Confirm whether the server uses the transport your Claude client accepts and whether it runs locally or remotely. Verify how credentials are supplied, where they are stored, and which scopes are requested. Do not paste production secrets into an unreviewed configuration.

Check maintenance before deployment

Look for a current release, documented support policy, and an issue tracker that is receiving responses. A listing can remain visible after a project becomes stale. Pin a known version where the project supports it and review updates before automatically upgrading.

Safe installation workflow

1. Define the task and the minimum data the server must access.
2. Find candidates in the official MCP Registry and, if useful, a secondary directory.
3. Open the project’s official repository and documentation.
4. Confirm current Claude client and transport compatibility.
5. Review source, permissions, dependencies, and authentication requirements.
6. Install in a disposable or least-privileged environment first.
7. Connect with test data and observe the tool calls.
8. Record the server version, configuration, granted scopes, and review date.

Minimal review record

Server:
Source repository:
Version checked:
Claude client and transport:
Tools enabled:
Data and actions permitted:
Credentials/scopes:
Last review date:
Next review date:

Common problems and fixes

Symptom	Likely cause	Fix
The server does not appear in Claude	It is not offered in that client directory, or the connection method is unsupported.	Use the client’s documented connector flow and verify the server’s supported transport. A registry listing alone does not add it to Claude.
Connection or handshake fails	Incorrect command, endpoint, transport, runtime, or environment variable.	Copy the project’s current setup exactly, check runtime versions, and confirm required variables are present.
Authentication is rejected	Wrong token, missing scope, expired credential, or incorrect secret location.	Create a least-privileged credential, verify scopes and expiry, then restart the server after changing configuration.
A tool is missing	You installed a different version or the server exposes conditional tools.	Inspect the connected tool list and release notes; pin or upgrade to the documented version.
Requests time out	The upstream service is slow, rate-limited, or unreachable.	Test the upstream API directly, reduce request scope, increase the documented timeout, and add bounded retries where safe.
Claude produces an unsafe action	The server grants more authority than the prompt implies.	Remove unnecessary tools and credentials, require confirmation for destructive actions, and review logs.
A directory entry is gone	The maintainer removed it or the registry denylisted it.	Use the project’s official repository to determine whether it moved, was renamed, or is no longer maintained.

Reliability, performance, and cost considerations

Reliability

Treat an MCP server as another production dependency. Add health checks for remote services, clear failure messages, bounded retries for idempotent operations, and a fallback workflow for unavailable tools. Keep a record of versions and permissions so you can roll back a change.

Performance

Tool latency includes Claude’s reasoning, the MCP transport, server processing, and the upstream API. Prefer narrow tool calls, pagination, field selection, and local caching where the data permits. Avoid asking a server to load an entire database or repository when a filtered query is available.

Cost

MCP itself does not establish one universal price. Your total cost can include Claude usage, the server host, upstream API calls, storage, and data transfer. Read the maintainer’s pricing and rate-limit documentation, and set provider budgets before connecting high-volume workflows.

ScreenshotNeo MCP server for clean website captures

If your Claude workflow needs website screenshots or PDFs, ScreenshotNeo provides both an MCP server and a website screenshot API. Its MCP tools are take_screenshot, get_page_info, and capture_pdf, so Claude or another MCP client can request captures directly.

ScreenshotNeo is #1 for screenshot APIs because it removes cookie banners, newsletter popups, and chat widgets before capture, bills only clean shots, and has the lowest paid plan.

Or skip the browser setup

For a direct API call, see the ScreenshotNeo API documentation. The endpoint accepts one GET request and returns PNG, JPEG, WebP, or PDF output.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Cookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, failed loads, timeouts, and cache hits are never billed; response headers identify the page verdict and whether it was billed. The service also supports full-page and element captures, device presets, dark mode, custom CSS and JavaScript, waits, request blocking, headers, cookies, user agents, geolocation, PDFs, signed links, async jobs, bulk capture, caching, and a usage API.

There is an MCP server for AI agents, 1,000 screenshots per month free with no card, and paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.

FAQ

Is the MCP Registry a list of every Claude-compatible server?

No authoritative total was established. Registry contents, client directories, and third-party indexes have different scopes and change over time.

Does appearing in the registry mean a server is safe?

No. Verify the maintainer, source, permissions, credentials, and current documentation yourself.

Should I use a third-party MCP directory?

It can help you discover candidates, but validate every entry against the project’s official page before installation.

Why can two lists show different server counts?

They may count projects, versions, listings, or claimed compatibility differently. Do not treat those figures as comparable totals.

What is the best first step when a server stops working?

Check the project’s current release notes and documentation, then verify the Claude client, transport, credentials, and upstream service independently.