pure.md MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUREMD_API_KEY | No | Your pure.md API token. Set to empty string ("") to use anonymously with lower rate limits. |
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 |
|---|---|
| unblock-urlD | – |
| search-webD | – |
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 2 tools
The two tools have clearly distinct purposes: search-web appears to perform web searches, while unblock-url likely handles URL unblocking or access. There is no overlap in functionality, making them easy to differentiate.
Both tools follow a consistent verb-noun naming pattern (search-web and unblock-url), using lowercase with hyphens. This uniformity makes the tool set predictable and easy to understand.
With only 2 tools, the server feels under-scoped for a general-purpose MCP server named 'pure.md'. This minimal set may lack coverage for common tasks, making it potentially insufficient for broader use cases.
Given the server name 'pure.md' and tools focused on web search and URL unblocking, there are significant gaps. For a markdown or documentation-related domain, expected tools like create, edit, or render markdown are missing, severely limiting functionality.