pure.md MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUREMD_API_KEY | No | Your pure.md API token for higher rate limits. Can be set to an empty string for anonymous usage. |
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 easily distinguishable.
Both tools follow a consistent verb-noun pattern with hyphen separation (e.g., 'search-web', 'unblock-url'), and they use clear, action-oriented verbs. There are no deviations in naming style.
With only 2 tools, the server feels thin and likely incomplete for a web-related domain. This minimal set suggests significant gaps in coverage, such as missing operations for browsing, filtering, or managing search results.
Inferred as a web search/access server, the toolset is severely incomplete. It lacks core operations like retrieving search results, handling pagination, or managing blocked URLs beyond unblocking. This will likely cause agent failures in typical workflows.