No user-submitted related servers found.
Scored across 66 tools
Multiple explicit aliases duplicate the same operation: prooflink.verify_receipt/verify_prooflink_receipt, prooflink.verify_chain/get_receipt_chain, mission.list_incidents/list_recent_incidents, and compliance.audit_summary/get_compliance_status. There is also a dense cluster of overlapping health/status/dashboard tools, so an agent cannot reliably distinguish which tool to call.
Many tools follow a prefix_snake_case pattern, but dotted namespaces like prooflink.*, mission.*, and compliance.* are mixed with flat equivalents for the same operations. The alias pairs also use inconsistent verb ordering, e.g. get_receipt_chain vs prooflink.verify_chain, making the naming pattern unpredictable.
With 66 tools, this is an extreme mismatch for a coherent toolset. The count is inflated by aliases, near-duplicate status endpoints, and many narrow integration health checks that could be consolidated.
Core workflows for ITSM tickets, SIE scanning, ProofLink verification, and integration health are well covered. However, there are notable dead ends: no reject/dismiss path for SIE or learning items, no contact lookup for GHL, no meaningful RMM/Mesh remote actions beyond script execution, and no RAG content ingestion.