enterprise-architect-mcp

Name: enterprise-architect-mcp
Author: io.github.mm6502

MCPattested

v3.0.0io.github.mm6502EUPL-1.2Updated 26d agonpm GitHub

Read-only search and navigation of Sparx Enterprise Architect .qea model exports

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build

A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.

587Downloads/wk

26d agoLast update

Package

Authorio.github.mm6502

LicenseEUPL-1.2

Version3.0.0

Sourcenpm+mcp-registry

npmenterprise-architect-mcp

GitHubmm6502/enterprise-architect-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

85/100Trusted

✓Listed in Forge index+10/10

✓Identity verified · attested build+20/20

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓npm Trusted Publishing (Sigstore)+5/5

—npm maintainer match+0/5

→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusIdentity verified

PublisherUnverified

SignatureUnsigned

Domain—

Provenance✓ Sigstore-verified · 5d08fcc

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface11 tools · none privileged

Security scan✓ Cleanv2.4.0 · 28d agoHow well does this scan work?

EvalsNone

IndexedAug 28, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

11 tools · none privileged

Statically extracted from the published packagev2.4.0 · 28d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

ea_get_connectorsNo description published

This tool published no description. Forge does not invent one.

ea_get_diagram_elementsGet all elements and connectors placed on a specific diagram: the `diagram` itself, plus `elements` and `connectors`. `elements` already includes free-text `Note` diagram objects, which often carry a legend or abbreviation definitions an agent would otherwise miss. Connectors include feature-link r…

Get all elements and connectors placed on a specific diagram: the `diagram` itself, plus `elements` and `connectors`. `elements` already includes free-text `Note` diagram objects, which often carry a legend or abbreviation definitions an agent would otherwise miss. Connectors include feature-link r…

No input schema was published for this tool.

ea_list_diagramsNo description published

This tool published no description. Forge does not invent one.

ea_get_elementNo description published

This tool published no description. Forge does not invent one.

ea_list_elementsNo description published

This tool published no description. Forge does not invent one.

ea_get_package_treeNavigate the package hierarchy. Without parameters, returns top-level `packages`. With a `packageId`, returns that package's children up to the specified depth. Each node carries `id`, `name`, `parentId`, and `elementCount`.

Navigate the package hierarchy. Without parameters, returns top-level `packages`. With a `packageId`, returns that package's children up to the specified depth. Each node carries `id`, `name`, `parentId`, and `elementCount`.

No input schema was published for this tool.

ea_resolveNo description published

This tool published no description. Forge does not invent one.

ea_get_scenariosGet use case scenario flows for an element. `scenarios` holds the parsed flows; each has `name`, `type`, `notes`, and `steps`, and each step carries `stepNumber` plus its attributes (`trigger`, `uses`, `result`, `state`, `link`). Steps are numbered within each scenario. Scenarios ordered by type: B…

Get use case scenario flows for an element. `scenarios` holds the parsed flows; each has `name`, `type`, `notes`, and `steps`, and each step carries `stepNumber` plus its attributes (`trigger`, `uses`, `result`, `state`, `link`). Steps are numbered within each scenario. Scenarios ordered by type: B…

No input schema was published for this tool.

ea_get_schemaList the model's database tables in `tables`, or pass a `tableName` to get that table's `columns` and `indexes` instead. That form echoes the `table` name and adds `rowidAlias` — the INTEGER PRIMARY KEY aliasing SQLite's rowid, so the fastest lookup path, or null when the table has none — with `row…

List the model's database tables in `tables`, or pass a `tableName` to get that table's `columns` and `indexes` instead. That form echoes the `table` name and adds `rowidAlias` — the INTEGER PRIMARY KEY aliasing SQLite's rowid, so the fastest lookup path, or null when the table has none — with `row…

No input schema was published for this tool.

ea_get_model_infoNo description published

This tool published no description. Forge does not invent one.

ea_searchNo description published

This tool published no description. Forge does not invent one.

4 of 11 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Read-only search and navigation of Sparx Enterprise Architect .qea model exports

Keywords

mcp

Alternatives

Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-06 — observed resolution, not a publisher declaration.

60 packages resolved · 4 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod3.25.76
yargs17.7.37 dependencies
- y18n5.0.8
- cliui8.0.1+2 not drawn1 dependency
  - string-width4.2.3+3 not drawn
- escalade3.2.0
- string-width4.2.3shown above+3 not drawn
- yargs-parser21.1.1
- get-caller-file2.0.5
- require-directory2.1.1
fast-xml-parser5.11.16 dependencies
- strnum2.4.2+1 not drawn
- is-unsafe2.0.2
- xml-naming0.3.0
- fast-xml-builder1.3.12 dependencies
  - xml-naming0.3.0shown above
  - path-expression-matcher1.6.2
- @nodable/entities3.0.0
- path-expression-matcher1.6.2shown above
@modelcontextprotocol/sdk1.30.0+10 not drawn7 dependencies
- ajv8.20.0+4 not drawn
- zod4.5.4
- cors2.8.6+2 not drawn
- hono4.13.7
- jose6.2.12
- express5.2.1incomplete+17 not drawn
- raw-body3.0.2incomplete

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 53

proxy-addr ^2.0.7 — required by express@5.2.1package cap reached
body-parser ^2.2.1 — required by express@5.2.1package cap reached
escape-html ^1.0.3 — required by express@5.2.1package cap reached
http-errors ^2.0.0 — required by express@5.2.1package cap reached
on-finished ^2.4.1 — required by express@5.2.1package cap reached
content-type ^1.0.5 — required by express@5.2.1package cap reached
finalhandler ^2.1.0 — required by express@5.2.1package cap reached
range-parser ^1.2.1 — required by express@5.2.1package cap reached
serve-static ^2.2.0 — required by express@5.2.1package cap reached
cookie-signature ^1.2.1 — required by express@5.2.1package cap reached
merge-descriptors ^2.0.0 — required by express@5.2.1package cap reached
content-disposition ^1.0.0 — required by express@5.2.1package cap reached

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

enterprise-architect-mcp

Tools

Tools exposed

Dependency tree

Declared but not resolved