ProofBase MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Your Anthropic API key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_testimonialA | Generate a realistic customer testimonial for a product. Creates a fictional but believable testimonial with customer details, suitable for social proof. |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has consistent naming, as there are no other tools to compare against. The name 'generate_testimonial' follows a clear verb_noun pattern.
One tool is too few for a server named 'ProofBase MCP Server', which suggests a broader scope related to social proof or testimonials. A single tool feels thin and limited for this apparent domain.
The server's name implies a domain of social proof or testimonials, but with only a generation tool, there are significant gaps. Missing operations like retrieving, updating, deleting, or managing testimonials make the surface severely incomplete for the inferred purpose.