Dredd MCP
Server Details
Pre-flight MCP security. Blocks compromised deps + tool drift. HMAC-signed. Dredd judges.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pduggusa/dredd-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is singular and well-defined.
With a single tool, naming consistency is inherently maintained. The name 'check_mcp_server' follows a clear verb_noun pattern.
The server's purpose is to provide a pre-flight security verdict for MCP servers. One tool is perfectly scoped for this focused responsibility.
The tool fully covers its stated function of security checking, but the domain might benefit from additional tools for threat intelligence updates or detailed reporting. However, for a single-purpose server, it is reasonably complete.
Available Tools
1 toolcheck_mcp_serverAInspect
Pre-flight security verdict for an MCP server invocation. Returns BLOCK / ADVISORY / ALLOW with severity, evidence, and HMAC-signed response. Backed by the DugganUSA threat-intel corpus (1.13M+ IOCs). Use this BEFORE invoking any other MCP server tool, especially those installed from outside the official MCP Registry.
| Name | Required | Description | Default |
|---|---|---|---|
| tool | No | Optional name of the specific tool being invoked | |
| server | Yes | MCP server name (e.g. io.github.foo/bar) or substring | |
| version | No | Optional version of the MCP server (semver) |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the burden. It describes the return format (verdict, severity, evidence, HMAC) and the threat-intel corpus backing. However, it does not disclose any potential side effects, authorization needs, or error conditions, leaving moderate gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loads the key purpose, and contains no unnecessary verbiage. Every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description adequately covers the return values (verdict types, evidence, HMAC). It also mentions the threat-intel corpus. It does not detail error cases or pagination, but for a pre-flight check it is sufficiently complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description does not add significant meaning beyond the schema, except a parenthetical example for the 'server' parameter. It does not elaborate on 'tool' or 'version' parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it returns a security verdict (BLOCK/ADVISORY/ALLOW) with severity, evidence, and HMAC-signed response. The verb 'check' and resource 'MCP server invocation' are specific, and there are no sibling tools to differentiate.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly advises 'Use this BEFORE invoking any other MCP server tool', particularly those from outside the official registry. It clearly states the context, though it does not specify when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!