SentryFrogg MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENCRYPTION_KEY | No | Override the default encryption key for coordinated environments. If not provided, a key is generated on first run. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcp_psql_managerB | PostgreSQL toolchain. Flow: setup_profile → action. setup_profile accepts credentials or connection_url plus optional TLS (ssl_mode, ssl_ca, ssl_cert, ssl_key, ssl_passphrase, ssl_servername, ssl_reject_unauthorized); secrets stored encrypted. Subsequent calls reuse profile_name: quick_query (adds LIMIT 100 if absent; supports params array for $ placeholders), show_tables, describe_table, sample_data, database_info, insert_data, update_data, delete_data, list_profiles. |
| mcp_ssh_managerA | SSH executor. setup_profile stores host credentials (password or PEM private_key with optional passphrase); data encrypted. list_profiles enumerates profiles, system_info returns collected facts, check_host validates reachability, execute runs one trimmed command (pipes/redirects allowed) sequentially per profile; no concurrent runs. |
| mcp_api_clientA | HTTP caller. Fields: action ∈ {get, post, put, delete, patch, check_api}, url (required), data (JSON body for mutating verbs), headers (string map), auth_token (prefixed into Authorization unless headers.Authorization supplied). Local URLs allowed. Responses are structured results or MCP errors. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a completely distinct domain: HTTP API calls, PostgreSQL database management, and SSH remote execution. There is no overlap in purpose or functionality, so an agent can clearly differentiate them.
All tool names follow the pattern 'mcp_<domain>_<role>' (e.g., mcp_api_client, mcp_psql_manager, mcp_ssh_manager), using consistent snake_case and a descriptive prefix. The variation between 'client' and 'manager' is appropriate for their roles.
With only three tools, the server covers three broad areas (API, database, SSH). While each tool is rich in sub-actions, the raw count is at the low end of the range, making it borderline but acceptable for a general-purpose server.
Within the declared domains, the tools provide comprehensive coverage: HTTP client supports all methods, PostgreSQL manager includes full CRUD and schema inspection, SSH manager handles command execution and system info. Minor gaps like bulk operations exist but do not hinder core workflows.