Skip to main content
Glama
luiacuaniello

PerspectiveGraph

by luiacuaniello
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Related Servers

Alternatives to PerspectiveGraph

No user-submitted related servers found.

    Related Servers

    • cyntrisec

      cyntrisec
      A
      license
      A
      quality
      C
      maintenance
      A local-first AWS security tool that uses graph theory to discover attack paths (e.g., Internet → Role → DB) and prioritize remediations. It allows agents to perform read-only security audits and generate Terraform fixes without data exfiltration.
      15
      62 PyPI
      4
      Apache 2.0

    • oci-mcp

      jaiakash
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP-aware agents to read and explore Oracle Cloud Infrastructure — listing, fetching, and searching across 39 resource types spanning Identity, Compute, Block Volume, Networking, Object Storage, and OKE. Runs locally over stdio using credentials from ~/.oci/config, with fail-closed safety gates and audit logging governing future write operations.
      4
      Apache 2.0

    • datasphere-mcp

      stkim3
      A
      license
      B
      quality
      C
      maintenance
      Enables read-only exploration of SAP Datasphere tenants, letting users list spaces and modeling objects, read objects' raw CSN definitions, and trace upstream dependency graphs with evidence. It enforces read-only DEV/QAS/PRD access through the official SAP Datasphere CLI and OAuth, with no mutation, SQL, or arbitrary command capabilities.
      4
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: explain_attack_path drills into one route, list_attack_paths ranks all routes, routes_to_target enumerates routes to a specific asset, and simulate_fix tests changes. The only potential confusion is between list_attack_paths and routes_to_target, but their descriptions clarify one is a global ranked list while the other is target-specific choke-point analysis.

    Naming Consistency4/5

    The dominant pattern is verb_noun (explain_attack_path, get_posture, list_attack_paths, search_assets, simulate_fix). One outlier, routes_to_target, is a noun phrase rather than verb_noun, and there is minor singular/plural variation (attack_path vs attack_paths, fix vs fixes), but overall the naming is predictable and readable.

    Tool Count5/5

    Eight tools is well-scoped for a security analysis server. Each tool earns its place: orientation, enumeration, deep-dive, trust calibration, remediation planning, and counterfactual simulation. No tool feels redundant or missing to make the set bloated or thin.

    Completeness4/5

    The tool surface covers the core lifecycle: orient (get_posture, search_assets), enumerate (list_attack_paths, routes_to_target), explain (explain_attack_path), validate score trust (get_score_trust), and remediate (list_fixes, simulate_fix). A minor gap is the lack of a dedicated asset-detail or relationship-detail tool, but search_assets and explain_attack_path compensate sufficiently for common workflows.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources