THE SUITE · REPORTS + SENTINEL

Your agents answer for themselves now.

Until now, most operators only heard from their firewall at the moment something was denied. These tools are the other half: ask, in plain language, inside whatever agent you already use, and get answers computed from the tamper-evident audit chain. Read-only, never executes an action, and works from the evidence available to your organization.

sentinel watches the pattern · the alert rides inside the ALLOW

Four questions, four tools

"{{ t.q }}"
{{ t.tool }}

{{ t.desc }}

try them without installing anything: the console on the home page runs these exact functions over a demo week

Sentinel: the warning arrives before the money moves

The mandate answers "is this allowed". Sentinel answers the question that arrives one step later in every real incident: it was allowed, but is it NORMAL for this agent? Five deterministic signals, computed from the agent's own history at decision time, delivered inside the ALLOW itself, the last moment a human can still act cheaply. No model, no score, no black box: every alert names its rule and its numbers.

{{ s.name }}

{{ s.desc }}

Two minutes, any agent

One MCP entry gives Claude, Cursor, or any MCP host the whole surface: the payment firewall, the reports, and Sentinel. OpenClaw agents get the same tools from the native plugin. Same functions, same answers, whichever shell your agent runs in.

@fidacy/mcp on npm → or use the hosted MCP →
mcp.json 
{
  "mcpServers": {
    "fidacy": {
      "command": "npx",
      "args": ["-y", "@fidacy/mcp"]
    }
  }
}