SentryFrogg MCP Server
Provides tools for executing parameterized SQL queries, catalog discovery, CRUD operations, and connection management with TLS support for PostgreSQL databases.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SentryFrogg MCP Servershow tables in profile mydb"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SentryFrogg MCP Server v4.2.0
Document Profile
Field | Value |
Product | SentryFrogg MCP Server |
Version | 4.2.0 |
Runtime | Node.js ≥ 16 |
Interfaces | Model Context Protocol (PostgreSQL · SSH · HTTP) |
License | MIT |
Related MCP server: ssh-mcp-server
Executive Synopsis
SentryFrogg MCP Server supplies a governed command plane for MCP-compatible agents that operate data platforms, remote shells and web services. The implementation prioritises deterministic behaviour, encrypted credential storage and prescriptive workflows so that autonomous agents can execute infrastructure tasks with enterprise auditability.
Functional Surface
Capability | Detail |
PostgreSQL control | Parameterised SQL, catalog discovery, CRUD helpers, mutual TLS, connection profiling. |
SSH execution | Serial command dispatch per profile, password/key authentication, reachability diagnostics. |
HTTP access | REST verbs with JSON payloads, health checks, programmable headers and bearer tokens. |
Secret vault | AES-256 encrypted profiles persisted in |
Telemetry | Tool-level statistics via |
System Components
Component | Scope |
| MCP entry point, tool catalogue, lifecycle supervision. |
| Service registration, dependency wiring, resource cleanup. |
| SQL execution, profile validation, TLS configuration, pool management. |
| SSH sessions, sequential execution enforcement, profile hygiene. |
| HTTP invocation, header synthesis, response shaping. |
| Encrypted persistence and retrieval of profile objects. |
| Key lifecycle, cryptographic primitives, payload size guards. |
| Canonical validation for incoming payloads. |
MCP Tools
mcp_psql_manager
Attribute | Specification |
Required flow |
|
Actions |
|
Credentials | Either discrete fields ( |
TLS options |
|
Query rules |
|
Response format | JSON with |
Rejection triggers | Missing profile, malformed SQL, payload limits exceeded, invalid TLS configuration. |
mcp_ssh_manager
Attribute | Specification |
Required flow |
|
Actions |
|
Execution model | Commands trimmed and length-limited; pipes/redirects permitted; per-profile execution is strictly sequential. |
Outputs | JSON containing |
Security posture | Secrets encrypted at rest; no templating—agents must supply fully qualified commands. |
mcp_api_client
Attribute | Specification |
Actions |
|
Inputs |
|
Behaviour | Local and private addresses allowed; HTTP status/body returned in structured JSON; transport or parsing failures emit MCP internal errors. |
Profile Lifecycle
Invoke
setup_profileto persist credentials and TLS artefacts; secrets encrypt with AES-256 using.mcp_profiles.key(0600permissions).Reference the same
profile_namefor subsequent operations; omitted sensitive fields inherit stored encrypted values.Rotate credentials by reissuing
setup_profile; the latest payload supersedes previous entries.Audit existing profiles via
list_profiles; responses never disclose secrets.Retire unused profiles by editing
profiles.jsonunder change control.
TLS Configuration Guidance
Prefer embedding
sslmodedirectives inconnection_url; explicit payload fields override URL parameters.Keep
ssl_reject_unauthorizedattrueunless communicating with trusted self-signed endpoints.Provide
ssl_servernamewhenever certificate CN/SAN mismatches the host.Supply PEM blocks as single-line strings using
\nescape sequences; leading/trailing spaces are disallowed.ssl_passphrasemust be non-empty if provided; omit otherwise.
Installation and Operations
Task | Command |
Clone and install |
|
Syntax check |
|
Launch (stdio) |
|
Update dependencies |
|
Reset profile store | Remove |
Security & Compliance
Encryption key lifecycle:
.mcp_profiles.keygenerated on first run; override viaENCRYPTION_KEYfor coordinated environments.Secret exposure: MCP responses never include decrypted values; rotation requires explicit
setup_profile.Input governance: SQL statements, SSH commands and HTTP payloads are length-limited; oversized inputs are rejected pre-execution.
Audit trail: stderr logging captures timestamped events per tool to support collection by SIEM platforms.
Dependency governance: locked versions of
pg,ssh2,node-fetch,@modelcontextprotocol/sdk; monitor advisories for patch cadence.
Troubleshooting Matrix
Symptom | Diagnostic Actions | Remediation |
PostgreSQL TLS failure | Inspect | Update TLS materials; rerun |
SSH command hang | Validate command length, ensure non-interactive execution, check remote prompts. | Adjust command or script; rerun |
HTTP error response | Review returned status/body, verify | Correct payload; retry request. |
Missing profile | Execute | Recreate via |
Change History Reference
Consult CHANGELOG.md for a dated record of functional and operational updates, including TLS support and renaming.
Contribution & Support
Submit changes through pull requests accompanied by verification evidence (
npm run check).Never commit
.mcp_profiles.keyor environment-specific secrets.Use maintainer contact information in
package.jsonfor escalation or integration assistance.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/iflow-mcp/SentryFrogg-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server