driftcheck
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FORGEJO_URL | No | The base URL of your Forgejo instance used for repo claims. | http://127.0.0.1:3000 |
| FORGEJO_TOKEN | No | Forgejo API token. Alternatively read from ~/.config/forgejo-token.env. Without a token, private repos report as not found. | |
| DRIFTCHECK_SCOPE | No | Active scope for scoped claims; equivalent to the --scope option. Scoped claims are skipped unless the scope is active. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_docsA | Check factual claims (file paths, local ports, systemd units, Forgejo repos) in markdown
docs or directories of docs against the live system. Returns drifted claims with file:line and why.
Set include_ok=true to also list claims that verified fine. Claims tagged
|
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
There is only one tool, so misselection between tools is impossible. Its purpose (verifying factual claims in markdown against the live system) is clearly stated and bounded.
check_docs follows the verb_noun snake_case convention cleanly. With a single tool there is no risk of mixing naming styles.
The server is narrowly scoped to one operation, so a single tool is defensible rather than an oversight. However, a bare 1-tool surface is thin, and the described functionality (scope filtering, include_ok, single file vs directory) hints at variants that could have been separate tools.
The core check operation is fully described, covering paths, ports, systemd units, and Forgejo repos with line-level reporting. Gaps remain: there is no way to discover available scopes or list claims without running a full check, no ignore/configuration operation, and no separate mode for previewing what would be checked.