@curatedmcp/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CURATEDMCP_APP_URL | No | Override with CURATEDMCP_APP_URL for local development against a different deployment. | https://curatedmcp.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_mcp_catalogA | Search the CuratedMCP catalog of human-reviewed, risk-classified MCP servers by keyword and/or category. Use this before installing an unfamiliar MCP server to see if a vetted alternative already exists. |
| get_mcp_server_detailsA | Fetch the full risk profile for a single MCP server in the CuratedMCP catalog: risk level, declared capabilities (file access, network egress, shell exec, etc.), compatible clients, transport type, and install command. |
| check_mcp_server_verifiedA | Quick lookup: given a server name or its npm package (e.g. '@org/some-mcp-server'), report whether it's in the CuratedMCP verified catalog. Useful right before running an unfamiliar |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: verifying existence, fetching full details, and searching the catalog. No overlap in functionality.
All tool names follow a consistent verb_noun pattern (check_, get_, search_) with snake_case, making them predictable and easy to understand.
With 3 tools, the set is well-scoped for querying a catalog, fitting within the ideal 3-15 range. Each tool serves a necessary function without redundancy.
The toolset covers the core use cases for interacting with a curated MCP server catalog: verifying a server, getting detailed risk profiles, and searching. No obvious gaps for its intended purpose.