InnerVault

scope-guard

Stale Official MCP Registry, io.github.mdfifty50-boop

Hard scope boundaries to prevent AI agent drift

Open the source (opens github.com) https://github.com/mdfifty50-boop/scope-guard-mcp

Before you use it

  • Runs on your computer with your permissions. Read what it can do before connecting it to an agent.

What it is

MCP servers from io.github.mdfifty50-boop.

The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.

How to get it

npm package (stdio)

scope-guard-mcp@0.1.3

From the server's entry in the official MCP Registry

Related

  1. ebenova-scope-guard

    MCP servers

    AI contract scope violation detector. Detect scope creep, draft responses.

    Stale Official MCP Registry, io.github.dgtalquantumleap-ai Updated 7 months ago 2 notes

    @ebenova/scope-guard-mcp@1.0.1
  2. kubeleash

    MCP servers

    Kubernetes MCP server with RBAC-style, context-scoped guardrails for AI agents.

    Stale Official MCP Registry, io.github.kubeleash Updated 5 months ago 1 note

    ghcr.io/kubeleash/kubeleash:0.3.0
  3. Stet

    MCP servers

    Guardrails for AI coding agents: scope guard and locked behaviours for Claude Code, Cursor, Codex

    Indexed Official MCP Registry, io.github.shamazkhan Updated yesterday 1 note

    stet-cli@0.6.5
  4. GitHub MCP server

    MCP servers

    GitHub's official MCP server. It lets an agent read and work with repositories, issues and pull requests.

    Hand-checked InnerVault (hand-checked), GitHub 34.3k ★MIT

    https://api.githubcopilot.com/mcp/
  5. Apify MCP server

    MCP servers

    Lets an agent run Apify's ready-made scrapers to pull data from websites, search engines, maps and social platforms.

    Hand-checked InnerVault (hand-checked), Apify 16.0k ★MIT

  6. Official MCP Registry

    MCP servers

    The MCP project's own registry of public MCP servers, so you can look for a connector before building one.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0