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.veldica/publishready

NPM · @VELDICA/PUBLISHREADY-MCP · SCANNED SEP 20

PublishReady: Deterministic writing control with local-first metrics and AI prose audits.

0 this week 95 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
  • 35 of 106 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to veldica/publishready-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 144 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1344 tokens (~51/item across 26 items; 16 tools + 10 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 98% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 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 io.github.veldica/publishready MCP server?

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

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

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

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

  • 12 Sept 26 +1

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

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
  • 8 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.

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 20 Sept 2026 · Analysed npm/@veldica/publishready-mcp@1.0.5

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo veldica/publishready-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/veldica/publishready-mcp/.github/workflows/publish.yml@refs/heads/main
Rekor log index 1396668991
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:06dd71bdf3a55cf222b6b41be8ecf1812ca0b1ffa6964df8bee967dadbab01764a02320ed8fefbd7b297bb17960735300fc9223a353d7c51902df68b6

Background: How many MCP packages publish verified provenance →

Dependencies 106 packages
Packages resolved 106
Stale 35
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~1,173 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
analyze_against_targets ~84

Check text against an explicit target profile. Use this before rewriting. After producing a revision, call compare_text_versions with the same targets to verify movement.

NameTypeReqDescription
optionsobjectOptional flags for expanding the structured response.
targetsobjectyesNumeric constraints to check against the analyzed text.
textstringyesEnglish prose or markdown-ish content to evaluate.
NameTypeReqDescription
ai_analysisobject
consensus_gradenumberyes
consensus_sourcesarrayyes
countsobjectyes
detailsobjectyes
excluded_formulasarrayyes
fiction_metricsobject
fitobject
formulasarrayyes
interpretationsobject
lexical_metricsobjectyes
metadataobjectyes
paragraph_metricsobjectyes
readability_bandstringyes
recommended_nextobject
revision_leversarrayyes
scannability_metricsobjectyes
sentence_metricsobjectyes
summaryyes
targetsyesNested numeric target profile for deterministic writing checks.
template_infoobject
violationsarrayyes
word_tracking_metricsobject

No examples provided.

analyze_against_template ~86

Check text against a built-in template. Use this before revising. After revision, call compare_text_versions with the same template_id to verify alignment.

NameTypeReqDescription
optionsobjectOptional flags for expanding the structured response.
template_idstringyesID of the built-in template to check against.
textstringyesEnglish prose or markdown-ish content to evaluate.
NameTypeReqDescription
ai_analysisobject
consensus_gradenumberyes
consensus_sourcesarrayyes
countsobjectyes
detailsobjectyes
excluded_formulasarrayyes
fiction_metricsobject
fitobject
formulasarrayyes
interpretationsobject
lexical_metricsobjectyes
metadataobjectyes
paragraph_metricsobjectyes
readability_bandstringyes
recommended_nextobject
revision_leversarrayyes
scannability_metricsobjectyes
sentence_metricsobjectyes
summaryyes
targetsyesNested numeric target profile for deterministic writing checks.
template_infoobject
violationsarrayyes
word_tracking_metricsobject

No examples provided.

analyze_text ~81

Return a deterministic writing analysis. MUST be used as the first step in most revision workflows to establish a baseline. After analysis, call suggest_revision_levers for optimization advice.

NameTypeReqDescription
optionsobjectOptional flags for expanding the structured response.
textstringyesEnglish prose or markdown-ish content to analyze. Blank input is accepted and returns zeroed metrics.
NameTypeReqDescription
ai_analysisobject
consensus_gradenumberyes
consensus_sourcesarrayyes
countsobjectyes
detailsobjectyes
excluded_formulasarrayyes
fiction_metricsobject
fitobject
formulasarrayyes
interpretationsobject
lexical_metricsobjectyes
metadataobjectyes
paragraph_metricsobjectyes
readability_bandstringyes
recommended_nextobject
revision_leversarrayyes
scannability_metricsobjectyes
sentence_metricsobjectyes
summaryyes
targetsyesNested numeric target profile for deterministic writing checks.
template_infoobject
violationsarrayyes
word_tracking_metricsobject

No examples provided.

audit_ai_sounding_prose ~135

Run the Veldica AI marker inventory directly. Returns marker density, weighted score, style band, categories, exact matches, tracked phrases, and supporting writing metrics. Use this when text feels generic, over-polished, formulaic, or AI-like.

NameTypeReqDescription
include_formula_breakdownbooleanInclude readability formula detail objects in the response.
include_matchesbooleanInclude individual marker matches with line/column positions.
textstringyesEnglish prose or markdown-ish content to audit.
track_wordsarrayOptional extra words or phrases to count alongside the built-in AI marker catalog.
NameTypeReqDescription
ai_analysisobject
consensus_gradenumberyes
consensus_sourcesarrayyes
countsobjectyes
detailsobjectyes
excluded_formulasarrayyes
fiction_metricsobject
fitobject
formulasarrayyes
interpretationsobject
lexical_metricsobjectyes
metadataobjectyes
paragraph_metricsobjectyes
readability_bandstringyes
recommended_nextobject
revision_leversarrayyes
scannability_metricsobjectyes
sentence_metricsobjectyes
summaryyes
targetsyesNested numeric target profile for deterministic writing checks.
template_infoobject
violationsarrayyes
word_tracking_metricsobject

No examples provided.

build_reference_profile ~51

Generate a Fingerprint Profile from one or more high-quality reference texts.

NameTypeReqDescription
profile_namestringOptional name for the reference profile.
textsarrayyesOne or more reference texts to aggregate.
NameTypeReqDescription
consensus_gradenumberyes
countsobjectyes
fiction_metricsobject
lexical_metricsobjectyes
namestring
paragraph_metricsobjectyes
profile_idstring
readability_bandstringyes
scannability_metricsobjectyes
sentence_metricsobjectyes
source_countinteger
source_sha256string
summarystring
timestampstringyesStable content-derived timestamp used to keep profile outputs deterministic.

No examples provided.

compare_profiles ~42

Compare two writing profiles, explicit target profiles, or templates.

NameTypeReqDescription
profile_ayesFirst profile or template ID.
profile_byesSecond profile or template ID.
NameTypeReqDescription
alignment_scorenumberyes
largest_differencesarrayyes
profile_a_namestring|nullyes
profile_b_namestring|nullyes
strongest_similaritiesarrayyes

No examples provided.

compare_text_versions ~128

Compare original and revised drafts. MUST be called after any revision to verify mechanical improvement and factual integrity. It returns a 'quality_gate' which acts as a final decision object.

NameTypeReqDescription
original_textstringyesThe original draft.
reference_profileobjectOptional reusable reference profile to compare both versions against.
reference_textstringOptional reference sample to compare both versions against.
revised_textstringyesThe revised draft.
targetsobjectOptional numeric target profile to compare movement against.
template_idstringOptional template to check improvement against.
NameTypeReqDescription
comparisonobjectyes
content_integrityobjectyes
improvementsarrayyes
metrics_deltaobjectyes
movementstringyes
quality_gateobjectyes
recommended_nextobject
reference_alignmentyes
regressionsarrayyes
stable_traitsarrayyes
summarystringyes
target_fityes
template_fityes

No examples provided.

compare_to_reference ~59

Compare current text against a specific Fingerprint Profile.

NameTypeReqDescription
candidate_textstringyesThe text to evaluate.
reference_profileobjectPreviously built reference profile to compare against.
reference_textstringReference text to compare against.
NameTypeReqDescription
alignment_scorenumberyes
candidate_summarystring
largest_differencesarrayyes
metricsobjectyes
recommended_nextobject
reference_namestringyes
reference_summarystring
reference_targetsobjectyesNested numeric target profile for deterministic writing checks.
revision_leversarrayyes
strongest_similaritiesarrayyes

No examples provided.

find_hotspots ~74

Locate specific sentences or paragraphs for surgical revision. Each hotspot includes a 'hotspot_id' and 'revision_instruction'. After editing, MUST call compare_text_versions to verify the fix.

NameTypeReqDescription
template_idstringOptional template to influence hotspot detection.
textstringyesText to analyze for structural or lexical hotspots.
NameTypeReqDescription
ai_analysisobject
consensus_gradenumberyes
consensus_sourcesarrayyes
countsobjectyes
detailsobjectyes
excluded_formulasarrayyes
fiction_metricsobject
fitobject
formulasarrayyes
interpretationsobject
lexical_metricsobjectyes
metadataobjectyes
paragraph_metricsobjectyes
readability_bandstringyes
recommended_nextobject
revision_leversarrayyes
scannability_metricsobjectyes
sentence_metricsobjectyes
summaryyes
targetsyesNested numeric target profile for deterministic writing checks.
template_infoobject
violationsarrayyes
word_tracking_metricsobject

No examples provided.

find_reference_drift ~63

Detect if current writing samples are drifting away from a reference profile.

NameTypeReqDescription
candidate_textstringyesThe text to evaluate for drift.
reference_profileobjectReference profile to compare against.
reference_textstringReference text to compare against.
NameTypeReqDescription
alignment_scorenumberyes
changing_traitsarrayyes
drift_detectedbooleanyes
drift_pointsarrayyes
impact_areasarrayyes
recommended_nextobject
reference_targetsobjectyesNested numeric target profile for deterministic writing checks.
stable_traitsarrayyes
summarystringyes

No examples provided.

get_template ~35

Return the full details of a specific template including its numeric targets.

NameTypeReqDescription
template_idstringyesID of the template to retrieve.
NameTypeReqDescription
audiencestringyes
descriptionstringyes
familystringyes
hard_failsobjectyesTarget failures that should usually block publication for this profile.
idstringyes
namestringyes
revision_prioritiesarrayyesOrdered deterministic levers to try first when the template does not fit.
signal_interpretationsobjectyesTemplate-specific explanations for the most important metrics.
soft_preferencesobjectyesSignals that shape the intended feel but may be traded off deliberately.
targetsobjectyesNested numeric target profile for deterministic writing checks.
tradeoffsarrayyesKnown style tradeoffs users should consider before optimizing mechanically.
use_casestringyes

No examples provided.

interpret_targets ~37

Explain the human implications, likely audience, and tradeoffs of a set of numeric targets.

NameTypeReqDescription
targetsobjectyesNumeric targets to interpret.
NameTypeReqDescription
coherence_warningsarrayyes
implicationsarrayyes
likely_audiencearrayyes
likely_use_casesarrayyes
nearest_templatesarrayyes
style_implicationsarrayyes
tradeoffsarrayyes

No examples provided.

list_templates ~85

Return a list of available writing templates with their metadata.

NameTypeReqDescription
audiencestringCase-insensitive substring filter for template audience.
familystringFilter templates by family.
querystringCase-insensitive search across ID, name, description, audience, and use case.
use_casestringCase-insensitive substring filter for template use case.
NameTypeReqDescription
countintegeryes
templatesarrayyes

No examples provided.

plan_revision_workflow ~92

Generate a step-by-step tool-call sequence for a specific revision task (e.g., fact-preserving revision, template alignment). Use this when you are unsure which tool to call next.

NameTypeReqDescription
reference_textstringReference text for reference_match.
taskstringyes
template_idstringTemplate ID for template_revision.
textstringyesThe text to be revised.
NameTypeReqDescription
acceptance_gateobjectyes
initial_toolstringyes
reasonstringyes
stepsarrayyes

No examples provided.

suggest_revision_levers ~87

Rank deterministic revision levers. Use this before rewriting to identify high-impact changes. After revision, MUST call compare_text_versions to verify style improved without factual loss.

NameTypeReqDescription
optionsobjectOptional ranking output flags.
targetsobjectOptional numeric targets that should influence lever ranking.
textstringyesEnglish prose or markdown-ish content to analyze for ranked revision leverage.
NameTypeReqDescription
ai_analysisobject
consensus_gradenumberyes
consensus_sourcesarrayyes
countsobjectyes
detailsobjectyes
excluded_formulasarrayyes
fiction_metricsobject
fitobject
formulasarrayyes
interpretationsobject
lexical_metricsobjectyes
metadataobjectyes
paragraph_metricsobjectyes
readability_bandstringyes
recommended_nextobject
revision_leversarrayyes
scannability_metricsobjectyes
sentence_metricsobjectyes
summaryyes
targetsyesNested numeric target profile for deterministic writing checks.
template_infoobject
violationsarrayyes
word_tracking_metricsobject

No examples provided.

summarize_writing_profile ~34

Generate a fingerprint profile from a text sample.

NameTypeReqDescription
textstringyesEnglish prose to summarize into a writing profile.
NameTypeReqDescription
nearest_templatesarrayyes
notable_traitsobjectyes
profileobjectyes
summarystringyes

No examples provided.

Common questions

What is the io.github.veldica/publishready MCP server?

io.github.veldica/publishready is an MCP server listed in the public MCP registry as io.github.veldica/publishready. PublishReady: Deterministic writing control with local-first metrics and AI prose audits. This page covers its npm package (@veldica/publishready-mcp).

Is the io.github.veldica/publishready MCP server safe to use?

io.github.veldica/publishready scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.veldica/publishready MCP server expose?

io.github.veldica/publishready exposes 16 tools: analyze_text, analyze_against_targets, audit_ai_sounding_prose, suggest_revision_levers, analyze_against_template, and 11 more. Their descriptions and schemas cost roughly 1,173 tokens of context every time the server is loaded.

Is the io.github.veldica/publishready MCP server still maintained?

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

io.github.veldica/publishready declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.