Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
crumple_scanA

Audit an AI coding agent setup (Claude Code, Codex, Gemini CLI, Cursor, MCP config, hooks, CLAUDE.md/AGENTS.md, .env exposure) the way an attacker would. Local and instant: no key, no Docker, nothing leaves the machine. Returns a 0-100 Safe Setup score and findings, each with why it matters and the fix. With cves: true it also checks the MCP servers it finds (npx/uvx packages) against published vulnerabilities on osv.dev, sending only package names and versions.

crumple_siteA

Grade a deployed web app (built with Lovable, Bolt, v0, Replit, Emergent or by hand) A to F for what a stranger can use against it: secret keys shipped in its JavaScript, a Supabase service_role key in the browser, public source maps, no Content-Security-Policy. Each finding has a plain-English reason, what the owner must do by hand (like revoking a key), and a fix prompt to apply in the app's code. Call it again after fixing: change lists what got fixed. Reads only what the site serves to every visitor. Database checks (which Supabase tables or Firebase data anyone can read) need the owner, so tell them to run npx crumplelab site <url> --mine themselves.

crumple_trapsB

The traps Crumple's crash test runs: each modelled on a real attack (poisoned issues, evil MCP servers, secret exfiltration, destructive commands), with its risk.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 3 tools

Disambiguation4/5

The three tools target clearly different surfaces: local AI-agent configuration, deployed web apps, and a reference list of attack traps. crumple_scan and crumple_site could be briefly confused as two audit modes, but the descriptions make the local-vs-deployed distinction explicit. crumple_traps is informational rather than an audit action, which is a mild mismatch in tool type but not genuinely ambiguous.

Naming Consistency4/5

All tools share the consistent crumple_ prefix and snake_case formatting, making the set predictable and easy to recognize. However, the suffixes mix verb-like (scan) and noun-like (site, traps) forms, so it is not a uniform verb_noun convention.

Tool Count5/5

Three tools is well-scoped for a focused security-audit server: one for local agent setups, one for deployed sites, and one reference tool for attack traps. Each tool has a clear reason to exist and none feels redundant or padded.

Completeness4/5

The surface covers the two main audit targets plus an explanatory trap catalogue, and crumple_site supports re-running after fixes. The main gap is that deeper database exposure checks cannot be performed by the server and must be delegated to the owner via CLI, though this is clearly documented as a workaround.

Maintenance

ActivityMaintained
ResponsivenessUsually handled