Read-only backend investigations with Loki, Prometheus, PostgreSQL, Redis, BullMQ, Docker and GitHub.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
list_projectsList configured projects with pagination. Use this first to select a projectId; no connection credentials are returned.List configured projects with pagination. Use this first to select a projectId; no connection credentials are returned.
No input schema was published for this tool.
get_project_capabilitiesDiscover enabled sources and available read-only checks for a project before choosing follow-up tools. Source IDs are included, connection configuration is not.Discover enabled sources and available read-only checks for a project before choosing follow-up tools. Source IDs are included, connection configuration is not.
No input schema was published for this tool.
investigate_backendPrimary high-level tool: conservatively select a strategy from an unambiguous question or explicit strategy. Unknown/mixed questions preserve full health checks. Conditional checks require observed dependency hints; irrelevant sources are skipped. Returns execution decisions, facts and optional rea…Primary high-level tool: conservatively select a strategy from an unambiguous question or explicit strategy. Unknown/mixed questions preserve full health checks. Conditional checks require observed dependency hints; irrelevant sources are skipped. Returns execution decisions, facts and optional rea…
No input schema was published for this tool.
investigate_operationInvestigate a specific endpoint or operation in one service/log source and explicit time window. Match route or query, then correlate sampled request/trace IDs. Live infrastructure anomalies are only temporally related, not proof of causation. When history is configured, appends a local archive wit…Investigate a specific endpoint or operation in one service/log source and explicit time window. Match route or query, then correlate sampled request/trace IDs. Live infrastructure anomalies are only temporally related, not proof of causation. When history is configured, appends a local archive wit…
No input schema was published for this tool.
investigate_deployment_regressionCompare evidence before/after an observed successful deployment or explicitly labelled release marker. Uses compatible archived snapshots and historical logs; missing baselines are not zero. Separates changes, unchanged metrics, time correlation and optional hypotheses. Current follow-up checks are…Compare evidence before/after an observed successful deployment or explicitly labelled release marker. Uses compatible archived snapshots and historical logs; missing baselines are not zero. Separates changes, unchanged metrics, time correlation and optional hypotheses. Current follow-up checks are…
No input schema was published for this tool.
list_investigationsList immutable saved investigation summaries with pagination and optional projectId filter. Historical projects need not still exist; credentials and raw logs are not loaded.List immutable saved investigation summaries with pagination and optional projectId filter. Historical projects need not still exist; credentials and raw logs are not loaded.
No input schema was published for this tool.
get_investigationRetrieve an immutable investigation snapshot by investigationId, with paginated summarized evidence, findings, accepted hypotheses and source availability. Evidence references may point to another page. No live source or deleted project credentials are required.Retrieve an immutable investigation snapshot by investigationId, with paginated summarized evidence, findings, accepted hypotheses and source availability. Evidence references may point to another page. No live source or deleted project credentials are required.
No input schema was published for this tool.
get_latest_deploymentRead latest/previous GitHub deployments using success-status timestamps, or explicitly enabled local demo-only simulated switches. Releases are publication markers, never claimed rollout times. Build historical before/after windows without changing infrastructure.Read latest/previous GitHub deployments using success-status timestamps, or explicitly enabled local demo-only simulated switches. Releases are publication markers, never claimed rollout times. Build historical before/after windows without changing infrastructure.
No input schema was published for this tool.
inspect_serviceFollow up on a Docker service/container by its exact serviceId and sourceId. Reads runtime inventory, health, optional stats and recent restarts; never restarts or modifies containers.Follow up on a Docker service/container by its exact serviceId and sourceId. Reads runtime inventory, health, optional stats and recent restarts; never restarts or modifies containers.
No input schema was published for this tool.
inspect_databaseRead PostgreSQL health, current sessions and blocking locks. For a performance review explicitly request performanceChecks: query_statistics (pg_stat_statements), tables, indexes, vacuum, io. Optional checks use bounded fixed read-only queries and report availability/reasons individually. performan…Read PostgreSQL health, current sessions and blocking locks. For a performance review explicitly request performanceChecks: query_statistics (pg_stat_statements), tables, indexes, vacuum, io. Optional checks use bounded fixed read-only queries and report availability/reasons individually. performan…
No input schema was published for this tool.
inspect_metricsRead fixed, scoped Prometheus range queries: availability (scrape targets), http (request rate, 5xx percent, classic histogram p95/p99) and resources (process CPU cores and resident bytes). No arbitrary PromQL or writes. Windows are at most 24 hours with at most 21 evaluation points. Missing data/n…Read fixed, scoped Prometheus range queries: availability (scrape targets), http (request rate, 5xx percent, classic histogram p95/p99) and resources (process CPU cores and resident bytes). No arbitrary PromQL or writes. Windows are at most 24 hours with at most 21 evaluation points. Missing data/n…
No input schema was published for this tool.
inspect_redisRead Redis health and sanitized SLOWLOG samples for a configured source. Never scans all keys, reads values or executes write commands.Read Redis health and sanitized SLOWLOG samples for a configured source. Never scans all keys, reads values or executes write commands.
No input schema was published for this tool.
inspect_queueRead BullMQ counts, worker visibility and sanitized bounded job samples for a configured queue. No job retry, removal or state changes are exposed.Read BullMQ counts, worker visibility and sanitized bounded job samples for a configured queue. No job retry, removal or state changes are exposed.
No input schema was published for this tool.
search_logsSearch bounded Docker or scoped Loki logs by optional serviceId and literal substring query. For Loki, serviceId is the source ID, not a container ID; configured labels cannot be overridden. Use a narrower explicit time window/query if sampled or oversized.Search bounded Docker or scoped Loki logs by optional serviceId and literal substring query. For Loki, serviceId is the source ID, not a container ID; configured labels cannot be overridden. Use a narrower explicit time window/query if sampled or oversized.
No input schema was published for this tool.
14 of 14 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Read-only backend investigations with Loki, Prometheus, PostgreSQL, Redis, BullMQ, Docker and GitHub.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
74 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+62 more not listed. The counts by reason above cover all of them.
Not followed: optionalDependencies, peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.