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.

org.velocms/mcp

NPM · @VELOCMS/MCP

Draft, publish, and manage your VeloCMS blog from Claude, Cursor, or any MCP client.

Available components

+1 this week 78 Trust /100

Last scanned (14 hours ago)

Scores higher than 58% 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 @modelcontextprotocol/sdk 1.30.0, 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 & Transparency45
Schema Quality & AI Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1080 tokens (~90/item across 12 items; 12 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 Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 76% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_post" implies "delete" 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 12 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.

  • 13 Nov 26 0
    • Package version: 0.1.1 → 0.1.3 functional
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 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.

  • 8 Nov 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.

  • 6 Nov 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.

  • 5 Nov 26 −3
    • Stability: pass → 0.80 functional
  • 30 Oct 26 0
    • Stability: 0.97 → pass security
  • 29 Oct 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.

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 15 Nov 2026 · Analysed npm/@velocms/mcp@0.1.3

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 7 findings
ID CVE Severity Vector Fix available
GHSA-22jm-h49p-29qw CVE-2026-111767 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-46jr-4wx8-v453 CVE-2026-111768 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-6qxp-vccf-f47h CVE-2026-104850 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-f897-62hf-6gxq high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rvq5-wwqv-78pq CVE-2026-111771 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
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 · 12 exposed · ~1,080 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
create_post ~198

Creates a new blog post. Defaults to status=draft — pass status=published to publish immediately (stamps published_at automatically), or create as a draft and call publish_post once you're ready. Requires the posts:write scope.

NameTypeReqDescription
contentHtmlstring–Post body as HTML.
contentJson––TipTap ProseMirror JSON document (arbitrary structure). Prefer contentHtml unless you specifically need to write a ProseMirror document.
excerptstring––
seoDescriptionstring–SEO meta description, max 160 chars.
seoTitlestring–SEO meta title, max 60 chars.
slugstring–Auto-generated from title if omitted.
statusstring–draft (default) or published. Publishing here stamps published_at automatically — or create as draft and call publish_post later.
tagsarray––
titlestringyesPost title. Required.

No output schema declared.

No examples provided.

delete_post ~39

Permanently deletes a post by ID. Requires the posts:write scope.

NameTypeReqDescription
idstringyesPocketBase record ID of the post to delete.

No output schema declared.

No examples provided.

get_post ~50

Fetches a single post by its PocketBase record ID, including content_html/content_json and SEO fields. Requires the posts:read scope.

NameTypeReqDescription
idstringyesPocketBase record ID of the post.

No output schema declared.

No examples provided.

get_site_settings ~56

Fetches the tenant's site configuration (name, description, logo, favicon, members/comments enabled flags). Encrypted fields (Stripe keys, AI API key) are always excluded by the API. Requires the site-settings:read scope.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_comments ~107

Lists comments, paginated. Optionally filter to a specific post (postId) and/or by moderation status (approved, pending, spam). Requires the comments:read scope.

NameTypeReqDescription
pageinteger–Page number (1-based). Default: 1.
perPageinteger–Records per page, max 100. Default: 20.
postIdstring–Filter to comments on a specific post.
statusstring–Filter by moderation status.

No output schema declared.

No examples provided.

list_media ~94

Lists items in the media library, paginated. Optionally filter by MIME type prefix (e.g. 'image'). Requires the media:read scope.

NameTypeReqDescription
pageinteger–Page number (1-based). Default: 1.
perPageinteger–Records per page, max 100. Default: 20.
typestring–Filter by MIME type prefix (e.g. 'image').

No output schema declared.

No examples provided.

list_members ~104

Lists reader/subscriber records, paginated. Email local parts are masked by the API (e.g. u***@example.com). Optionally filter by tier (free or paid). Requires the members:read scope.

NameTypeReqDescription
pageinteger–Page number (1-based). Default: 1.
perPageinteger–Records per page, max 100. Default: 20.
tierstring–Filter by subscription tier (free or paid).

No output schema declared.

No examples provided.

list_posts ~99

Lists blog posts for the authenticated tenant, paginated (default 20/page, max 100). Optionally filter by status (draft or published). Requires the posts:read API key scope.

NameTypeReqDescription
pageinteger–Page number (1-based). Default: 1.
perPageinteger–Records per page, max 100. Default: 20.
statusstring–Filter by post status (draft or published).

No output schema declared.

No examples provided.

moderate_comment ~65

Sets a comment's moderation status (approved, pending, or spam). Requires the comments:moderate scope.

NameTypeReqDescription
idstringyesPocketBase record ID of the comment to moderate.
statusstringyesModeration status to apply: approved, pending, or spam.

No output schema declared.

No examples provided.

publish_post ~56

Sets a post's status to published (stamps published_at). Shorthand for update_post({ status: 'published' }). Requires the posts:write scope.

NameTypeReqDescription
idstringyesPocketBase record ID of the post to publish.

No output schema declared.

No examples provided.

unpublish_post ~61

Sets a post's status back to draft, taking it off the public site. Shorthand for update_post({ status: 'draft' }). Requires the posts:write scope.

NameTypeReqDescription
idstringyesPocketBase record ID of the post to unpublish.

No output schema declared.

No examples provided.

update_post ~151

Partially updates an existing post — only the fields you pass are changed. Requires at least one field besides id. Requires the posts:write scope.

NameTypeReqDescription
contentHtmlstring––
contentJson––TipTap ProseMirror JSON document.
excerptstring––
idstringyesPocketBase record ID of the post to update.
seoDescriptionstring––
seoTitlestring––
slugstring––
statusstring–draft or published. Transitioning draft -> published stamps published_at automatically. Prefer publish_post/unpublish_post for a status-only change.
tagsarray––
titlestring––

No output schema declared.

No examples provided.

Install

How do I install the org.velocms/mcp server?

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

# add to Claude Code
claude mcp add org-velocms-mcp -- npx -y @velocms/mcp
Common questions

What is the org.velocms/mcp server?

org.velocms/mcp is listed in the public MCP registry as org.velocms/mcp. Draft, publish, and manage your VeloCMS blog from Claude, Cursor, or any MCP client. This page covers its npm package (@velocms/mcp).

Is the org.velocms/mcp server safe to use?

org.velocms/mcp scores 78 out of 100 on VerifyMCP. We recorded 7 known advisories against it as of 15 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 org.velocms/mcp server expose?

org.velocms/mcp exposes 12 tools: list_posts, get_post, create_post, update_post, delete_post, and 7 more. Their descriptions and schemas cost roughly 1,080 tokens of context every time the server is loaded.

Is the org.velocms/mcp server still maintained?

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

org.velocms/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.

What did VerifyMCP test on the org.velocms/mcp server?

VerifyMCP ran 16 checks on org.velocms/mcp, 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.