Skip to main content
Glama

Related Servers

Alternatives to spindl-workshop

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query and manage Cisco Secure Firewall Management Center devices, policies, and deployments over streamable HTTP, and is designed to demonstrate Cisco AI Defense's in-path control of MCP tool calls.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      A local, keyless MCP server simulating Forge's industrial telemetry kernel, enabling agents to normalize vendor-specific machine data, forecast breaches, and test integrations against realistic equipment data without credentials or persistence.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Publishes an MCP Streamable HTTP JSON-RPC endpoint where clients can initialize sessions, list and call synthetic deployment, runtime, cluster-inspection, and audit-log tools. While serving those decoy tools, it records initialization, tool discovery, argument shapes, and multi-tool sequences as evidence for classifying and investigating agent-like behavior.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      A policy and audit layer for Model Context Protocol (MCP). MCP Firewall sits transparently between any MCP client (Claude Desktop, Cursor, VS Code, etc.) and an upstream MCP server, allowing you to inspect, allow, block, or audit requests before they reach the server.
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server provides a stateful, resettable, verifiable API runtime that gates every tool call, enabling agents to run long workflows against provider-shaped environments without live provider write access. It records decisions, side effects, and outcome evidence for replayable, verifiable benchmark runs.
      Apache 2.0

    TDQS

    B3.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    The three fw_get_* tools each target a clearly distinct resource (device metadata, security rulebase, traffic logs), and the two meta tools split cleanly into index (fw_list_tools) versus detail (fw_describe_tool). No two tools overlap in purpose.

    Naming Consistency5/5

    Every tool follows the same fw_<verb>_<noun> snake_case convention with a small, predictable verb set (get, list, describe). The shared fw_ prefix further groups all tools under one server namespace.

    Tool Count3/5

    Five tools is numerically fine, but two of them are introspection/meta tools, leaving only three actual firewall operations. The surface feels thin for a firewall domain, even a read-only workshop one.

    Completeness3/5

    Read coverage is reasonable but narrow: logs are hard-coded to the last 24 hours with no time-range or filter parameters, and there are no operations for interfaces, zones, NAT, or rule creation/editing. Agents inspecting a firewall will hit dead ends for anything beyond a snapshot.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues