Najjab MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| najjab_overviewA | What Najjab covers: the six Gulf countries, the authorities and duties in the register, how each duty was verified, and the authorities still being verified. Start here. |
| najjab_list_obligationsA | Notification duties in the register with authority, who they apply to, the deadline in words, the official source and the verification level. Filter by country, financial free zone, trigger (cyber-incident or personal-data-breach) or sector. Paged. |
| najjab_get_obligationA | One duty by id (for example "kw-cbk-incident" or "sa-sdaia-pdb") with every deadline row, the summary, the official source with its reference and link, and the secondary sources when the official text could not be read automatically. |
| najjab_deadlinesA | Every notification duty an incident triggers across the given countries, soonest first, with the due time computed from the discovery time, follow up updates and closure reports, and notes when the severity grade changes the answer. |
| najjab_playbookA | The playbook for an incident type: how it shows up, the first hour, containment, eradication, recovery, the evidence to keep and what to do after. |
| najjab_tabletopA | A ready tabletop exercise for an incident type: the scenario, the developments with the minute each is revealed, and the questions for the room. |
| najjab_calendarA | An iCalendar (.ics) file with one event per timed deadline the incident triggers and a reminder 15 minutes before each, ready to import into Outlook, Google Calendar or Apple Calendar. |
| najjab_draft_noticeB | A plain notice in Arabic or English that gathers the facts every regulator asks for first, addressed to the authorities the incident triggers. Use the authority's own form and channel where one exists. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
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.
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.
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.
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.