RepoGraph-Honest MCP Server
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_fileB | Scan a file for potential hallucinations: undefined symbols, missing imports, and incorrect API calls. Args: file_path: Absolute path to the Python 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 a single tool, there is no possibility of confusion or overlap between tools. The purpose of scan_file is clearly isolated and distinct.
Only one tool exists, so consistency is trivially satisfied. The name follows a sensible verb_noun pattern (scan + file) that would fit well if more tools were added.
A single trivial tool for a server named 'RepoGraph-Honest' is extremely thin. Scanning individual files for hallucinations is a narrow capability that does not justify an MCP server's scope.
The tool only scans a single file at a time with no support for scanning directories, repos, or batch operations. There are no complementary tools for viewing results history, scanning modules, or handling related analysis tasks, leaving significant gaps in the stated purpose.