Skip to main content
Glama
oneprofile-dev

@curatedmcp/mcp

Check if an MCP server is verified in the CuratedMCP catalog

check_mcp_server_verified

Check whether an MCP server name or npm package is listed in the CuratedMCP verified catalog before running an unfamiliar install command.

Instructions

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 npx <package> MCP server install command.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameOrPackageYesServer display name or npm package name to check
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations; description says it's a quick lookup reporting verification status. Lacks details on error handling, response format, or any side effects. Adequate but minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with 'Quick lookup'. Every sentence earns its place—no unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, use case, and parameter. Missing explicit return value description, but for a simple boolean lookup, description is largely complete. Output schema absent reduces burden.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single parameter nameOrPackage is described in schema; description adds clarifying example (@org/some-mcp-server) and restates acceptable inputs. Adds value beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb ('check'/'report') and resource (verification status in CuratedMCP catalog). Distinguishes from siblings by focusing on quick lookup vs details or search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States when to use ('right before running an unfamiliar npx MCP server install command'). No explicit when-not-to-use or sibling comparison, but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/oneprofile-dev/curatedmcp-catalog-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server