vibecheck
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scanA | Scan a project directory for vibe-coding security / ship-readiness issues (offline, no AI). Returns high-confidence (taint-backed) findings as JSON by default; pass includeAll:true for medium/review too. Run before declaring a coding task done. |
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
Only one tool exists, so there is no possibility of confusing it with other tools. Agents will always select the correct tool.
With a single tool, naming consistency is trivially maintained. The name 'scan' is a clear verb that matches its action.
A single tool is on the low end for a server, but it is acceptable for a narrowly focused utility that performs one well-defined task. The tool covers a specific security scanning need without requiring multiple operations.
The one tool handles the primary scanning operation with configurable output levels, but lacks supporting tools for managing scan history, configurations, or results. It covers the core function but leaves gaps for typical workflows.