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.

page.invoker/mcp

NPM · INVOKER-MCP

Deploy forms and sites to live URLs from AI conversations with automatic form capture.

Available components

0 this week 72 Trust /100

Last scanned (22 hours ago)

Scores higher than 43% of npm servers

Category CI/CD and DevOps

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 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability77
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 550 tokens (~39/item across 14 items; 14 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy" implies "deploy" 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 14 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
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.

  • 4 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.

  • 3 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 28 Oct 26 0
    • Stability: 0.97 → pass security
  • 27 Oct 26 0
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −6
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 21 Oct 26 +1
    • Stability: 0.97 → pass security
  • 20 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +3
    • Stability: 0.83 → 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 4 Nov 2026 · Analysed npm/invoker-mcp@0.1.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 →

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 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~550 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
configure_webhook ~75

Add a webhook to a deployment. Supports generic JSON and Slack-formatted payloads.

NameTypeReqDescription
deployment_idstringyesThe deployment ID
typestring–Webhook type: 'generic' (default) sends JSON, 'slack' sends Slack blocks format
urlstringyesThe webhook URL

No output schema declared.

No examples provided.

delete_webhook ~40

Remove a webhook from a deployment.

NameTypeReqDescription
deployment_idstringyesThe deployment ID
webhook_idstringyesThe webhook ID to delete

No output schema declared.

No examples provided.

deploy ~85

Deploy HTML to a live URL. Returns a public URL accessible immediately. Use {{SUBMIT_URL}} as the form action placeholder — it will be replaced with the real submission endpoint at deploy time.

NameTypeReqDescription
htmlstringyesThe full HTML content to deploy
slugstring–Optional URL slug (lowercase, hyphens). If omitted, a random slug is generated.

No output schema declared.

No examples provided.

get_status ~36

Get the status of a deployment including its URL, submission count, and metadata.

NameTypeReqDescription
idstringyesThe deployment ID to check

No output schema declared.

No examples provided.

get_submissions ~53

Get form submissions for a deployment.

NameTypeReqDescription
idstringyesThe deployment ID
limitnumber–Results per page (default 50)
pagenumber–Page number (default 1)

No output schema declared.

No examples provided.

list_templates ~14

List all available deployment templates

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_webhooks ~29

List all webhooks configured for a deployment.

NameTypeReqDescription
deployment_idstringyesThe deployment ID

No output schema declared.

No examples provided.

login ~25

Sign in to Invoker via browser-based email verification. Opens your browser to complete authentication.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

logout ~17

Sign out of Invoker and clear stored credentials.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

teardown ~31

Delete a deployment. The URL will no longer be accessible.

NameTypeReqDescription
idstringyesThe deployment ID to delete

No output schema declared.

No examples provided.

toggle_notifications ~47

Enable or disable email notifications for new submissions on a deployment.

NameTypeReqDescription
deployment_idstringyesThe deployment ID
enabledbooleanyestrue to enable email notifications, false to disable

No output schema declared.

No examples provided.

update ~47

Update an existing deployment with new HTML content. The URL stays the same.

NameTypeReqDescription
htmlstringyesThe new HTML content to deploy
idstringyesThe deployment ID to update

No output schema declared.

No examples provided.

use_template ~35

Get the full HTML source of a template. You can modify it before deploying.

NameTypeReqDescription
templatestringyesTemplate ID to use

No output schema declared.

No examples provided.

whoami ~16

Show the currently authenticated Invoker user.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the page.invoker/mcp server?

page.invoker/mcp runs locally as an npm package, launched with npx -y invoker-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 · invoker-mcp

# add to Claude Code
claude mcp add page-invoker-mcp -- npx -y invoker-mcp
Common questions

What is the page.invoker/mcp server?

page.invoker/mcp is listed in the public MCP registry as page.invoker/mcp. Deploy forms and sites to live URLs from AI conversations with automatic form capture. This page covers its npm package (invoker-mcp).

Is the page.invoker/mcp server safe to use?

page.invoker/mcp scores 72 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 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 page.invoker/mcp server expose?

page.invoker/mcp exposes 14 tools: list_templates, use_template, deploy, update, teardown, and 9 more. Their descriptions and schemas cost roughly 550 tokens of context every time the server is loaded.

Is the page.invoker/mcp server still maintained?

page.invoker/mcp is still listed as active in the MCP registry. We last reached this channel on 4 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 page.invoker/mcp server under?

page.invoker/mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.