Sentinel for Stacks

app.runsentinelPublished by runsentinel.appOfficial publisherv0.36.0Updated Oct 30, 2026

Stacks contract monitoring: add a watch in one line, get alerts. Hosted, browser sign-in.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Hosted MCP endpoint for Stacks contract monitoring: an assistant can add a watch in one line and receive alerts.

What you can do
  • Add a monitoring watch on a Stacks contract with a single line.
  • Receive alerts when the watched contract activity triggers them.
  • Connect through a hosted remote endpoint after signing in with a browser.
When to use it
Useful when you want an assistant to set up and keep track of Stacks smart contract monitoring without building your own watcher, and to be notified through alerts rather than polling manually.
Requirements
A remote MCP endpoint reached over streamable HTTP; OAuth sign-in through a browser is required. No environment variables or headers are declared.
Before you install
Sign-in is via OAuth, so the server receives an authorized account connection; review what the hosted service can see and do with that access. Adding a watch changes state on the remote service and may trigger alert notifications. No tool list or pricing details are published, so confirm behavior and cost before relying on it.

Installation

In SourceWeft

  1. Open Sentinel for Stacks in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.runsentinel%2Fsentinel/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "sentinel-for-stacks": {
      "type": "http",
      "url": "https://api.runsentinel.app/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.36.0LatestOct 30, 2026
  2. v0.35.0Oct 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.