ArcSync
NPM · ARCSYNC-MCP
Architecture graphs from Terraform, CDK, CloudFormation, Pulumi and ARM, for coding agents
Available components
Last scanned (28 minutes ago)
Scores higher than 26% of npm servers
Category Cloud Infrastructure
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to VanLandinghamLabs/arcsync-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
- Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
- Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Tool Safety0
- Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
- Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need 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 the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
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.
- 5 Nov 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- Package version: 0.3.4 → 0.3.5 functional
- 4 Nov 26 −43
- Known CVEs: pass → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Dependency health: pass → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 0.3.2 → 0.3.4 functional
- Package version: 0.3.2 → 0.3.3 functional
- 3 Nov 26 0
- Package version: 0.3.1 → 0.3.2 functional
- 2 Nov 26 +43
- Injection markers: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Dependency health: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 85 functional
- 1 Nov 26 38
First indexed and scored.
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 5 Nov 2026 · Analysed npm/arcsync-mcp@0.3.5
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | VanLandinghamLabs/arcsync-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/VanLandinghamLabs/arcsync-mcp/.github/workflows/publish.yml@refs/tags/v0.3.5 |
| Rekor log index | 3692369584 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:809517896452a6620220c7f40fb7ae15177b33dfe614ba560ab6af485ab551ccf27e18c90689c50570dd68fe1a1ff2bd852a3e6444d94139e07a1ce8c |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
describe_resource Describe a resource ~121
Describe one resource in an ArcSync diagram: its type, IaC attributes, and every relationship in and out (what it calls, reads, is attached to, or is contained by). `resource` may be the resource id, its name, or a substring; an ambiguous match returns the candidates to choose from.
| Name | Type | Req | Description |
|---|---|---|---|
| graphId | string | yes | The diagram's graphId, as list_diagrams or get_diagram returns it. The id start_parse returned also works. |
| resource | string | yes | Resource id, name, or a substring of either. |
No output schema declared.
No examples provided.
get_delta Get an infrastructure delta ~124
Show what changed in a diagram's infrastructure. Without `version`, returns the pull-request delta for a PR-branch diagram: resources added, removed and changed compared with the base branch. With `version` (a timestamp from list_versions), compares that version with the one before it, or with the latest parse when `against` is "live".
| Name | Type | Req | Description |
|---|---|---|---|
| against | string | – | – |
| graphId | string | yes | The diagram's graphId, as list_diagrams or get_diagram returns it. The id start_parse returned also works. |
| version | string | – | – |
No output schema declared.
No examples provided.
get_diagram Get an ArcSync diagram ~116
Fetch one architecture diagram ArcSync parsed from infrastructure-as-code. `format: "mermaid"` (default) returns a Mermaid flowchart to show or embed; `format: "json"` returns the resources and relationships as lists to reason over. Both include a link to the interactive canvas. Prefer this to inferring architecture from source files.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
| graphId | string | yes | The diagram's graphId, as list_diagrams or get_diagram returns it. The id start_parse returned also works. |
No output schema declared.
No examples provided.
get_diagram_source Get an authored diagram's source ~59
Return the stored ArcSync source text of an authored diagram (one pushed with push_diagram), to edit and push again. Takes the graphId push_diagram returned.
| Name | Type | Req | Description |
|---|---|---|---|
| graphId | string | yes | The graphId push_diagram returned. |
No output schema declared.
No examples provided.
get_parse_status Check a parse ~95
Report the progress of a parse started with start_parse: status (pending, running, completed, failed, cancelled), the current phase and percentage, and the error when it failed. Takes the graphId start_parse returned, or the canonical graphId a completed parse reports.
| Name | Type | Req | Description |
|---|---|---|---|
| graphId | string | yes | The diagram's graphId, as list_diagrams or get_diagram returns it. The id start_parse returned also works. |
No output schema declared.
No examples provided.
list_diagrams List ArcSync diagrams ~102
List the architecture diagrams in the caller's ArcSync workspace (one per repository, branch and IaC path), newest first. Use it to find the graphId for a repository before calling get_diagram, describe_resource or get_delta. Optional `query` filters by repository URL, owner, repo name, branch, path or project type.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum rows (default 25). |
| query | string | – | Case-insensitive substring filter. |
No output schema declared.
No examples provided.
list_icons List diagram icons ~76
List the icon ids a diagram node can use in `@{ icon: "..." }` (aws:lambda, azure:function-apps, gcp:cloud-storage, generic ones such as user), grouped by vendor. `query` filters by substring.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Case-insensitive substring, e.g. lambda. |
No output schema declared.
No examples provided.
list_versions List diagram versions ~92
List the saved versions of a diagram (one per re-parse, newest first) with the commit each came from and how much it changed. Pass a version's `timestamp` to get_delta to see what it changed. Version history is a Pro feature.
| Name | Type | Req | Description |
|---|---|---|---|
| graphId | string | yes | The diagram's graphId, as list_diagrams or get_diagram returns it. The id start_parse returned also works. |
No output schema declared.
No examples provided.
push_diagram Push an authored diagram ~147
Validate ArcSync diagram source locally, then store it as a private diagram in the caller's workspace. Pushing the same diagramId again updates that diagram. Returns the canvas link and an embed link for Notion. Counts against the workspace's diagram and hourly limits; call validate_diagram first.
| Name | Type | Req | Description |
|---|---|---|---|
| diagramId | string | – | Defaults to the `%% diagram:` id in the source's first block, else a slug of the source's title. |
| source | string | yes | The diagram as markdown holding ```arcsync fenced blocks (Mermaid flowchart or stateDiagram-v2 syntax with @{ } node metadata). |
| title | string | – | Defaults to the source's own title. |
No output schema declared.
No examples provided.
start_parse Diagram a repository ~184
Ask ArcSync to clone a GitHub repository and parse its infrastructure-as-code (Terraform, CloudFormation, AWS CDK, Pulumi, Azure ARM, Serverless Framework) into a diagram. Returns a graphId at once; poll get_parse_status until it completes, then call get_diagram. Uses one parse from the workspace's monthly quota (CDK and Pulumi also use a server-side synth), so call list_diagrams first and reuse a diagram that already exists. Private repositories need the ArcSync GitHub App installed.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Defaults to the repository's default branch, or main when ArcSync cannot look it up. Pass it when you know it. |
| path | string | – | Subdirectory holding the IaC, when it is not at the repository root. |
| repoUrl | string | yes | https://github.com/owner/repo |
No output schema declared.
No examples provided.
validate_diagram Validate an authored diagram ~103
Check ArcSync diagram source (```arcsync blocks) locally, without pushing it: reports OK with node and edge counts, or INVALID with one line per problem (block:line:column, and a suggestion when one exists). Run it, fix every error, then call push_diagram.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | The diagram as markdown holding ```arcsync fenced blocks (Mermaid flowchart or stateDiagram-v2 syntax with @{ } node metadata). |
No output schema declared.
No examples provided.
How do I install the ArcSync MCP server?
ArcSync runs locally as an npm package, launched with npx -y arcsync-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 · arcsync-mcp
claude mcp add vanlandinghamlabs-arcsync-mcp -- npx -y arcsync-mcp
What is the ArcSync MCP server?
ArcSync is an MCP server listed in the public MCP registry as io.github.VanLandinghamLabs/arcsync-mcp. Architecture graphs from Terraform, CDK, CloudFormation, Pulumi and ARM, for coding agents. This page covers its npm package (arcsync-mcp).
Is the ArcSync MCP server safe to use?
ArcSync scores 49 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 ArcSync MCP server expose?
ArcSync exposes 11 tools: list_diagrams, get_diagram, describe_resource, list_versions, get_delta, and 6 more. Their descriptions and schemas cost roughly 1,219 tokens of context every time the server is loaded.
Is the ArcSync MCP server still maintained?
ArcSync is still listed as active in the MCP registry. We last reached this channel on 5 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 ArcSync MCP server under?
ArcSync declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.