Damn Vulnerable MCP Server Demo
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 |
|---|---|
| additionD | Sum tool |
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 'addition' has a single, clearly defined purpose of summing numbers, so an agent can easily identify and select it without ambiguity.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'addition' follows a simple noun pattern, which is appropriate for its function, and there are no other tools to compare it against for inconsistency.
A single tool is too few for most server purposes, making the server feel thin and limited in scope. While the tool 'addition' is straightforward, a server with only one basic arithmetic operation lacks the depth expected for meaningful agent interactions, indicating a mismatch with typical MCP server expectations.
The server's domain appears to be arithmetic or mathematical operations, but with only an addition tool, it is severely incomplete. There are obvious gaps, such as missing subtraction, multiplication, division, or other basic operations, which would cause agent failures when attempting broader mathematical tasks.