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.

Kadmo agent runtime

NPM · @KADMO/CLI

Kadmo agent runtime on your computer: workflows, skill packs and Chrome automation for AI agents

Available components

+4 this week 60 Trust /100

Last scanned (21 hours ago)

Scores higher than 29% of npm servers

Category Browser Automation

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @fastify/static 9.3.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 49 of 172 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4435 tokens (~130/item across 34 items; 34 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 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 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 34 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 (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

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.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

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.

  • 19 Nov 26 +1

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

  • 17 Nov 26 +3
    • Stability: unverified → 0.17 ▲ functional
  • 13 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Nov 26 41

    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/@kadmo/cli@0.5.1

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 12 findings
ID CVE Severity Vector Fix available
GHSA-83w8-p2f5-377r CVE-2026-15074 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-8pvw-jcv7-9cmj CVE-2026-7120 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-7q85-xj36-vmfc CVE-2026-77301 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-8238-w5pm-2374 CVE-2026-114102 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-c6fg-446q-cg94 CVE-2026-114103 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-j5f4-cc29-5x44 CVE-2026-102282 high CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-p634-w6r4-rjp2 CVE-2026-114104 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-rcw4-f5rp-g42v CVE-2026-92000 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vwc7-r8mq-g2x9 CVE-2026-76845 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N no
GHSA-xcpc-8h2w-3j85 CVE-2026-39244 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-3g3m-2fjr-6pw4 CVE-2026-118773 medium yes
GHSA-g3hv-75wg-m249 CVE-2026-118764 medium yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 172 packages
Packages resolved 172
Stale 49
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 34 exposed · ~4,435 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
browser_batch ~664

Run a SEQUENCE of browser actions in ONE call instead of one round trip per action. Each step is the same shape you would pass to the individual tool, plus a "cmd" field naming which tool to run. A batch is a DETERMINISTIC run: actions you already know the selectors for, executed top to bottom, halting at the first failure (unless on_error:"continue"). By default it ends by returning a fresh accessibility snapshot of the resulting page, so you can decide the next move in the same turn. The moment you need to SEE something before choosing an action, end the batch and read the returned snapshot. Guidance: - Prefer CSS selectors over refs inside a batch. Refs come from a prior snapshot and go stale the instant a step re-renders the page; selectors survive. - After a navigate (or an action that loads new content), add a { "cmd": "wait", "selector": "..." } step before interacting with the new content. - Add "optional": true to a step whose failure should not halt the batch. - Add "return": "drop" to a side-effect-only step you do not need echoed back (e.g. a screenshot taken only to trigger lazy-load). Batchable cmds: navigate, wait, exists, click, type, fill, press_key, select_option, scroll, scroll_into_view, hover, extract, extract_all, extract_map, snapshot, screenshot, inject_css, evaluate. To capture a redacted screenshot in one call: navigate → inject_css (blur the sensitive selectors) → wait → screenshot with a "path". The shot lands on disk already redacted and no image bytes come back. Example — log in then land on the dashboard in one call: { "steps": [ { "cmd": "navigate", "url": "https://app.example.com/login" }, { "cmd": "wait", "selector": "#user" }, { "cmd": "fill", "selector": "#user", "value": "alice" }, { "cmd": "fill", "selector": "#pw", "value": "secret" }, { "cmd": "click", "selector": "button[type=submit]" }, { "cmd": "wait", "selector": ".dashboard" } ] }

NameTypeReqDescription
on_errorstring–"stop" (default): halt at the first failed step, marking the rest skipped. "continue": run every step regardless.
snapshot_tailboolean–Append a fresh accessibility snapshot of the final page to the response so you can decide the next action (default: true). Skipped automatically when the last step is already a snapshot or screenshot…
stepsarrayyesOrdered list of actions. Each item is { "cmd": "<tool name>", ...that tool's arguments }. Optional per-step keys: "optional" (boolean — failure never halts the batch) and "return": "drop" (omit this…
tabstring–The tab every step drives (a handle such as "t2" from list_tabs or new_tab); a step may name its own "tab". Default: this session's current tab.

No output schema declared.

No examples provided.

capture_page ~55

Capture selectors and interactive elements from the current page.

NameTypeReqDescription
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.

No output schema declared.

No examples provided.

clear_basic_auth ~104

Remove stored HTTP Basic Auth credentials. Omit "origin" to clear all stored credentials; pass "origin" to clear just that site.

NameTypeReqDescription
originstring–Optional origin to clear (e.g. "https://staging.example.com"). Omit to clear all stored credentials.
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.

No output schema declared.

No examples provided.

click ~104

Click an element on the page.

NameTypeReqDescription
elementstring–Human-readable element description (for logging).
refnumber–Element reference from snapshot (the number after ref=).
selectorstring–CSS selector for the element. Supports :has-text("text") pseudo-selector.
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.

No output schema declared.

No examples provided.

close_tab ~55

Close a tab of THIS session by its handle. A tab the person lent to the session goes back to them instead of closing.

NameTypeReqDescription
tabstringyesThe handle of the tab to close (e.g. "t2").

No output schema declared.

No examples provided.

evaluate ~86

Execute JavaScript in the browser page context and return the result. Useful for reading page state, checking values, or performing calculations.

NameTypeReqDescription
jsstringyesJavaScript code to evaluate in the page context.
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.

No output schema declared.

No examples provided.

exists ~99

Check if an element exists on the page. Returns true/false without throwing. Useful for conditional logic.

NameTypeReqDescription
selectorstringyesCSS selector to check.
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.
timeoutnumber–How long to wait before returning false, in milliseconds (default: 2000).

No output schema declared.

No examples provided.

extract ~63

Extract text content from an element.

NameTypeReqDescription
selectorstringyesCSS selector for the element.
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.

No output schema declared.

No examples provided.

extract_all ~126

Extract text from all elements matching a selector, joined by a separator. Useful for getting lists of items, table columns, or repeated elements.

NameTypeReqDescription
attributestring–Optional attribute to extract instead of text content (e.g., "href", "src").
selectorstringyesCSS selector matching multiple elements.
separatorstring–String to join results with (default: "\n").
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.

No output schema declared.

No examples provided.

extract_map ~130

Extract structured data from repeated elements. For each element matching the outer selector, extracts named fields using sub-selectors. Returns JSON array of objects.

NameTypeReqDescription
fieldsobjectyesMap of field names to extraction rules. Each rule has a "selector" (relative CSS selector) and optional "attribute".
selectorstringyesCSS selector for the repeating container elements (e.g., "table tbody tr", ".card").
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.

No output schema declared.

No examples provided.

fill ~123

Fill a form field by setting its value programmatically. Unlike "type" (which simulates keystrokes), "fill" sets the value directly and triggers React/Vue/Angular change events. Use this for framework-controlled inputs where "type" doesn't work.

NameTypeReqDescription
selectorstringyesCSS selector for the input element.
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.
valuestringyesValue to set on the input.

No output schema declared.

No examples provided.

get_browser_status ~44

Check if the browser extension is connected, and list this session's window and tabs (protocol 2) or the one shared tab and who holds it (protocol 1).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_run_log ~35

Retrieve the execution log for a completed workflow run.

NameTypeReqDescription
run_idstringyesThe run ID returned from run_workflow

No output schema declared.

No examples provided.

get_workflow ~30

Get detailed information about a specific workflow.

NameTypeReqDescription
workflow_idstringyesUnique identifier of the workflow

No output schema declared.

No examples provided.

hover ~67

Hover over an element (positions cursor for scroll targeting).

NameTypeReqDescription
selectorstringyesCSS selector for the element.
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.

No output schema declared.

No examples provided.

inject_css ~159

Inject a CSS rule into the current page. The main use is pre-capture redaction: blur or hide sensitive elements, then screenshot to a file, so no unredacted image ever exists. Pass an id to make the injection replaceable — injecting the same id again swaps the rule rather than stacking a second one.

NameTypeReqDescription
cssstringyesCSS to inject, e.g. ".user-email { filter: blur(6px); }"
idstring–Optional identifier for the injected style element, so it can be replaced or removed later.
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.

No output schema declared.

No examples provided.

list_run_logs ~41

List recent workflow execution logs.

NameTypeReqDescription
limitnumber–Maximum number of logs to return
workflow_idstring–Filter logs by workflow ID

No output schema declared.

No examples provided.

list_tabs ~65

List the tabs of THIS session's browser window: each tab's handle ("t1", "t2", …), URL and title, which one is current (the one a call without "tab" drives), and which the person lent. Other sessions' tabs are never listed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_workflows ~26

List all available workflow automations.

NameTypeReqDescription
sourcestring–Filter by source

No output schema declared.

No examples provided.

navigate ~65

Navigate the connected browser tab to a URL.

NameTypeReqDescription
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.
urlstringyesThe URL to navigate to

No output schema declared.

No examples provided.

new_tab ~103

Open a new tab in THIS session's browser window and return its handle. Pass that handle as "tab" on every call that should drive it; calls without "tab" keep driving the current tab. A sub-agent opens its own tab this way so two agents never share a page.

NameTypeReqDescription
activeboolean–Bring the tab to the front of the window (default: true).
urlstring–The page to open (default: a blank tab).

No output schema declared.

No examples provided.

press_key ~171

Press a key on the keyboard. Use this for keyboard shortcuts, Tab navigation, Enter, Escape, arrow keys, etc. Supports key combinations like "Ctrl+A" or "Shift+Tab".

NameTypeReqDescription
keystringyesKey to press. Examples: "Tab", "Enter", "Escape", "ArrowDown", "Backspace", "Shift+Tab", "Ctrl+A". For single characters, use the character directly (e.g., "a").
refnumber–Optional element reference from snapshot to focus before pressing the key.
selectorstring–Optional CSS selector to focus before pressing the key.
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.

No output schema declared.

No examples provided.

publish_artifact ~374

Publish a piece of evidence (a screenshot, a design mockup, an RCA/coverage report) to the portal RIGHT NOW, mid-session, and get back a paste-ready snippet to cite in your ONE resolution comment on the ticket. The file is uploaded, attached to the ticket automatically, and given a tokenized no-login download link — the snippet contains that link (a portal issue gets a markdown link to the file). A report attached to a ticket is numbered and named by the portal (<KEY>_<playbook>_<step>_<NN>), and its snippet leads with a "Report: #NN <link>" line to paste as it is. Use this the moment you have evidence worth showing, instead of waiting for the end of the session (nothing you save after your comment is written can be cited in it). Works on a dispatched job and for every turn of a live app editing session; on a ticketless/chat job it returns a download link only. Files must be ≤ 25 MB and live under your home directory. On any failure the file is left on disk and still uploads at session end, so save deliverables under artifacts/ as a fallback.

NameTypeReqDescription
captionstring–Optional short label for the snippet. Shown only in the returned snippet as a hint for your comment; it is NOT stored on the artifact.
kindstring–Gallery category. Optional — inferred from the file extension when omitted (images → screenshot, .svg/.html → mock, .pdf/.md/.txt/.csv/.json → report, .mp4/.webm → video).
pathstringyesPath to the file to publish. A relative path resolves against your workspace (~/workspace); an absolute path is also accepted, as long as it stays within your home directory.

No output schema declared.

No examples provided.

publish_report ~322

Hand your step report over to the portal as the LAST action of a dispatched job, instead of posting the ticket comment yourself. The portal records the verdict on the step (the playbook gate reads it from there), writes the ticket comment from your report in the account's report shape — a readable comment, a short summary with the report attached as a numbered file, both, or nothing at all on the quiet shape — translates it when a report language is set, and edits the comment of an earlier call in the same step instead of posting again. Publish evidence with publish_artifact first and pass its links as evidence. Every failure is non-fatal: the result then tells you to post your ONE comment yourself.

NameTypeReqDescription
bodystringyesThe full report in Markdown — the sections your workflow asks for (what changed, how to verify, the handoff checklist, the findings). No closing verdict line: the portal adds it.
evidencearray–Links that evidence the report: the PR, the download links publish_artifact returned (at most 20).
filenamestring–Optional name for the report file (Markdown); the portal numbers it on the ticket when it attaches it.
summarystringyesOne or two sentences: what the step did and where it stands (at most 2,000 characters).
verdictstringyesThe step verdict token, one of the workflow's verdicts (e.g. PR_OPEN, WORK_CONTINUE, BLOCKED, PASS, FAIL). Only the token — never a sentence.

No output schema declared.

No examples provided.

run_workflow ~89

Execute a workflow automation by ID. Returns a run_id for tracking execution status.

NameTypeReqDescription
paramsobject–Key-value parameters required by the workflow
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.
workflow_idstringyesUnique identifier of the workflow

No output schema declared.

No examples provided.

screenshot ~275

Capture a screenshot of the current page. Prefer cropping to a specific area instead of capturing the full viewport — use ref (from snapshot), selector (CSS), or region (manual rect) to save context tokens. Full viewport is fine for first visit to a new page; after that, crop to the relevant section. Pass path to write the PNG to a file instead of returning image bytes — that is what you want for docs screenshots and QA evidence, since the file can then be published with publish_artifact and never enters your context.

NameTypeReqDescription
pathstring–Write the PNG here instead of returning image bytes; returns the path and byte count as text. Accepts ~/... or an absolute path; a relative path resolves against ~/workspace. Must stay inside the hom…
refnumber–Element reference from snapshot (the number after ref=). Crops screenshot to that element with padding.
regionobject–Manual crop region in CSS pixels (viewport coordinates).
selectorstring–CSS selector for the element. Crops screenshot to that element with padding.
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.

No output schema declared.

No examples provided.

scroll ~73

Scroll the page.

NameTypeReqDescription
amountnumber–Scroll amount in pixels (default: 300).
directionstringyesScroll direction.
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.

No output schema declared.

No examples provided.

scroll_into_view ~98

Scroll a specific element into the viewport. More precise than "scroll" — targets an exact element.

NameTypeReqDescription
blockstring–Vertical alignment in viewport (default: "center").
selectorstringyesCSS selector for the element to scroll into view.
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.

No output schema declared.

No examples provided.

select_option ~167

Select an option from a native <select> dropdown element. Use this instead of click for <select> elements, as native dropdowns cannot be controlled via click events.

NameTypeReqDescription
elementstring–Human-readable element description (for logging).
labelstring–The visible text of the option to select (matches <option> text content).
refnumber–Element reference from snapshot (the number after ref=).
selectorstring–CSS selector for the <select> element.
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.
valuestring–The option value to select (matches <option value="...">).

No output schema declared.

No examples provided.

select_profile ~86

List the Chrome profiles connected to the runtime (one Kadmo extension per profile), or move THIS session to one of them. Moving closes the session's window in the old profile; the next browser call opens it in the new one.

NameTypeReqDescription
profilestring–The profile's label (e.g. "Chrome · a9f3") or install id; omit to list them.

No output schema declared.

No examples provided.

set_basic_auth ~190

Provide HTTP Basic Auth credentials so the browser logs in silently instead of showing the native username/password modal, which would otherwise block the page and hang automation. Applies to the connected tab. Omit "origin" to use the credentials for any site that challenges; pass "origin" (e.g. "https://staging.example.com") to scope them to one site. When a challenge has no matching credentials it is dismissed so the page never hangs.

NameTypeReqDescription
originstring–Optional origin to scope the credentials to (e.g. "https://staging.example.com"). Omit to apply to any challenged site.
passwordstringyesBasic Auth password.
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.
usernamestringyesBasic Auth username.

No output schema declared.

No examples provided.

snapshot ~134

Capture accessibility snapshot of the current page. Returns YAML with element refs for use with click/type. Use includeContent=true to also include visible text content as markdown. Note: taking a snapshot may dismiss inline modals or popups — use screenshot instead if you need to verify modal content.

NameTypeReqDescription
includeContentboolean–Include visible text content in the snapshot as markdown (default: false). Useful for reading articles, documentation, or any page content.
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.

No output schema declared.

No examples provided.

type ~111

Type text into an input element.

NameTypeReqDescription
elementstring–Human-readable element description.
refnumber–Element reference from snapshot.
selectorstring–CSS selector for the input element.
submitboolean–Press Enter after typing (default: false).
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.
textstringyesText to type.

No output schema declared.

No examples provided.

wait ~101

Wait for an element to appear on the page. Blocks until the element matching the selector exists in the DOM, or throws after timeout.

NameTypeReqDescription
selectorstringyesCSS selector to wait for.
tabstring–The tab to drive: a handle of this session such as "t2" (list_tabs, new_tab). Default: the session's current tab.
timeoutnumber–Maximum wait time in milliseconds (default: 5000).

No output schema declared.

No examples provided.

Install

How do I install the Kadmo agent runtime MCP server?

Kadmo agent runtime runs locally as an npm package, launched with npx -y @kadmo/cli 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 · @kadmo/cli

# add to Claude Code
claude mcp add ai-kadmo-kadmo-agent -- npx -y @kadmo/cli mcp
Common questions

What is the Kadmo agent runtime MCP server?

Kadmo agent runtime is an MCP server listed in the public MCP registry as ai.kadmo/kadmo-agent. Kadmo agent runtime on your computer: workflows, skill packs and Chrome automation for AI agents. This page covers its npm package (@kadmo/cli).

Is the Kadmo agent runtime MCP server safe to use?

Kadmo agent runtime scores 60 out of 100 on VerifyMCP. We recorded 12 known advisories against it as of 21 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.

What tools does the Kadmo agent runtime MCP server expose?

Kadmo agent runtime exposes 34 tools: run_workflow, get_run_log, list_workflows, get_workflow, list_run_logs, and 29 more. Their descriptions and schemas cost roughly 4,435 tokens of context every time the server is loaded.

Is the Kadmo agent runtime MCP server still maintained?

Kadmo agent runtime 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 Kadmo agent runtime MCP server under?

Kadmo agent runtime declares the UNLICENSED licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

What did VerifyMCP test on the Kadmo agent runtime MCP server?

VerifyMCP ran 15 checks on Kadmo agent runtime, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Kadmo agent runtime: Security disclosure. 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.