Sentinel Signal Mcp

Created By
sentinelsignal3 months ago
Local stdio MCP server exposing Sentinel Signal as agent tools: score workflows, check limits/usage, and submit feedback. Supports env-based auth or auto-minted trial key for fast start.
Overview

Sentinel Signal MCP

Local stdio MCP server exposing Sentinel Signal as agent tools:

  • Score workflows
  • Check limits & usage
  • Submit feedback

Supports env-based auth or auto-minted trial key for fast start (unless disabled).


Skills (Tools)

  • score_workflow — Score a structured payload against a named workflow
  • get_limits — Retrieve plan limits for the current key
  • get_usage — Retrieve usage for a given month
  • submit_feedback — Submit structured outcome feedback

Install & Run

Recommended:

uvx sentinel-signal-mcp

Environment Variables

export SENTINEL_BASE_URL="https://api.sentinelsignal.io"
export SENTINEL_TOKEN_BASE_URL="https://token.sentinelsignal.io"
export SENTINEL_TIMEOUT_SECONDS="30"

# If omitted, the server can auto-mint a trial key (unless disabled)
# export SENTINEL_API_KEY="ss_live_or_test_..."

# Disable auto-trial minting
# export SENTINEL_NO_TRIAL="1"

# Override credentials cache location
# export SENTINEL_CREDENTIALS_PATH="$HOME/.sentinel/credentials.json"

Troubleshooting

402: upgrade_required: trial quota exhausted → follow the returned upgrade URL.
429: rate limited → retry later.
401/403: invalid or missing API key (set SENTINEL_API_KEY or remove SENTINEL_NO_TRIAL to allow trial).

Credentials stuck / need fresh trial key: reset cached credentials:

sentinel-signal-mcp --reset-credentials

PyPI: https://pypi.org/project/sentinel-signal-mcp/ Docs/Homepage: https://sentinelsignal.io

Server Config

{
  "mcpServers": {
    "sentinel-signal": {
      "command": "uvx",
      "args": [
        "sentinel-signal-mcp"
      ],
      "env": {
        "SENTINEL_BASE_URL": "https://api.sentinelsignal.io",
        "SENTINEL_TOKEN_BASE_URL": "https://token.sentinelsignal.io",
        "SENTINEL_TIMEOUT_SECONDS": "30"
      }
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
sentinelsignal
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago