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.

Pre-Trip compliance scanner

NPM · PRETRIP-MCP · SCANNED SEP 25

Screen regulated-health marketing copy against source-cited rulesets, all 50 states.

Available components

npm · pretrip-mcp 77
0 this week 77 Trust /100
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 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
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (GPL-2.0-or-later).Pass
  • Actively maintained (last published 60 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 304 tokens (~152/item across 2 items; 2 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 Management83
  • Stability observed for 25 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
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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
Install

How do I install the Pre-Trip compliance scanner MCP server?

Pre-Trip compliance scanner runs locally as an npm package, launched with npx -y pretrip-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 · pretrip-mcp

# add to Claude Code
claude mcp add agency-kesey-pretrip -- npx -y pretrip-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "agency-kesey-pretrip": {
      "command": "npx",
      "args": [
        "-y",
        "pretrip-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "agency-kesey-pretrip": {
      "command": "npx",
      "args": [
        "-y",
        "pretrip-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add agency-kesey-pretrip -- npx -y pretrip-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "agency-kesey-pretrip": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "pretrip-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add agency-kesey-pretrip --command npx --arg -y --arg pretrip-mcp
# ~/.hermes/config.yaml
mcp_servers:
  agency-kesey-pretrip:
    command: "npx"
    args: ["-y", "pretrip-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "agency-kesey-pretrip": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "pretrip-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add agency-kesey-pretrip -t stdio -c npx -a -y pretrip-mcp
// mcp.json
{
  "mcpServers": {
    "agency-kesey-pretrip": {
      "command": "npx",
      "args": [
        "-y",
        "pretrip-mcp"
      ]
    }
  }
}
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.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 23 Sept 26 0
    • Stability: 0.97 → pass security
  • 22 Sept 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.

  • 20 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
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 25 Sept 2026 · Analysed npm/pretrip-mcp@1.0.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 →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~304 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
get_coverage ~45

Return the verticals, asset types, and states Pre-Trip covers, so scan_content can be called with valid values. Call this when unsure which vertical or state to pass.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scan_content ~259

Screen marketing copy for regulated-health advertising compliance (addiction treatment, ketamine, psilocybin, cannabis, and related verticals) against Pre-Trip's curated, source-cited rulesets. Use this whenever the user is drafting or about to publish a health-marketing email, landing page, blog post, or social post, or asks to check copy for compliance. Returns a pass, or a fix list where each flag quotes the exact line, names the rule, and cites the statute. This is a screen, not legal advice. Call get_coverage first if unsure which vertical or state values are valid.

NameTypeReqDescription
asset_typestringyesThe kind of asset being scanned.
contentstringyesThe marketing copy to check. Plain text or HTML.
covered_entityboolean–True if the advertiser is a HIPAA covered entity (most clinics that bill insurance or hold patient records).
statestringyesTwo-letter US state code you are marketing into, e.g. CA.
subjectstring–Email subject and preview text. Email only.
verticalstringyesThe regulated vertical, e.g. addiction_treatment, ketamine, cannabis. Use get_coverage for the exact list.

No output schema declared.

No examples provided.

Common questions

What is the Pre-Trip compliance scanner MCP server?

Pre-Trip compliance scanner is an MCP server listed in the public MCP registry as agency.kesey/pretrip. Screen regulated-health marketing copy against source-cited rulesets, all 50 states. This page covers its npm package (pretrip-mcp).

Is the Pre-Trip compliance scanner MCP server safe to use?

Pre-Trip compliance scanner scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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 Pre-Trip compliance scanner MCP server expose?

Pre-Trip compliance scanner exposes 2 tools: scan_content, get_coverage. Their descriptions and schemas cost roughly 304 tokens of context every time the server is loaded.

Is the Pre-Trip compliance scanner MCP server still maintained?

Pre-Trip compliance scanner is still listed as active in the MCP registry. We last reached this channel on 25 September 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 Pre-Trip compliance scanner MCP server under?

Pre-Trip compliance scanner declares the GPL-2.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.