MCP Easy Copy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| _________available_mcp_services_for_easy_copy_________B | List all MCP services available in this Claude instance |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| mcp-services-list |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose: listing available MCP services.
With only one tool, naming consistency is inherently perfect. The tool name follows a descriptive snake_case pattern that clearly indicates its function.
A single tool is too few for most practical server purposes, as it severely limits functionality. While the tool's purpose is clear, the server feels incomplete and under-scoped with just one operation.
The server is severely incomplete for any meaningful domain. With only a listing tool and no actual copy or manipulation capabilities, there are significant gaps that will prevent agents from performing useful work beyond basic discovery.