EyalSec MCP Server
OfficialRelated Servers
Alternatives to EyalSec MCP Server
No user-submitted related servers found.
Related Servers
AlicenseAqualityCmaintenanceProvides read-only access to a Mailfact tenant, letting users list domains, sending sources, and aggregate reports, and query DMARC alignment, reporter coverage, and record-level data through MCP tools. It returns counts and rows only, without recommending policies or scoring domains.9MIT- AlicenseNot gradedqualityCmaintenanceEnables read-only MCP access to Tactical RMM, allowing agents to query devices, clients, sites, audit logs, software, and pending actions without any mutating capabilities.MIT
- AlicenseNot gradedqualityDmaintenanceEnables read-only access to SentinelOne's platform through MCP, allowing security investigations, threat hunting, and asset inventory queries via natural language.MIT
- AlicenseNot gradedqualityBmaintenanceEnables read-only access to Autobase Console projects, clusters, environments, operations, PostgreSQL versions, and extensions through configurable MCP tools. Supports paginated listing and filtering, with limited redacted operation logs and no write or arbitrary execution tools.MIT
- AlicenseNot gradedqualityCmaintenanceEnables read-only inspection of Google Ads accounts through MCP, including account inventory, reporting, metadata, change history, and safe GAQL queries.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceProvides safe, read-only CRM access for AI assistants with per-key scopes, field masking, rate limits, and a full audit log of allowed and blocked actions.MIT
TDQS
Scored across 19 tools
Most tools target clearly distinct resources (events, runs, machines, rules, filters, labels, account). Minor overlap exists between event_stats (dashboard summary) and event_counts (per-product/quota counts), and between list_event_names (sink labels) and list_labels (triage labels), which could cause occasional misselection.
Consistent snake_case throughout, with a predictable verb_noun pattern for most tools (list_rules, get_event, search_events). A subset deviates to bare noun_phrases (event_stats, event_counts, event_map, ci_findings, supported_targets), which is a minor but noticeable inconsistency.
19 tools is slightly above the ideal 3-15 range but justified by a broad security-monitoring domain spanning events, runs, machines, rules, filters, labels, findings and account state. Each tool maps to a distinct capability, so nothing feels padded.
The surface is heavily read-only: many list_*/get_*/search_* tools but no create/update/delete for rules, filters, labels, saved searches or machines. Core investigation workflows are well covered, but lifecycle/mutation operations are notably absent, limiting it as a full management surface.