mcp-hardened
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Echo a message back. Smoke test only. |
| search_filesD | Read a note from the sandbox directory. |
| query_recordsA | Look up records by category. |
| fetch_docA | Fetch the text of a document at a URL. |
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 4 tools
Each tool has a clearly distinct purpose: ping for smoke testing, search_files for reading a note, query_records for searching records, and fetch_doc for retrieving a URL. There is no overlap or ambiguity between them.
Three tools follow a verb_noun pattern (search_files, query_records, fetch_doc), but 'ping' is a standalone command and 'search_files' is misleading since it actually reads a note rather than searching files. This mixing of conventions reduces consistency.
The four tools form a compact and well-scoped set for a lightweight server, covering a smoke test, file access, record lookup, and URL fetching without unnecessary bloat.
The toolset offers read operations for different resources but lacks discovery methods (e.g., listing notes, categories, or available URLs) and any write capabilities. This limits the ability to perform full workflows without prior external knowledge.