Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AAI Gateway

NPM · AAI-GATEWAY

Unified MCP & Skill management gateway, shared across AI agents, 99% context token savings

Available components

0 this week 78 Trust /100

Last scanned (14 hours ago)

Scores higher than 59% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

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 Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 50 of 128 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 567 tokens (~70/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "aai:exec" implies "exec" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 8 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 9 Nov 26 +4
    • Source repository: unverified → pass ▲ security
    • Stability: pass → 0.90 functional
  • 8 Nov 26 −5
    • Provenance: pass → unverified ▼ security
  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 1 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 28 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
Diagnostics

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 21 Nov 2026 · Analysed npm/aai-gateway@1.1.10

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 128 packages
Packages resolved 128
Stale 50
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~567 tokens

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 →

Tool Tokens
aai:exec ~101

Execute any AAI tool action. Read the guide first (call app:*, mcp:import, skill:import, or search:discover) — it contains the required schema and parameters.

NameTypeReqDescription
appstring–Required for app tools, omit or use "gateway" for gateway tools.
argsobject–Arguments for the selected tool.
toolstringyesTool name within the app, not prefixed with app id.

No output schema declared.

No examples provided.

disableApp ~64

Disable one app for the current agent only. If you do not know the app id, call listAllAaiApps first to find it.

NameTypeReqDescription
appstringyesRequired. The app id to disable. Use listAllAaiApps to look up available app ids.

No output schema declared.

No examples provided.

enableApp ~87

Enable or re-enable an app for the current agent. When the user asks to enable, start, turn on, or use a specific app by name, call listAllAaiApps first to check if it is already imported before searching for new tools.

NameTypeReqDescription
appstringyesRequired. The app id to re-enable. Use listAllAaiApps to look up available app ids.

No output schema declared.

No examples provided.

listAllAaiApps ~53

List imported apps (MCP servers and skills) for the current agent. This does not include built-in tools like search:discover, mcp:import, or skill:import — those are always available.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mcp:import ~51

Import an MCP server as a new app. Call this first to get the import guide, then use aai:exec to perform the import. Never ask the user for API keys or secrets in chat.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

removeApp ~93

Remove one AAI Gateway managed import from all agents. If you do not know the app id, call listAllAaiApps first to find it.

NameTypeReqDescription
appstringyesRequired. The imported app id to remove globally. Use listAllAaiApps to look up available app ids.
confirmbooleanyesRequired. Must be true only after the agent explains the global impact and the user explicitly confirms.

No output schema declared.

No examples provided.

search:discover ~80

Find and install new tools. Call this when: 1. The user explicitly asks to search for or install tools. 2. The user's request cannot be fulfilled by any currently available tool — proactively suggest and search for a suitable tool. Before searching, check listAllAaiApps first — the user may already have the app imported (possibly disabled).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

skill:import ~38

Import a local skill as a new app. Call this first to get the import guide, then use aai:exec to perform the import.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the AAI Gateway MCP server?

AAI Gateway runs locally as an npm package, launched with npx -y aai-gateway. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · aai-gateway

# add to Claude Code
claude mcp add gybob-aai-gateway -- npx -y aai-gateway
Common questions

What is the AAI Gateway MCP server?

AAI Gateway is an MCP server listed in the public MCP registry as io.github.gybob/aai-gateway. Unified MCP & Skill management gateway, shared across AI agents, 99% context token savings. This page covers its npm package (aai-gateway).

Is the AAI Gateway MCP server safe to use?

AAI Gateway scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 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 AAI Gateway MCP server expose?

AAI Gateway exposes 8 tools: aai:exec, mcp:import, skill:import, listAllAaiApps, disableApp, and 3 more. Their descriptions and schemas cost roughly 567 tokens of context every time the server is loaded.

Is the AAI Gateway MCP server still maintained?

AAI Gateway is still listed as active in the MCP registry. We last reached this channel on 21 November 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 AAI Gateway MCP server under?

AAI Gateway declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the AAI Gateway MCP server?

VerifyMCP ran 16 checks on AAI Gateway, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.