cyberday-mcp
Related Servers
Alternatives to cyberday-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceLets AI agents query a computerized system inventory as a knowledge graph using Cypher, enabling blast radius, data lineage, regulation checks, and change impact assessments while preventing hallucinated regulatory claims.-
- FlicenseAqualityBmaintenanceEnables AI assistants to query RoboShadow's Rubicon Platform Data API for read-only endpoint security, asset inventory, applications, users, vulnerabilities, and remediation status data.401-
- AlicenseNot gradedqualityFmaintenanceProvides AI assistants with read-only access to Secureframe's compliance data, enabling querying of security controls, tests, users, vendors, and more across frameworks like SOC 2 and ISO 27001.8MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI systems to manage Verodat accounts, workspaces, and datasets, including creating datasets, querying data, and executing AI-powered queries through natural language.9 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to securely query VAST Data databases for schema, metadata, and sample data via read-only SQL and MCP resources.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to read, create, and update legal practice data—cases with history and movements, clients, tasks, and financial transactions—using the firm's API token.MIT
TDQS
Scored across 6 tools
Most tools are clearly distinct: list/search/get handle different retrieval needs, and systems_summary provides aggregate analytics. However, create_system and create_system_advanced overlap on creation, which could cause an agent to choose the wrong one when extended fields are needed.
Five tools follow a consistent verb_noun snake_case pattern (list_systems, search_systems, get_system, create_system, create_system_advanced). The outlier systems_summary uses a noun_noun style, but the overall convention remains readable and predictable.
With six tools, the set is well-scoped for a data-system registry MCP. Each tool covers a distinct operation or aggregation need, and the count avoids both excessive fragmentation and under-provisioning.
The surface covers list, search, get, create, update-via-advanced-create, and summary analytics. The main gap is a dedicated delete or archive operation, which is a minor omission for a registry but not a severe workflow blocker.