F
licenseNot graded
qualityC
maintenanceEnables AI agents to perform offline cybersecurity research and penetration testing by querying a local knowledge base of curated security data, with tools for searching, answering, and status checking.
-
Najjab MCP Server
by SiteQ8
Related Servers
Alternatives to Najjab MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides GCC regulatory intelligence including ZATCA e-invoicing, Arabic NLP, UAE Corporate Tax, and compliance tools for AI agents via the Model Context Protocol.53 npmMIT
- AlicenseNot gradedqualityFmaintenanceQuery Lithuanian cybersecurity data — regulations, decisions, and requirements from NKSC — directly from AI assistants.Apache 2.0
brehon-mcp-serverofficial
AlicenseNot gradedqualityDmaintenanceProvides AI assistants with real-time, structured access to 32 privacy and AI governance laws across 28 jurisdictions to prevent hallucination in compliance answers.9 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables natural-language queries about US federal and New York privacy law obligations, returning citation-anchored answers with computed deadlines, usable from Claude Desktop or the command line.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables engineers and AI assistants to search source-backed hardware design guidelines, retrieve detailed conditions and limitations, and trace citations to original sources, all through a read-only offline interface.AGPL 3.0
TDQS
A3.8/5.0
Scored across 8 tools
Disambiguation4/5
Each tool targets a distinct function: orientation (overview), browsing duties (list_obligations vs get_obligation are a clear list/single pair), computing deadlines, response guidance (playbook vs tabletop), calendar export, and notice drafting. The only mild overlap is that deadlines, list_obligations, and calendar all touch notification timing, but their descriptions differentiate incident-computed timing from register browsing and export.
Naming Consistency4/5
All tools share a consistent najjab_ prefix and snake_case formatting. The suffix style is mixed, though: some are verb_noun (list_obligations, get_obligation, draft_notice) and others are bare nouns (overview, deadlines, playbook, tabletop, calendar), but the convention is readable and predictable overall.
Tool Count5/5
Eight tools is well within the ideal 3-15 range and each one serves a clear, non-redundant purpose in the incident-notification workflow. Nothing feels padded or missing in the count.
Completeness4/5
The surface covers the full arc: orientation, browse/lookup of duties, deadline computation from an incident, response playbook, tabletop exercise, calendar export, and notice drafting. Minor gaps exist (e.g. no direct lookup or filtering by authority, or a comparison/updates view), but core regulatory and response workflows are covered.
Maintenance
ActivityMaintained
ResponsivenessNo issues