An MCP server that connects to Vercel API
Nothing to run from here
ArcSync is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
94/100
trust score
959
downloads a day
local
runs on your machine
1k
downloads in 30d
What it does
Architecture graphs from Terraform, CDK, CloudFormation, Pulumi and ARM, for coding agents
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user arcsync-mcp '--' npx -y arcsync-mcp
# 2 — ask your agent for something these tools do
# list_diagrams, get_diagram, describe_resource and 8 more
ArcSync costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
VAAll 1 server
VanLandinghamLabs1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts ArcSync as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user arcsync-mcp '--' npx -y arcsync-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take ARCSYNC_CLIENT_ID (MCP credential client ID for CI or shared machines; omit to connect in the browser), ARCSYNC_CLIENT_SECRET (MCP credential secret, paired with ARCSYNC_CLIENT_ID) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
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,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Case-insensitive substring filter. |
| limit | integer | no | Maximum rows (default 25). |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| graphId | yes | — | |
| format | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| graphId | yes | — | |
| resource | string | yes | Resource id, name, or a substring of either. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| graphId | yes | — |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| graphId | yes | — | |
| version | string | no | — |
| against | string | no | — |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repoUrl | string | yes | https://github.com/owner/repo |
| branch | string | no | — |
| path | string | no | Subdirectory holding the IaC, when it is not at the repository root. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| graphId | yes | — |
Check a diagram written in ArcSync syntax, locally
No parameter schema on file.
Store a validated diagram and return its canvas and embed links
No parameter schema on file.
Return the source of a pushed diagram, to edit it
No parameter schema on file.
List the icon ids a written diagram can use
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install ArcSync or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 94 / 100
Release 0.3.1 · scanned 2 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score94
Findings2 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest55d0583db9f4bbd8f2e33c103b39797e7921411a2ca66fa957951e086ebc630c
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can execute shell commands or code
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest55d0583db9f4bbd8
Scanned2026-11-02
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.3.1. Pin a release below and the command asks for exactly that one.
0.3.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish ArcSync can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.