mcp-servers (Six production-minded MCP servers)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | Optional GitHub token to improve GitHub rate limits. Never returned or logged. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookupC | Retrieve CV evidence with BM25+dense reciprocal-rank fusion. |
| verify_claimC | Verify claims and attach exact spans to each supported one. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| answer-from-cv | Prepare an evidence-only answer with exact CV citations. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| structured-profile | The complete versioned profile and atomic evidence chunks. |
| retrieval-corpus | The independently citable chunks indexed by both retrievers. |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: lookup retrieves evidence, while verify_claim checks claims against that evidence. There is no ambiguity or overlap in their roles.
Both tool names are imperative verbs, but 'lookup' is a single word while 'verify_claim' follows a verb_noun pattern. This is a minor deviation, and the names are still predictable and readable.
With only two tools, the set feels slightly thin for a production-oriented server. However, the narrow scope of evidence retrieval and verification may justify the small number, making it borderline appropriate.
The two tools form a logical pipeline: retrieve evidence first, then verify claims against it. Minor gaps might exist, such as a way to browse or filter evidence sources, but the core workflow appears covered.