F
licenseA
qualityD
maintenancePackage intelligence MCP server. Stops AI agents from installing hallucinated/malicious packages across 17 ecosystems. 22 tools, free, no auth.
22
1
Hextrap MCP
by com.hextrap
Server Details
Hextrap's MCP Connector protects your LLM coding sessions from installing malicious dependencies, typosquats, unpopular packages, and enforces your strict allow and deny lists.
No setup means your LLM uses MCP to configure itself to use Hextrap's proxy's automatically, enforcing your firewall rules immediately. Manage your allow and deny lists right from your favorite LLM.
- 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.
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.8/5.0
Tool DescriptionsB
Average 3.6/5 across 10 of 10 tools scored. Lowest: 2.9/5.
Server CoherenceA
Disambiguation5/5
Each tool has a clearly distinct purpose with no ambiguity: allowlist/denylist management, package checking, credential handling, activity monitoring, firewall listing, and proxy configuration. The descriptions clearly differentiate their functions, such as 'check_package' for security verification versus 'add_to_allowlist' for policy management.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with snake_case, such as 'add_to_allowlist', 'remove_from_denylist', and 'get_proxy_config'. The naming is predictable and readable throughout the set, with no deviations in style or convention.
Tool Count5/5
With 10 tools, the count is well-scoped for managing a firewall system, covering key operations like listing, checking, configuring, and maintaining security policies. Each tool earns its place without redundancy, fitting a typical range for this domain.
Completeness5/5
The tool set provides complete coverage for firewall management: CRUD operations for allowlist/denylist, package verification, credential lifecycle (create, get, roll), activity monitoring, and firewall listing. There are no obvious gaps, enabling agents to handle full workflows from setup to maintenance.
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
- Alicense-qualityCmaintenanceRuntime safety guardrails for AI coding agents. Checks file access, validates shell commands, and scores your repo's AI safety — all via MCP.78MIT
- Flicense-qualityBmaintenanceEnables secure interaction between LLMs and MCP tools by applying zero-trust security controls, including sensitive data masking, file system protection, and policy enforcement.
- Alicense-qualityBmaintenanceA security MCP proxy that monitors and blocks data exfiltration between AI agents and their tools by detecting toxic flows (untrusted → sensitive → egress) deterministically with zero LLM calls in the decision path.1MIT