A
licenseNot graded
qualityC
maintenanceRuntime safety guardrails for AI coding agents. Checks file access, validates shell commands, and scores your repo's AI safety — all via MCP.
5
8
MIT
agentguard
Server Details
AgentGuard — 20-tool AI safety MCP: policy preflight, risk scoring, audit logging, rate limits.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- ToolOracle/agentguard
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
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.
100% free. Your data is private.
Tool Definition Quality
A3.6/5.0
Tool DescriptionsA
Average 4/5 across 24 of 24 tools scored. Lowest: 2.9/5.
Server CoherenceA
Disambiguation3/5
Most tools have distinct purposes, but there is notable overlap: output_safety_scan and secret_exposure_check both detect secrets/PII, and payment_policy_check vs spend_limit_check relate to payment limits. The descriptions help, but an agent may struggle to choose among the many similar 'check' tools.
Naming Consistency4/5
Tool names are overwhelmingly snake_case with a noun-based prefix followed by a verb or 'check' (e.g., rate_limit_check, audit_log_query). Minor deviations like 'decision_explain' and 'emergency_kill' still fit the readable pattern, so naming is mostly consistent.
Tool Count3/5
24 tools is on the heavy side but within the borderline range. The domain of agent security and governance justifies many specialized checks, though some tools could potentially be consolidated (e.g., output_safety_scan and secret_exposure_check).
Completeness4/5
The tool surface covers the full guardrail lifecycle: pre-execution checks, approval workflows, emergency controls, post-execution auditing, and metrics. Gaps include no policy management (create/update) and no tenant administration, but these are not critical for the server's apparent purpose.
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!
Related MCP Servers
- AlicenseAqualityBmaintenancePolicy-based governance for AI agent tool calls. YAML policies, approval gates, risk assessment, and audit logging across LangChain, OpenAI, Anthropic, and MCP.515MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for AI agent security guardrails. Provides input validation, prompt injection detection, PII redaction, output filtering, policy enforcement, rate limiting, and comprehensive audit logging.451MIT
SentinelGateofficial
AlicenseNot gradedqualityAmaintenanceOpen-source MCP proxy that enforces security policies, content scanning, and audit logging between AI agents and tool servers25AGPL 3.0