ContractAudit MCP Server
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 |
|---|---|
| search_security_knowledge | Search audit findings and EVM security guidance with source citations. |
| get_audit_finding | Return one exact finding or guidance chunk by its stable chunk ID. |
| get_document_contextC | Return ordered chunks from one source document. |
| list_sourcesA | List ingested source documents, licenses, URLs, and processing states. |
| corpus_statusA | Return corpus, vector collection, and embedding model status. |
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 3 tools
Each tool targets a clearly distinct aspect of the server: retrieving document content, listing source metadata, and reporting system status. No overlapping functionality.
Most names follow a verb_noun pattern (get_document_context, list_sources), but corpus_status is a noun_noun pair without a verb, breaking full consistency. Overall pattern is clear and readable.
Three tools is on the low end for a contract audit server, but could be acceptable if the server is narrowly scoped. It borders on feeling thin.
The tool set lacks essential operations like adding or deleting sources, searching across documents, or comparing contracts. Significant gaps impair full audit workflows.