org.velocms/mcp
NPM · @VELOCMS/MCP · SCANNED OCT 1
Draft, publish, and manage your VeloCMS blog from Claude, Cursor, or any MCP client.
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 → 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 93 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 42 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add org-velocms-mcp -- npx -y @velocms/mcp
{
"mcpServers": {
"org-velocms-mcp": {
"command": "npx",
"args": [
"-y",
"@velocms/mcp"
]
}
}
} {
"servers": {
"org-velocms-mcp": {
"command": "npx",
"args": [
"-y",
"@velocms/mcp"
]
}
}
} codex mcp add org-velocms-mcp -- npx -y @velocms/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-velocms-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@velocms/mcp"
],
"enabled": true
}
}
} openclaw mcp add org-velocms-mcp --command npx --arg -y --arg @velocms/mcp
mcp_servers:
org-velocms-mcp:
command: "npx"
args: ["-y", "@velocms/mcp"] {
"McpServers": {
"org-velocms-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@velocms/mcp"
]
}
}
} assistant mcp add org-velocms-mcp -t stdio -c npx -a -y @velocms/mcp
{
"mcpServers": {
"org-velocms-mcp": {
"command": "npx",
"args": [
"-y",
"@velocms/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.
- 1 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.
- 29 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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 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.
- 26 Sept 26 −3
- Stability: pass → 0.80 functional
- 25 Sept 26 0
- 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 +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.
- 22 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
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 1 Oct 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 →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
create_post Create a 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.
| Name | Type | Req | Description |
|---|---|---|---|
| contentHtml | string | – | Post body as HTML. |
| contentJson | – | – | TipTap ProseMirror JSON document (arbitrary structure). Prefer contentHtml unless you specifically need to write a ProseMirror document. |
| excerpt | string | – | – |
| seoDescription | string | – | SEO meta description, max 160 chars. |
| seoTitle | string | – | SEO meta title, max 60 chars. |
| slug | string | – | Auto-generated from title if omitted. |
| status | string | – | draft (default) or published. Publishing here stamps published_at automatically — or create as draft and call publish_post later. |
| tags | array | – | – |
| title | string | yes | Post title. Required. |
No output schema declared.
No examples provided.
delete_post Delete a post ~39
Permanently deletes a post by ID. Requires the posts:write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | PocketBase record ID of the post to delete. |
No output schema declared.
No examples provided.
get_post Get a post ~50
Fetches a single post by its PocketBase record ID, including content_html/content_json and SEO fields. Requires the posts:read scope.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | PocketBase record ID of the post. |
No output schema declared.
No examples provided.
get_site_settings 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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Default: 1. |
| perPage | integer | – | Records per page, max 100. Default: 20. |
| postId | string | – | Filter to comments on a specific post. |
| status | string | – | Filter by moderation status. |
No output schema declared.
No examples provided.
list_media List media ~94
Lists items in the media library, paginated. Optionally filter by MIME type prefix (e.g. 'image'). Requires the media:read scope.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Default: 1. |
| perPage | integer | – | Records per page, max 100. Default: 20. |
| type | string | – | Filter by MIME type prefix (e.g. 'image'). |
No output schema declared.
No examples provided.
list_members 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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Default: 1. |
| perPage | integer | – | Records per page, max 100. Default: 20. |
| tier | string | – | Filter by subscription tier (free or paid). |
No output schema declared.
No examples provided.
list_posts 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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Default: 1. |
| perPage | integer | – | Records per page, max 100. Default: 20. |
| status | string | – | Filter by post status (draft or published). |
No output schema declared.
No examples provided.
moderate_comment Moderate a comment ~65
Sets a comment's moderation status (approved, pending, or spam). Requires the comments:moderate scope.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | PocketBase record ID of the comment to moderate. |
| status | string | yes | Moderation status to apply: approved, pending, or spam. |
No output schema declared.
No examples provided.
publish_post Publish a post ~56
Sets a post's status to published (stamps published_at). Shorthand for update_post({ status: 'published' }). Requires the posts:write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | PocketBase record ID of the post to publish. |
No output schema declared.
No examples provided.
unpublish_post Unpublish a 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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | PocketBase record ID of the post to unpublish. |
No output schema declared.
No examples provided.
update_post Update a 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.
| Name | Type | Req | Description |
|---|---|---|---|
| contentHtml | string | – | – |
| contentJson | – | – | TipTap ProseMirror JSON document. |
| excerpt | string | – | – |
| id | string | yes | PocketBase record ID of the post to update. |
| seoDescription | string | – | – |
| seoTitle | string | – | – |
| slug | string | – | – |
| status | string | – | draft or published. Transitioning draft -> published stamps published_at automatically. Prefer publish_post/unpublish_post for a status-only change. |
| tags | array | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
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 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 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 1 October 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.