blast-scope-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": 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 | |
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/Atharva-Jayappa/blast-scope'
If you have feedback or need assistance with the MCP directory API, please join our Discord server