Marketo MCP Server

marketo-mcp-server npm v1.4.0

Published by zleventer — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Marketo — 45 tools covering leads, programs, emails, forms, smart lists, static lists, channels, landing pages, bulk export, analytics, and admin utilities

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([marketo_browse_folders, marketo_get_bulk_export_file]) co-exist with external-action tools ([marketo_get_lead_activities]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [marketo_browse_folders, marketo_get_bulk_export_file] → sinks [marketo_get_lead_activities]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow marketo_browse_folders → marketo_get_lead_activities

Tools 44

Each tool and what it can reach — statically extracted from the published source.

  • marketo_browse_foldersingests untrusted input
  • marketo_get_bulk_export_fileingests untrusted input
  • marketo_get_lead_activitiesnetwork egress
  • marketo_add_leads_to_listno sensitive capability
  • marketo_approve_formno sensitive capability
  • marketo_change_program_statusno sensitive capability
  • marketo_clone_emailno sensitive capability
  • marketo_clone_formno sensitive capability
  • marketo_clone_landing_pageno sensitive capability
  • marketo_clone_programno sensitive capability
Show 34 more tools ↓
  • marketo_clone_program_with_tokensno sensitive capability
  • marketo_create_bulk_export_leadsno sensitive capability
  • marketo_create_channelno sensitive capability
  • marketo_create_or_update_leadsno sensitive capability
  • marketo_delete_leadno sensitive capability
  • marketo_describe_lead_fieldsno sensitive capability
  • marketo_enqueue_bulk_exportno sensitive capability
  • marketo_find_dead_programsno sensitive capability
  • marketo_get_activities_paging_tokenno sensitive capability
  • marketo_get_bulk_export_statusno sensitive capability
  • marketo_get_channel_by_idno sensitive capability
  • marketo_get_channelsno sensitive capability
  • marketo_get_email_by_idno sensitive capability
  • marketo_get_emailsno sensitive capability
  • marketo_get_engagement_program_healthno sensitive capability
  • marketo_get_form_by_idno sensitive capability
  • marketo_get_formsno sensitive capability
  • marketo_get_landing_page_by_idno sensitive capability
  • marketo_get_landing_pagesno sensitive capability
  • marketo_get_lead_by_emailno sensitive capability
  • marketo_get_lead_by_idno sensitive capability
  • marketo_get_lead_listsno sensitive capability
  • marketo_get_lead_timelineno sensitive capability
  • marketo_get_program_by_idno sensitive capability
  • marketo_get_program_membersno sensitive capability
  • marketo_get_programsno sensitive capability
  • marketo_get_smart_campaign_mapno sensitive capability
  • marketo_get_smart_list_by_idno sensitive capability
  • marketo_get_smart_listsno sensitive capability
  • marketo_list_activity_typesno sensitive capability
  • marketo_rank_campaign_engagementno sensitive capability
  • marketo_remove_leads_from_listno sensitive capability
  • marketo_search_campaigns_by_filterno sensitive capability
  • marketo_send_sampleno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.4.0 latest A 96/100 1 1.13.0 2026-09-08

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/marketo-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/marketo-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/marketo-mcp-server"><img src="https://mcptrustchecker.com/registry/marketo-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/marketo-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan marketo-mcp-server --online

Use the free API → How scoring works

More in Other