PerspectiveGraph
Related Servers
Alternatives to PerspectiveGraph
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables read-only scanning and graph mapping of a cloud estate, revealing public exposure, connectivity, firewall and NSG rules, identity permissions, and RBAC with cited evidence.16MIT
- AlicenseAqualityDmaintenanceA 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.154Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables AI to scan AWS accounts, analyze attack paths, and verify security fixes on a read-only graph of cloud resources.5-
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to query a local code graph over stdio, so they can see what a Git change may affect, find related tests, routes and nodes, and cite evidence paths — read-only and fully on-machine.2 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables cross-framework queries over MITRE ATT&CK, D3FEND, ATLAS and F3 with provenance on every link, plus coverage and gap analysis against a technique list, actor or detection rules. Also renders validated D3FEND CAD, Attack Flow, ATT&CK Navigator and Mermaid diagrams from a small scenario spec.5Apache 2.0
- AlicenseAqualityDmaintenanceMCP server for auditing infrastructure-as-code attack paths, finding multi-hop chains from public internet to sensitive resources.2MIT
TDQS
Scored across 8 tools
Each tool has a distinct role: get_posture orients, list_attack_paths enumerates globally, explain_attack_path details one route, routes_to_target enumerates to a named asset, list_fixes gives remediation, search_assets resolves names, get_score_trust reports calibration, and simulate_fix runs counterfactuals. The descriptions explicitly disambiguate the potentially overlapping route tools (global listing vs target-specific k-best vs single-route detail) and when to reach for each.
Seven of eight names follow a clean snake_case verb_noun pattern (get_posture, list_attack_paths, explain_attack_path, list_fixes, search_assets, get_score_trust, simulate_fix). Only routes_to_target breaks the convention with a noun_to_noun form, a minor deviation but still readable.
Eight tools is well-scoped for an attack-path exposure analysis domain, with each tool covering a genuine capability (orientation, enumeration, detail, target analysis, remediation, search, calibration, simulation). No tool feels redundant or padded.
Coverage of the analysis lifecycle is strong: orient, enumerate, explain, remediate, verify, and self-assess score trust. Minor gaps exist—no tool manages the analyst suppression referenced by list_attack_paths, and there is no export/report operation—but core workflows are complete for a read-only analytical surface.