io.github.arose26/zapier-dev-mcp
NPM · ZAPIER-DEV-MCP · SCANNED AUG 17
For Zapier integration developers: inspect, lint, and validate zapier-platform-cli projects.
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 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
- 30 of 96 dependencies flagged as unhealthy. 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 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 309 tokens (~77/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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 · zapier-dev-mcp
claude mcp add arose26-zapier-dev-mcp -- npx -y zapier-dev-mcp
codex mcp add arose26-zapier-dev-mcp -- npx -y zapier-dev-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"arose26-zapier-dev-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"zapier-dev-mcp"
],
"enabled": true
}
}
} openclaw mcp add arose26-zapier-dev-mcp --command npx --arg -y --arg zapier-dev-mcp
mcp_servers:
arose26-zapier-dev-mcp:
command: "npx"
args: ["-y", "zapier-dev-mcp"] {
"mcpServers": {
"arose26-zapier-dev-mcp": {
"command": "npx",
"args": [
"-y",
"zapier-dev-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.
- 16 Aug 26 0
- Security disclosure: unverified → fail ▼ functional
- 15 Aug 26 70
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 17 Aug 2026 · Analysed npm/zapier-dev-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
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.
generate_test_fixtures Generate test fixtures ~104
Ready-to-run test scaffolds for the integration: a bundle mock (authData from the auth fields, typed inputData from each component's input fields) plus a zapier-platform appTester test skeleton per trigger/create/search. Optionally target one component.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | – | Limit to one component, e.g. 'triggers.new_message' or 'new_message' |
| path | string | yes | Path to a zapier-platform-cli integration project directory |
No output schema declared.
No examples provided.
inspect_integration Inspect a Zapier integration ~69
Structured summary of a zapier-platform-cli project: triggers, creates, searches, authentication, platform version, request hooks. Note: this evaluates the project's own entry module (exactly as the Zapier CLI does).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to a zapier-platform-cli integration project directory |
No output schema declared.
No examples provided.
lint_integration Lint for review readiness ~74
Checks a Zapier integration against common app-review blockers: missing sample data, unlabeled input fields, missing descriptions/nouns, dynamic dropdowns referencing nonexistent triggers, version mismatches. Complements (does not replace) `zapier validate`.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to a zapier-platform-cli integration project directory |
No output schema declared.
No examples provided.
validate_integration Run zapier validate ~62
Runs the project's own `zapier validate` (schema + style checks) via npx. Requires zapier-platform-cli in the project or globally; returns install guidance if missing.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path to a zapier-platform-cli integration project directory |
No output schema declared.
No examples provided.