io.github.dlsforge/aegov-mcp
NPM · @DLSFORGE/AEGOV-MCP · SCANNED SEP 30
UAE Design System (AEGOV DLS) for AI assistants: components, tokens, validation. Not TDRA-official.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 61 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1136 tokens (~162/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.dlsforge/aegov-mcp server?
io.github.dlsforge/aegov-mcp runs locally as an npm package, launched with npx -y @dlsforge/aegov-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @dlsforge/aegov-mcp
claude mcp add dlsforge-aegov-mcp -- npx -y @dlsforge/aegov-mcp
{
"mcpServers": {
"dlsforge-aegov-mcp": {
"command": "npx",
"args": [
"-y",
"@dlsforge/aegov-mcp"
]
}
}
} {
"servers": {
"dlsforge-aegov-mcp": {
"command": "npx",
"args": [
"-y",
"@dlsforge/aegov-mcp"
]
}
}
} codex mcp add dlsforge-aegov-mcp -- npx -y @dlsforge/aegov-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dlsforge-aegov-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@dlsforge/aegov-mcp"
],
"enabled": true
}
}
} openclaw mcp add dlsforge-aegov-mcp --command npx --arg -y --arg @dlsforge/aegov-mcp
mcp_servers:
dlsforge-aegov-mcp:
command: "npx"
args: ["-y", "@dlsforge/aegov-mcp"] {
"McpServers": {
"dlsforge-aegov-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@dlsforge/aegov-mcp"
]
}
}
} assistant mcp add dlsforge-aegov-mcp -t stdio -c npx -a -y @dlsforge/aegov-mcp
{
"mcpServers": {
"dlsforge-aegov-mcp": {
"command": "npx",
"args": [
"-y",
"@dlsforge/aegov-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 −3
- Stability: pass → 0.80 functional
- 26 Sept 26 +1
- Stability: 0.97 → pass security
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 30 Sept 2026 · Analysed npm/@dlsforge/aegov-mcp@0.2.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
getComponent Get a UAE Design System component ~153
Return the full official record for one UAE Design System (AEGOV DLS) artifact: canonical markup, variant examples (copy these rather than inventing markup), rules (accessibility, RTL/bilingual, usage), class inventory and provenance. Accepts a component class-root ('aegov-btn'), a docs name ('Button', 'Checkbox'), a block or pattern id ('header', 'emirates-id-input'), or any member class ('aegov-check-item'). Use listComponents to discover identifiers. Always respect the returned rules; markup must keep the official aegov-* classes.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Component class-root, docs name, block/pattern id, or member class (case-insensitive) |
No output schema declared.
No examples provided.
getTokens Get UAE Design System design tokens ~132
Return the UAE Design System's resolved design tokens (CSS custom properties) from the pinned @aegov/design-system package: colours (OKLCH palettes incl. semantic primary/secondary), typography scale, fonts, shadows and container widths. Generated markup must use these tokens or the aegov-* component classes built on them — never arbitrary hard-coded values. Filter by category and/or a name substring (e.g. category 'color', query 'primary').
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Token category to filter by |
| query | string | – | Case-insensitive substring of the token name, e.g. 'primary' |
No output schema declared.
No examples provided.
listComponents List UAE Design System components ~141
List every artifact of the UAE Design System (AEGOV DLS) this server can describe: package components (authoritative classes + official markup), blocks, patterns, and docs-only components. Call this first to discover what exists and the exact identifier to pass to getComponent. Package-tier data is authoritative for the pinned @aegov/design-system version; docs-tier data comes from designsystem.gov.ae and is provisional. When building a full page, note the standard page furniture: every UAE government page carries the header block, the footer block, and the page-rating block ('Did you find this content useful?') near the end of the page content.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ping Ping ~50
Health check for the AEGOV DLS MCP server. Returns 'pong', echoing back an optional message. Use to confirm the server is connected.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | Optional message to echo back |
No output schema declared.
No examples provided.
scaffoldEmiratesId Scaffold an Emirates ID input ~202
Generate the standard Emirates ID form control (AEGOV DLS aegov-form-control): accepts 15 raw digits, auto-formats to the printed-card format 784-XXXX-XXXXXXX-X, validates the mandatory pattern ^784-\d{4}-\d{7}-\d$, bilingual labels, plus a masked display (784-1945-XXXXXXX-X) with an explicit reveal control. Emirates ID format, masking and pattern validation are non-negotiable for UAE government services — use this scaffold rather than hand-rolling. Returns html, the auto-format script, the masked-display snippet, and the official pattern rules.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | HTML id/name for the input (also prefixes the hint and display ids) |
| language | string | – | Label/hint language(s). 'both' emits bilingual labels (English + Arabic) |
| maskedDisplay | boolean | – | Include the masked read-back display + reveal control snippet |
No output schema declared.
No examples provided.
scaffoldUaePass Scaffold a UAE Pass button ~274
Generate official-guideline UAE Pass button markup (UAE Pass is the mandatory national digital identity — any government login must use it). Emits AEGOV DLS classes with the documented wording, appearance and logo rules from docs.uaepass.ae, the OAuth2 authorize URL template with staging/production endpoints, and links to the official logo assets. Returns bilingual (English + Arabic) markup by default; Arabic strings are generated and flagged for native review. Follow the returned rules and notes — they are the standard, not suggestions.
| Name | Type | Req | Description |
|---|---|---|---|
| appearance | string | – | Permitted appearances only. black: for white/light backgrounds; white: for dark or colored backgrounds with sufficient contrast; outline: light backgrounds where the white fill lacks contrast |
| environment | string | – | UAE Pass OAuth2 environment for the endpoint set |
| language | string | – | Markup language(s). 'both' returns English and Arabic (RTL) variants |
| radius | string | – | Documented corner-radius options: default (standard, 12px), rectangle (minimum), pill (maximum) |
| variant | string | – | Documented button wording: sign-in/sign-up (authentication; never both on one page), login (synonym flow — don't mix with sign-in wording), continue (document sharing — requires user disclosure), sig… |
No output schema declared.
No examples provided.
validate_snippet Validate an HTML snippet against the UAE Design System ~184
Validate generated HTML against the AEGOV DLS: verifies every aegov-* class against the pinned @aegov/design-system version (certain), checks other classes against official docs-example usage (best-effort), and runs UAE-specific checks — Emirates ID inputs must validate ^784-\d{4}-\d{7}-\d$ and displayed IDs must be masked, images need alt, Arabic content needs RTL handling, dates must be DMY (day/month/year, never month-first). If the snippet is a documented block (it carries aegov-header or aegov-footer), it is also checked against that block's conformance contract — the mobile menu affordance, the footer's mobile accordion. Call this on every snippet you emit before showing it to the user; fix errors and re-validate.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | The HTML snippet to validate |
No output schema declared.
No examples provided.
What is the io.github.dlsforge/aegov-mcp server?
io.github.dlsforge/aegov-mcp is listed in the public MCP registry as io.github.dlsforge/aegov-mcp. UAE Design System (AEGOV DLS) for AI assistants: components, tokens, validation. Not TDRA-official. This page covers its npm package (@dlsforge/aegov-mcp).
Is the io.github.dlsforge/aegov-mcp server safe to use?
io.github.dlsforge/aegov-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 30 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.dlsforge/aegov-mcp server expose?
io.github.dlsforge/aegov-mcp exposes 7 tools: ping, listComponents, getComponent, getTokens, scaffoldUaePass, and 2 more. Their descriptions and schemas cost roughly 1,136 tokens of context every time the server is loaded.
Is the io.github.dlsforge/aegov-mcp server still maintained?
io.github.dlsforge/aegov-mcp is still listed as active in the MCP registry. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.dlsforge/aegov-mcp server under?
io.github.dlsforge/aegov-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.