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.

Markasso

Owner verified

NPM · @MARKASSO/MCP

Let AI agents draw and edit Markasso diagrams, offline or live on a shared whiteboard.

Available components

83 Trust /100

Last scanned (17 hours ago)

Scores higher than 73% of npm servers

Category Design and Media

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 Security98
  • 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
  • 31 of 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to AlbertoBarrago/markasso). 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 Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1635 tokens (~86/item across 19 items; 19 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 20 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.

  • 21 Nov 26 +12
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.87 ▲ functional
  • 20 Nov 26 −7
    • Known CVEs: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.10 → unverified ▼ security
    • Schema quality: 76 → 86 ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Dependency health: 0.87 → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Tool coverage: 50% → 100% ▲ functional
    • First check of Schema quality: unverified functional
    • Destructive annotations: All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
    • Package version: 0.7.5 → 0.7.6 functional
  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 77

    First indexed and scored.

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/@markasso/mcp@0.7.6

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 AlbertoBarrago/markasso
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/AlbertoBarrago/markasso/.github/workflows/mcp-release.yml@refs/tags/mcp-v0.7.6
Rekor log index 4022805189
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:bfed2396b2ab61987f9d338a004b78c32644abe3a596cbfe485ecd2a899ba5d9d51fdefa895965edbc68238e54adceeb4b8a9b80e9a60dbb4918bd48e

Background: How many MCP packages publish verified provenance →

Dependencies 105 packages
Packages resolved 105
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 19 exposed · ~1,342 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
diagram_add_nodes ~68

Add one or more nodes in a single step. Give each a short unique key. Positions are optional: call diagram_layout afterwards. Example: nodes=[{key:"api",label:"API"},{key:"db",kind:"database"}].

NameTypeReqDescription
nodesarrayyesNodes to add

No output schema declared.

No examples provided.

diagram_connect ~59

Connect nodes by key with arrows or lines, in a single step. Connectors follow the nodes when they move. Example: edges=[{from:"api",to:"db",label:"SQL"}].

NameTypeReqDescription
edgesarrayyesConnections to add

No output schema declared.

No examples provided.

diagram_disconnect ~53

Remove connections, each by id (see diagram_read) or by from/to keys. The nodes stay. Example: edges=[{from:"api",to:"db"}].

NameTypeReqDescription
edgesarrayyesConnections to remove

No output schema declared.

No examples provided.

diagram_export_png ~118

Render the diagram as a PNG image, returned so you can look at it, and optionally saved to a file. Lists layout warnings (connections through nodes, overlaps, crossings) when there are any. To only refresh a preview file, set path and returnImage: false.

NameTypeReqDescription
backgroundstring–Canvas background (default dark)
pathstring–Absolute path ending in .png (optional)
returnImageboolean–Return the image (default true). false with a path only writes the file and answers in text.

No output schema declared.

No examples provided.

diagram_export_svg ~43

Export the diagram as an SVG image file.

NameTypeReqDescription
backgroundstring–Canvas background (default dark)
pathstringyesAbsolute path ending in .svg

No output schema declared.

No examples provided.

diagram_layout ~82

Arrange nodes in layers following their connections (TB = top to bottom, LR = left to right). Use after adding nodes. Reports layout warnings (connections through nodes, overlaps, crossings) when there are any. Example: direction="LR".

NameTypeReqDescription
directionstring–Flow direction (default TB)
keysarray–Only these nodes (default: all)

No output schema declared.

No examples provided.

diagram_new ~20

Start a new empty diagram (leaves any live session).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

diagram_open ~66

Open a .markasso file path or a Markasso share link (https://markasso.it/#s=...). Replaces the current diagram. Example: source="/Users/me/flow.markasso".

NameTypeReqDescription
sourcestringyesAbsolute .markasso path or markasso.it share link

No output schema declared.

No examples provided.

diagram_read ~30

Describe the current diagram: nodes (key, kind, label, position, size), connections and layout warnings.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

diagram_remove ~39

Remove nodes by key; their connections are removed too. Example: keys=["cache"].

NameTypeReqDescription
keysarrayyesKeys of the nodes to remove

No output schema declared.

No examples provided.

diagram_save ~42

Save the diagram as a .markasso file (open it in the app with File > Open).

NameTypeReqDescription
pathstringyesAbsolute path ending in .markasso

No output schema declared.

No examples provided.

diagram_share ~30

Publish the diagram and return a markasso.it link anyone can open. The answer says when the link expires.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

diagram_update ~147

Change a node's label, color, font size, position (top-left x/y) or size. Example: key="api", label="Gateway".

NameTypeReqDescription
colorstring–Color name
fontSizenumber–Text size in px (text nodes default 20, shape labels 16, icon labels 14). Auto-sized nodes grow to fit.
heightnumber–Height in px
keystringyesKey of the node to change
labelstring–New label
widthnumber–Width in px
xnumber–Left edge in px
ynumber–Top edge in px

No output schema declared.

No examples provided.

diagram_update_edge ~218

Change a connection's label (empty string removes it), label font size, routing, heads, dash or color. Pick it by id or by from/to keys. Example: from="api", to="db", dashed=true.

NameTypeReqDescription
arrowstring–Which ends get a head (default end)
colorstring–Color name
dashedboolean–Dashed line
endHeadstring–triangle/diamond for UML (inheritance, aggregation)
fontSizenumber–Label text size in px (default 12)
fromstring–Key of the start node
idstring–Connection id shown by diagram_read
labelstring–Current label, when several connections join the same nodes
newLabelstring–New label
routingstring–elbow = orthogonal route (good for flowcharts)
startHeadstring–Head style at the start
tostring–Key of the end node

No output schema declared.

No examples provided.

icons_search ~64

Find icons for kind "icon": Markasso generic architecture icons and the Kubernetes set.

NameTypeReqDescription
limitinteger–Max results (default 30)
querystringyese.g. "database", "queue", "pod", "ingress"; empty lists all

No output schema declared.

No examples provided.

live_join ~102

Join a Markasso live session (link with ?live=...) and draw on that board in real time. If the room has content it becomes the current diagram; if it is empty, the current diagram is published to it.

NameTypeReqDescription
linkstringyesLive session link from Markasso (Start live session at the top right, or the prompt from Invite AI agent)
namestring–Name shown to people in the room (default "AI agent")

No output schema declared.

No examples provided.

live_leave ~19

Leave the live session. The diagram stays loaded locally.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

live_reply ~67

Answer a request from a person in the live room. The answer appears under your name in their participant list. Keep it short; the board itself shows what you changed.

NameTypeReqDescription
requestIdstringyesId of the request
textstringyesShort answer shown to the person

No output schema declared.

No examples provided.

live_wait_request ~75

On a live board, wait until a person in the room sends you a request, then return it (with its id for live_reply). Returns empty-handed after the timeout: call it again to keep listening.

NameTypeReqDescription
timeoutSecondsinteger–How long to wait (default 50; some clients time out after 60)

No output schema declared.

No examples provided.

Install

How do I install the Markasso MCP server?

Markasso runs locally as an npm package, launched with npx -y @markasso/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 · @markasso/mcp

# add to Claude Code
claude mcp add albertobarrago-markasso -- npx -y @markasso/mcp
Common questions

What is the Markasso MCP server?

Markasso is an MCP server listed in the public MCP registry as io.github.AlbertoBarrago/markasso. Let AI agents draw and edit Markasso diagrams, offline or live on a shared whiteboard. This page covers its npm package (@markasso/mcp). Its publisher has verified ownership with us.

Is the Markasso MCP server safe to use?

Markasso scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 Markasso MCP server expose?

Markasso exposes 19 tools: diagram_new, diagram_open, diagram_read, diagram_add_nodes, diagram_connect, and 14 more. Their descriptions and schemas cost roughly 1,342 tokens of context every time the server is loaded.

Is the Markasso MCP server still maintained?

Markasso 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 Markasso MCP server under?

Markasso 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 Markasso MCP server?

VerifyMCP ran 16 checks on Markasso, 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.