| Transport | Package | Auth | |||
|---|---|---|---|---|---|
M mcp-server-fear-greed An MCP server for mcp-server-fear-greed | SSEstdio+1 | npm | Required | 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.