blast-scope-mcp
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 |
|---|---|
| assess_commandA | Assess the blast radius of a shell command. Splits chained commands on When Args: command: Raw shell command string to analyze. cwd: Working directory for resolving relative paths. Defaults to the server's current working directory. project_root: Root directory of the project for graph-based scoring. If provided, the graph is auto-built when missing. Returns: Structured risk assessment with worst-step score, severity, recommendation, and per-step chain breakdown. Example:: |
| index_projectA | Build or refresh the dependency graph for a project. Forces a graph rebuild for the given project root. Normally not
required — Args: project_root: Absolute path to the project root directory. Returns: Status dict confirming the project was indexed. Example:: |
| list_snapshotsA | List undo snapshots captured before risky commands, newest first. Snapshots are taken automatically by the PreToolUse hook before a
medium-or-higher risk command and stored under
Args: project_root: The project root the snapshots were taken under. Returns:
Example:: |
| restore_snapshotA | Undo a risky command by restoring a snapshot's files in place. Overwrites whatever currently exists at each snapshotted path with the
archived copy. Use Args: snapshot_id: The snapshot id to restore. project_root: The project root the snapshot was taken under. Returns:
Example:: |
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 targets a distinct action: assessing commands, rebuilding the graph, listing snapshots, and restoring them. No functional overlap exists.
All tools follow a consistent verb_noun pattern with lowercase and underscores (assess_command, index_project, list_snapshots, restore_snapshot).
Four tools cover the essential operations on the blast radius domain without redundancy or missing core functionality.
The set covers assessment, graph indexing, and snapshot retrieval/restoration. Snapshot lifecycle management (e.g., deletion) is not exposed, but the core workflow is complete.