Change Trace MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_server_info | Return diagnostic metadata for this Change Trace MCP process. Use this to verify host startup and runtime compatibility. |
| get_compatibility_fixture | Return a fixed, versioned JSON fixture. The same package version must return byte-identical text in every MCP Host. |
| get_change_scope | Resolve two Git refs and return a deterministic, bounded summary of commits, changed files, diff excerpts, detected languages, truncation, and read errors. The repository path must be an explicit Git root. |
| collect_local_evidence | Collect bounded, provenance-rich excerpts from regular files beneath configured document roots in the exact Git repository named by a ChangeScope. Symbolic links are not followed and common credential patterns are redacted. |
| get_review_bundle | Combine a ChangeScope, local document evidence, and optional normalized evidence into a bounded ReviewBundle with a stable evidence index, deterministic Git facts, and explicit missing-evidence records. |
| validate_findings | Validate Agent-produced findings against the shared schema and a ReviewBundle. Known enum formatting aliases are normalized; unknown evidence IDs, unsupported sources, duplicate IDs, and unsupported substantive findings are rejected without inventing content. |
| write_reportA | Render validated Agent findings as a deterministic Markdown and JSON report pair inside a repository-relative output directory. The report preserves confirmed, suspected, and inconclusive findings, evidence coverage, bundle limits/truncation, and validation warnings. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Canlendula/change-trace-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server