Prismfy MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRISMFY_API_KEY | Yes | API key for Prismfy Search API |
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 |
|---|---|
| prismfy_searchC | Search the web through Prismfy. Returns titles, URLs, snippets, source engines, and request metadata. |
| prismfy_quotaA | Get the current Prismfy tier, used searches, remaining searches, and quota reset date. |
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 are clearly distinct: one performs web searches, the other checks quota status. No overlapping functionality or ambiguity in purpose.
Both tools follow a consistent pattern with the 'prismfy_' prefix and lowercase_snake_case. Names clearly indicate action (search) and resource (quota), maintaining uniformity.
With only two tools, the server feels thin for a search service, but it covers the essential operations (search and quota). This aligns with the borderline range where tools are minimal yet purposeful.
The core search and quota tracking are covered, but advanced features like pagination, result filtering, or search history are absent. These are minor gaps that agents can work around for basic use cases.