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
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
10 toolsadd_to_allowlistTry in Inspector
Add a package to a firewall's allowlist.
| Name | Required | Description | Default |
|---|---|---|---|
| registry | Yes | Package registry | |
| firewall_id | Yes | Firewall public ID | |
| package_name | Yes | Package name to add |
add_to_denylistTry in Inspector
Add a package to a firewall's denylist.
| Name | Required | Description | Default |
|---|---|---|---|
| registry | Yes | Package registry | |
| firewall_id | Yes | Firewall public ID | |
| package_name | Yes | Package name to add |
check_packageTry in Inspector
Check if a package is allowed by a hextrap firewall and verify it is not a suspected typosquat. Call this BEFORE suggesting any npm, PyPI, or Go dependency to ensure it meets security policy.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Package name to check | |
| registry | Yes | Package registry | |
| firewall_id | Yes | Firewall public ID |
create_service_credentialTry in Inspector
Create a named service credential for CI/CD pipelines. Returns proxy credentials and configuration commands to use in pipeline environment variables or config files. Each pipeline or environment should have its own credential for auditability.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Descriptive name for the credential (e.g. "GitHub Actions", "GitLab CI") | |
| firewall_id | Yes | Firewall public ID |
get_activityTry in Inspector
Get recent package installation activity for a firewall.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of records (default 20) | |
| firewall_id | Yes | Firewall public ID |
get_proxy_configTry in Inspector
Get proxy credentials and package manager configuration for a firewall. If no credential exists, creates one and returns ready-to-use setup commands. If a credential already exists, returns the username and a note that the password is already configured. Call roll_proxy_credential if a new password is needed.
| Name | Required | Description | Default |
|---|---|---|---|
| firewall_id | Yes | Firewall public ID |
list_firewallsTry in Inspector
List all firewalls the user has access to.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
remove_from_allowlistTry in Inspector
Remove a package from a firewall's allowlist.
| Name | Required | Description | Default |
|---|---|---|---|
| firewall_id | Yes | Firewall public ID | |
| package_name | Yes | Package name to remove |
remove_from_denylistTry in Inspector
Remove a package from a firewall's denylist.
| Name | Required | Description | Default |
|---|---|---|---|
| firewall_id | Yes | Firewall public ID | |
| package_name | Yes | Package name to remove |
roll_proxy_credentialTry in Inspector
Roll (regenerate) the personal proxy credential for a firewall. This invalidates the previous password and returns a new one with ready-to-use configuration commands. Only call this when the user explicitly needs new credentials — it will break any existing package manager configuration using the old password.
| Name | Required | Description | Default |
|---|---|---|---|
| firewall_id | Yes | Firewall public ID |
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
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!