io.form/uag
NPM · @FORMIO/UAG
The Universal Agent Gateway (UAG) enables in-process agentic automation using Form.io.
Available components
Last scanned (5 hours ago)
Scores higher than 10% of npm servers
Deprecated
This server is marked deprecated in the MCP registry.
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 @modelcontextprotocol/sdk 1.27.1, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 65 of 188 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →
Checks we ran (9)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
Checks we could not complete (5)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.
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 →
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.
- 29 Oct 26 0
- CVE-2026-118663 affects this package: high ▼ security
- 28 Oct 26 0
- CVE-2026-116803 affects this package: high ▼ security
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- CVE-2026-116802 affects this package: high ▼ security
- GHSA-c6gr-qvv4-5v3f no longer affects this package ▲ security
- GHSA-mrv2-3pqr-j5jr no longer affects this package ▲ security
- 23 Oct 26 0
- GHSA-mrv2-3pqr-j5jr affects this package: high ▼ security
- GHSA-c6gr-qvv4-5v3f affects this package: high ▼ security
- 22 Oct 26 0
- CVE-2026-90776 no longer affects this package ▲ security
- CVE-2026-100701 no longer affects this package ▲ security
- CVE-2026-100702 no longer affects this package ▲ security
- CVE-2026-100699 no longer affects this package ▲ security
- CVE-2026-100700 no longer affects this package ▲ security
- 21 Oct 26 0
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
- CVE-2026-111767 affects this package: high ▼ security
- 13 Oct 26 0
- CVE-2026-109345 affects this package: high ▼ security
- GHSA-6688-9rhm-gjv2 no longer affects this package ▲ security
- 12 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 11 Oct 26 −3
- GHSA-6688-9rhm-gjv2 affects this package: high ▼ security
- CVE-2026-104850 affects this package: high ▼ security
- Known CVEs: CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.27.1, a direct dependency. A fixed version is available. security
- Security disclosure: pass → unverified ▼ functional
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 6 Nov 2026 · Analysed npm/@formio/uag@1.11.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 →
Vulnerabilities 29 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-rmxm-3fg6-px4f | CVE-2026-118663 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-39q2-94rc-95cp | CVE-2026-65903 | medium | yes | |
| GHSA-55q2-fjhq-7xh7 | CVE-2026-75838 | medium | yes | |
| GHSA-6688-9rhm-gjv2 | CVE-2026-109345 | low | yes | |
| GHSA-76mc-f452-cxcm | CVE-2026-65902 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N | yes |
| GHSA-c2j3-45gr-mqc4 | CVE-2026-66010 | low | yes | |
| GHSA-c6gr-qvv4-5v3f | CVE-2026-116802 | low | yes | |
| GHSA-cj63-jhhr-wcxv | CVE-2026-65913 | medium | yes | |
| GHSA-cjmm-f4jc-qw8r | CVE-2026-65912 | medium | yes | |
| GHSA-cmwh-pvxp-8882 | CVE-2026-65898 | medium | yes | |
| GHSA-crv5-9vww-q3g8 | CVE-2026-41239 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N | yes |
| GHSA-gvmj-g25r-r7wr | CVE-2026-65900 | low | yes | |
| GHSA-h7mw-gpvr-xq4m | CVE-2026-41240 | medium | yes | |
| GHSA-h8r8-wccr-v5f2 | CVE-2026-65914 | medium | yes | |
| GHSA-hpcv-96wg-7vj8 | CVE-2026-49458 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N | yes |
| GHSA-mrv2-3pqr-j5jr | CVE-2026-116803 | high | yes | |
| GHSA-r47g-fvhr-h676 | CVE-2026-49459 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N | yes |
| GHSA-rp9w-3fw7-7cwq | CVE-2026-49978 | medium | yes | |
| GHSA-v2wj-7wpq-c8vv | CVE-2026-0540 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N | yes |
| GHSA-v8jm-5vwx-cfxm | CVE-2025-15599 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N | yes |
| GHSA-v9jr-rg53-9pgp | CVE-2026-41238 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N | yes |
| GHSA-vxr8-fq34-vvx9 | CVE-2026-65899 | low | yes | |
| GHSA-x4vx-rjvf-j5p4 | CVE-2026-65901 | low | no |
Background: What a vulnerability scan can and cannot prove →
Dependencies 188 packages
| Packages resolved | 188 |
|---|---|
| Stale | 63 |
| No linked repository | 2 |
| 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 →
Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.
How do I install the io.form/uag MCP server?
io.form/uag runs locally as an npm package, launched with npx -y @formio/uag. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @formio/uag
claude mcp add io-form-uag -- npx -y @formio/uag
What is the io.form/uag MCP server?
io.form/uag is an MCP server listed in the public MCP registry as io.form/uag. The Universal Agent Gateway (UAG) enables in-process agentic automation using Form.io. This page covers its npm package (@formio/uag).
Is the io.form/uag MCP server safe to use?
io.form/uag scores 34 out of 100 on VerifyMCP. We recorded 29 known advisories against it as of 6 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.
Is the io.form/uag MCP server still maintained?
io.form/uag is marked deprecated in the MCP registry. We last reached this channel on 6 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 io.form/uag MCP server under?
io.form/uag declares the MIT 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 io.form/uag MCP server?
VerifyMCP ran 9 checks on io.form/uag, covering Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 5 items could not be completed, a gap on our side rather than a finding about io.form/uag: Schema quality, Stability, Tool coverage, Tool safety and 1 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.