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.

io.github.ozten/cantrip

NPM · MCP-SERVER-CANTRIP

MCP server for Cantrip — AI-powered GTM engine for solo founders

Available components

0 this week 78 Trust /100

Last scanned (8 hours ago)

Scores higher than 59% of npm servers

Category Marketing and SEO

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 zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1758 tokens (~92/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "cantrip_next_run" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • 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.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

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

  • 9 Nov 26 +4
    • Source repository: unverified → pass ▲ security
    • Stability: pass → 0.90 functional
  • 8 Nov 26 −5
    • Provenance: pass → unverified ▼ security
  • 3 Nov 26 0
    • Stability: 0.97 → pass security
  • 2 Nov 26 0
    • Stability: pass → 0.97 functional
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 22 Nov 2026 · Analysed npm/mcp-server-cantrip@1.0.5

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 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 96 packages
Packages resolved 96
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 19 exposed · ~1,683 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
cantrip_connect ~66

Start here. Connect this workspace to a Cantrip project by writing a .cantrip.json file. All subsequent commands will target this project automatically. Call without arguments to check the current connection.

NameTypeReqDescription
projectstring–Project name to connect to. Omit to check current connection.

No output schema declared.

No examples provided.

cantrip_entity_add ~363

Create a new entity. Automatically marked as 'accepted'. Fields vary by type: - icp: name, description, demographics, jobs_to_be_done, willingness_to_pay, current_alternatives, priority, is_beachhead - pain_point: description, severity (low|medium|high|critical), frequency (rare|occasional|frequent|constant), evidence - value_prop: framing (required — use instead of 'name'; 'description' is stored in extensions), tagline, evidence - channel: name, channel_type, lifecycle_stage (exploring|testing|scaling|maintaining|killed), cac, estimated_reach, conversion_rate (note: 'description' maps to 'notes' column) - experiment: title (required — use instead of 'name'), hypothesis, description, status (proposed|designed|active|completed|analyzed|abandoned), success_metrics, outcome_notes, value_prop_id, channel_id - competitor: name, description, url, positioning, strengths, weaknesses, pricing_model - contact: name, email, phone, company, role, source, url, notes Extra fields (any field not in the schema above) are stored in extensions. After adding entities, pause and confirm with the user before adding more.

NameTypeReqDescription
descriptionstring–Entity description
entity_typestringyesEntity type: icp, pain_point, value_prop, experiment, channel, competitor, contact
fieldsobject–Additional fields as key-value pairs (e.g. {severity: 'high', frequency: 'constant'})
namestring–Entity name (mapped to 'framing' for value_prop, 'title' for experiment)

No output schema declared.

No examples provided.

cantrip_entity_edit ~138

Edit an existing entity. Fields vary by type (same as cantrip_entity_add). Pass well-known fields directly, and any additional fields in the 'fields' object. Extra fields are stored in extensions.

NameTypeReqDescription
descriptionstring–Updated description
entity_typestringyesEntity type: icp, pain_point, value_prop, experiment, channel, competitor, contact
fieldsobject–Additional fields to update as key-value pairs
idstringyesEntity ID to edit
namestring–Updated name (mapped to 'framing' for value_prop, 'title' for experiment)

No output schema declared.

No examples provided.

cantrip_history ~94

Query the append-only audit trail of all actions taken on the project

NameTypeReqDescription
entitystring–Filter by entity type (e.g. icp, pain_point)
limitnumber–Max events to return (default: 50)
sincestring–Only events after this ISO date
typestring–Filter by event type (e.g. init, entity_created, review_accept)

No output schema declared.

No examples provided.

cantrip_init ~178

Create a new project and connect this workspace to it. Pass 'brief_text' (product brief as text) to auto-extract ICPs, pain points, and value props as inferred entities (costs 5 credits). Or pass 'brief_path' (absolute file path) and the file will be read locally. Without a brief, the project is created empty (free) and you add entities manually. Writes .cantrip.json automatically after creation. After creating a project, add a few entities and confirm them with the user before going deeper.

NameTypeReqDescription
brief_pathstring–Absolute path to a product brief file — will be read locally and sent as text
brief_textstring–Product brief content as text (preferred)
descriptionstringyesOne-line project description
namestringyesProject name

No output schema declared.

No examples provided.

cantrip_meter_balance ~31

Check remaining credits. Returns available credits, reserved credits (held by in-progress operations), and total balance.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

cantrip_meter_history ~42

View recent credit transactions. Shows usage debits, purchases, and running balance.

NameTypeReqDescription
limitnumber–Maximum entries to return (default: 20)

No output schema declared.

No examples provided.

cantrip_meter_tiers ~26

View available credit packs. Shows tier name, credits included, and price.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

cantrip_next ~74

List gap-analysis opportunities — things that would move the project closer to ideal state. Each opportunity has a stable UUID that you can pass to cantrip_next_prompt or cantrip_next_run. Opportunities persist across calls; re-running gap analysis updates existing opportunities rather than replacing them. Review the project snapshot with the user before running opportunities.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

cantrip_next_prompt ~52

Generate a context-rich LLM prompt for an opportunity. Returns a ready-to-use prompt with all relevant ontology context baked in. Zero credit cost.

NameTypeReqDescription
idstringyesOpportunity ID from cantrip_next

No output schema declared.

No examples provided.

cantrip_next_run ~104

Execute an enrichment opportunity with AI. Runs the LLM-powered enrichment inline — either updating existing entities' missing fields (targeted) or generating new entities (bulk). Returns when complete with a summary of what was created or updated. Parallelism: you may run different loop types concurrently (e.g. enrich ICPs + enrich competitors), but the daemon blocks concurrent runs of the same loop type for safety.

NameTypeReqDescription
idstringyesOpportunity ID from cantrip_next

No output schema declared.

No examples provided.

cantrip_project ~131

Manage projects. Actions: - list (default): List all projects in the current team. - update: Update a project's name or description. Uses the connected project unless 'slug' is provided. - delete: Delete a project and all its data. Uses the connected project unless 'slug' is provided.

NameTypeReqDescription
actionstring–Action to perform (default: list)
descriptionstring–New description (update only)
namestring–New display name (update only)
slugstring–Project slug to target. Defaults to the connected project from .cantrip.json.

No output schema declared.

No examples provided.

cantrip_review ~23

List all items pending review (inferred entities and open escalations)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

cantrip_review_accept ~33

Accept an inferred entity, marking it as verified ground truth

NameTypeReqDescription
idstringyesEntity ID to accept

No output schema declared.

No examples provided.

cantrip_review_dismiss ~58

Dismiss an inferred entity or open escalation. For entities: removes from review queue without accepting or rejecting (kept for history). For escalations: closes without resolving.

NameTypeReqDescription
idstringyesEntity or escalation ID to dismiss

No output schema declared.

No examples provided.

cantrip_review_reject ~34

Reject an inferred entity (soft-delete, kept for history)

NameTypeReqDescription
idstringyesEntity ID to reject

No output schema declared.

No examples provided.

cantrip_review_resolve ~43

Resolve an open escalation with a resolution message

NameTypeReqDescription
idstringyesEscalation ID
resolutionstringyesResolution text explaining the decision

No output schema declared.

No examples provided.

cantrip_snapshot ~132

Browse project data at three zoom levels. No args: project overview with entity counts by type and review state, gaps, and review queue size. entity_type only: list all entities of that type (e.g. 'icps', 'pain-points', 'channels'). entity_type + entity_id: show full detail for one entity. This is the primary tool for listing and inspecting entities.

NameTypeReqDescription
entity_idstring–Specific entity ID for detail view
entity_typestring–Entity type to drill into (e.g. 'icps', 'pain-points', 'value-props')

No output schema declared.

No examples provided.

cantrip_status ~61

Check daemon health, authentication, and current project. Returns daemon reachability, authenticated identity (user, team), and the active project from .cantrip.json. When CANTRIP_API_KEY is missing, returns setup instructions with config examples for common MCP clients.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.ozten/cantrip MCP server?

io.github.ozten/cantrip runs locally as an npm package, launched with npx -y mcp-server-cantrip. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mcp-server-cantrip

# add to Claude Code
claude mcp add ozten-cantrip -- npx -y mcp-server-cantrip
Common questions

What is the io.github.ozten/cantrip MCP server?

io.github.ozten/cantrip is an MCP server listed in the public MCP registry as io.github.ozten/cantrip. MCP server for Cantrip, AI-powered GTM engine for solo founders. This page covers its npm package (mcp-server-cantrip).

Is the io.github.ozten/cantrip MCP server safe to use?

io.github.ozten/cantrip scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 22 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 io.github.ozten/cantrip MCP server expose?

io.github.ozten/cantrip exposes 19 tools: cantrip_connect, cantrip_status, cantrip_init, cantrip_project, cantrip_snapshot, and 14 more. Their descriptions and schemas cost roughly 1,683 tokens of context every time the server is loaded.

Is the io.github.ozten/cantrip MCP server still maintained?

io.github.ozten/cantrip is still listed as active in the MCP registry. We last reached this channel on 22 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 io.github.ozten/cantrip MCP server under?

io.github.ozten/cantrip 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 io.github.ozten/cantrip MCP server?

VerifyMCP ran 16 checks on io.github.ozten/cantrip, 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.