Kit.com MCP Server
NPM · @DANCUMBERLAND/KIT-MCP · SCANNED AUG 5
Agent-optimized MCP server for Kit.com email marketing. 13 composite tools, 100% V4 API.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 140 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 537 tokens (~41/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @dancumberland/kit-mcp
claude mcp add dancumberland-kit-mcp -- npx -y @dancumberland/kit-mcp
codex mcp add dancumberland-kit-mcp -- npx -y @dancumberland/kit-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dancumberland-kit-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@dancumberland/kit-mcp"
],
"enabled": true
}
}
} openclaw mcp add dancumberland-kit-mcp --command npx --arg -y --arg @dancumberland/kit-mcp
mcp_servers:
dancumberland-kit-mcp:
command: "npx"
args: ["-y", "@dancumberland/kit-mcp"] {
"mcpServers": {
"dancumberland-kit-mcp": {
"command": "npx",
"args": [
"-y",
"@dancumberland/kit-mcp"
]
}
}
} 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 Aug 26 +1
- CVE-2026-69207 no longer affects this package ▲ security
- Known CVEs: fail → partial ▲ security
- 4 Aug 26 +4
- CVE-2026-69207 affects this package: medium ▼ security
- Known CVEs: partial → fail ▼ security
- Stability: unverified → 0.30 ▲ functional
- 2 Aug 26 +43
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: 100 → unverified ▼ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: unverified functional
- Licence: MIT functional
- 31 Jul 26 −25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 46
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 Aug 2026 · Analysed npm/@dancumberland/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
bulk_operations ~50
Batch operations for large-scale subscriber management. Requires OAuth authentication. Actions: create_subscribers, create_tags, tag_subscribers, untag_subscribers, add_to_forms, create_custom_fields, update_custom_fields
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_account ~27
Get a comprehensive overview of your Kit account including creator profile, email stats, and subscriber growth.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
manage_broadcasts ~52
Manage Kit email broadcasts — list with status filter, get details, create drafts or scheduled sends, update, delete, or view performance stats. Actions: list, get, create, update, delete, stats
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
manage_custom_fields ~39
Manage Kit custom subscriber fields — list all fields, create, rename, or delete (destructive). Actions: list, create, update, delete
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
manage_email_templates ~28
List Kit email templates — returns template IDs and names needed for creating broadcasts. Actions: list
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
manage_forms ~53
Manage Kit forms — list all forms, list subscribers who opted in through a form, or add a subscriber to a form (triggers double opt-in if enabled). Actions: list, list_subscribers, add_subscriber
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
manage_purchases ~36
Manage Kit purchases — list, get details, or record a new purchase. Requires OAuth authentication. Actions: list, get, create
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
manage_segments ~28
List Kit subscriber segments (read-only — segments are created in the Kit UI). Actions: list
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
manage_sequences ~40
Manage Kit email sequences — list all sequences, enroll a subscriber, or list subscribers in a sequence. Actions: list, add_subscriber, list_subscribers
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
manage_subscribers ~58
Manage Kit subscribers — find by email/ID, list with filters, create (upsert with tags), update, unsubscribe, view stats, or filter by engagement. Actions: find, list, create, update, unsubscribe, stats, filter
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
manage_tags ~55
Manage Kit tags — list all tags, create, rename, apply/remove tags on subscribers, or list subscribers with a specific tag. Actions: list, create, update, tag_subscriber, untag_subscriber, list_subscribers
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
manage_webhooks ~40
Manage Kit webhooks — list registered webhooks, create new webhook subscriptions for Kit events, or delete webhooks. Actions: list, create, delete
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
test_connection ~31
Verify your Kit API key is valid and check connection status. Use this as the first tool call to confirm setup.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.