GeeksHacking MCP
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tool_add_todoA | Add a single #TODO text from a source file |
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 ambiguity. The single tool has a clear and distinct purpose.
Since there is only one tool, there are no inconsistencies in naming patterns. The name itself follows snake_case convention.
A single tool is extremely limited for a server, especially when the domain is not explicitly narrow. This feels like an extreme mismatch between scope and tool count.
The server only offers a tool to add a TODO, with no tools for listing, updating, or deleting TODOs. This is a significant gap for basic task management functionality.