Skip to main content
Glama
sn0bored

Permissioned MCP Server

by sn0bored

Related Servers

Alternatives to Permissioned MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      A least-privilege enforcement proxy for MCP servers. It sits between MCP clients and upstream servers, enforcing tool policies, hiding denied tools, requiring human approval for risky actions, and providing a structured audit trail.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A governed MCP server exposing 37 risk-checked tools with signed Ed25519 receipts on a Bitcoin-anchored ledger, failing closed if governance or receipt writing fails.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server lets agents inspect every Model Context Protocol server on the machine, verify tools by running them in a sandbox, and check each call against a human-approved baseline so that changed or newly appeared tools are blocked before they execute. It also surfaces token cost, capability facts, and drift history for each tool entirely locally, without uploading inventory or requiring an account.
      403 PyPI
      1
      Apache 2.0
    • F
      license
      B
      quality
      C
      maintenance
      A security research MCP server for testing tool call safety with deterministic policies like allowlists, path boundary enforcement, SSRF prevention, output redaction, and prompt injection detection, without requiring external LLMs or API keys.
      6
      -
    • A
      license
      B
      quality
      B
      maintenance
      A deliberately small MCP server that demonstrates security hardening against the OWASP MCP Top 10 with tools for file search, record queries, and document fetching, each defended against path traversal, SQL injection, and SSRF.
      4
      MIT

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: list returns metadata, get returns a full note, and create adds a new note. No overlap in functionality.

    Naming Consistency5/5

    All tools follow the consistent pattern 'notes.<verb>', using simple, descriptive verbs (list, get, create). No naming style deviations.

    Tool Count5/5

    Three tools is a reasonable scope for a basic note management server. It covers core operations without being too sparse or excessive.

    Completeness3/5

    The set supports listing, reading, and creating notes but lacks update and delete operations. While a minimal viable set, these missing operations are notable gaps for typical CRUD coverage.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive