codesentry-mcp
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Test connectivity to the CodeSentry server |
| analyze_repositoryB | Analyze a git repository for security, performance, and quality issues |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| code_review | Comprehensive code review prompt for analyzing code quality, security, and performance |
| security_audit | Security-focused analysis prompt for identifying vulnerabilities and security issues |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| CodeSentry Configuration | Current analysis configuration settings |
TDQS
Scored across 2 tools
The two tools serve entirely different purposes: one checks connectivity and the other performs repository analysis. There is no overlap or ambiguity in their intended use.
Both tool names are imperative verbs, but 'ping' is a bare verb while 'analyze_repository' follows a verb_noun pattern. This is a minor deviation from a fully uniform naming convention.
With only two tools, the server feels minimal. For a repository analysis service, one might expect additional tools for managing or retrieving results, but the count is not unreasonable for a simple utility.
The core analysis functionality is present, but there are no supporting operations such as listing previous analyses, fetching detailed reports, or configuring analysis parameters. The surface is functional but incomplete for a comprehensive analysis workflow.