solidity-sentinel
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SENTINEL_KEY | No | Optional key to unlock deep audit |
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 |
|---|---|
| audit_contractA | Static security audit of a Solidity smart contract OR a deployed contract's bytecode. Paste the contract |
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 risk of confusion. The tool's purpose is clearly distinct from any other potential tool.
The single tool name follows a clear verb_noun pattern (audit_contract), which is consistent and descriptive. No inconsistencies to evaluate.
With only one tool, the server is on the thin side. However, the tool is comprehensive, encapsulating both free and premium audits via parameters, which somewhat justifies the low count.
The tool covers a wide range of security detectors and audit modes (source code, bytecode, deep analysis). Minor gaps like gas analysis or integration checks are absent but not critical for the core audit purpose.