| Transport | Package | Auth | |||
|---|---|---|---|---|---|
R registry-mcp An MCP server that serves informtaion from the official MCP registry | SSEHTTP | remote | No signal | Sep 9, 2025 | |
L lighthouse-mcp MCP server for Google Lighthouse performance metrics | stdio | npm | No signal | Sep 9, 2025 | |
A atest-mcp-server Auto-download & launch https://github.com/LinuxSuRen/atest-mcp-server | stdio | npm | No signal | Sep 9, 2025 | |
T try Create guides as MCP servers to instruct coding agents to use your software (library, API, etc). | HTTP | remote | No signal | Sep 9, 2025 | |
S sec-edgar-mcp SEC EDGAR MCP server that provides access to the US public filings through the US SEC EDGAR API | stdio | pip | Required | Sep 9, 2025 | |
M memory-mcp MCP server for AI memory management using Letta - Standard MCP format | stdio | npm | Required | Sep 9, 2025 | |
M mcp-server-search MCP server for web search operations | SSEstdio+1 | npm | Required | Sep 9, 2025 | |
M mcp-server-filesystem MCP server for filesystem access | SSEstdio+1 | npm | Required | Sep 9, 2025 | |
M mcp-server-commands An MCP server to run arbitrary commands | SSEstdio+1 | npm | Required | Sep 9, 2025 | |
M mcp-server-browser MCP server for browser use access | SSEstdio+1 | npm | Required | Sep 9, 2025 | |
G google-analytics-mcp An MCP server that provides [describe what your server does] | stdio | pip | Required | Sep 9, 2025 | |
M mcp-sap-docs Fast MCP server for unified SAP docs search (SAPUI5, CAP, OpenUI5, wdi5) with BM25 full-text search | stdio | npm | No signal | Sep 9, 2025 | |
M mcp-trino MCP server for Trino distributed SQL query engine access | stdio | mcpb | Required | Sep 9, 2025 | |
M meta-api-mcp-server You can connect any API to LLMs. This enables AI to interact directly with APIs | stdio | npm | Required | Sep 9, 2025 | |
M mcp-server-fear-greed An MCP server for mcp-server-fear-greed | SSEstdio+1 | npm | Required | Sep 9, 2025 | |
D dialer An MCP server that provides lets you make outbound phone calls using your own phone number | SSEHTTP | remote | No signal | Sep 9, 2025 |
An MCP server exposes tools, resources, or prompts that an AI client can call through the Model Context Protocol. Servers can connect models to apps, databases, files, APIs, search systems, and internal workflows.
The MCP Registry is a searchable directory of Model Context Protocol servers. Drio uses registry metadata to show server profiles, install details, auth signals, and discovered tools where available.
Open an MCP profile, choose your client, then copy the generated configuration or endpoint into Claude, Codex, Cursor, VS Code, or another MCP-compatible client.
Registry profiles show live metadata and discovery results, not a safety endorsement. Review the source link, auth requirements, and configuration before connecting a server to your client.
Most profiles include install snippets for common MCP-compatible clients such as Claude Desktop, Claude Code, Codex, Cursor, VS Code, Windsurf, and Cline. Use the profile page to copy the client-specific config.
Check the source repository, endpoint, transport, package, auth requirement, and discovered tools. If a server needs credentials, review the provider and scopes before adding it to a client.
Some MCP servers require OAuth, API keys, session credentials, or another provider-specific login before tools, resources, and prompts can be listed. Drio shows public inventory when the server exposes it.
Tools are callable actions, resources are readable context such as files or records, and prompts are reusable instructions exposed by a server. These fields help humans and AI agents understand what a server can actually do.
Yes. The registry pages expose names, summaries, install details, auth signals, endpoints, and discovered capabilities in a structured format so humans and AI agents can compare MCP servers more easily.
The registry is synced regularly from upstream metadata, then enriched when public endpoint discovery is available. Individual profile pages show the latest metadata and captured capabilities we have for that server.
Search by product, use case, tool name, package, transport, or auth requirement. Open promising profiles and compare the install instructions, source link, and captured tools before connecting one to your client.