Nexus MCP — AI Security Tools
Server Details
MCP server providing AI security tools: prompt injection detection, PII scanning, and RAG input validation. Works with Claude, Cursor, and any MCP-compatible client.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
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/5 across 6 of 6 tools scored.
Most tools have distinct purposes: check_injection detects prompt injection, pii_scan masks personal data, sanitize_content cleans external content, and validate_rag_input provides a pass/fail gate. However, check_injection and validate_rag_input overlap slightly as both handle injection detection, though their descriptions clarify that one is for detailed analysis and the other for quick decisions. The two key-getting tools (get_trial_key and get_pii_guard_key) are clearly separate but could be confused due to similar naming and function.
The naming is mixed: check_injection, sanitize_content, and validate_rag_input follow a verb_noun pattern, but get_trial_key and get_pii_guard_key use a get_noun pattern, and pii_scan uses a noun_verb style. This inconsistency makes the set less predictable, though all names are readable and descriptive. The deviation from a single convention reduces clarity but doesn't render the tools chaotic.
With 6 tools, the count is well-scoped for an AI security server. Each tool serves a specific function in the domain, such as injection detection, PII scanning, content sanitization, and API key management. This number allows for comprehensive coverage without being overwhelming, fitting typical server sizes of 3-15 tools and ensuring each tool earns its place.
The tool set covers key AI security workflows: injection detection (check_injection, validate_rag_input), PII handling (pii_scan), content sanitization (sanitize_content), and API access (get_trial_key, get_pii_guard_key). Minor gaps exist, such as no explicit tool for logging or monitoring security events, but agents can work around this. The domain is well-covered for Japanese-language applications, with no dead ends in core operations.
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!