Publishready MCP server
io.github.veldica/publishready·v1.0.5·2 starsPublishReady: Deterministic writing control with local-first metrics and AI prose audits.
2 stars47 downloads/wk
Reviews
Write oneNobody has reviewed Publishready yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Publishready tools (16, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
analyze_against_targetsCheck 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.
analyze_against_templateCheck text against a built-in template. Use this before revising. After revision, call compare_text_versions with the same template_id to verify alignment.
analyze_textReturn 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.
audit_ai_sounding_prosewrite actionRun 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.
build_reference_profileGenerate a Fingerprint Profile from one or more high-quality reference texts.
compare_profilesCompare two writing profiles, explicit target profiles, or templates.
compare_text_versionsCompare 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.
compare_to_referenceCompare current text against a specific Fingerprint Profile.
find_hotspotsLocate 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.
find_reference_driftDetect if current writing samples are drifting away from a reference profile.
get_templateReturn the full details of a specific template including its numeric targets.
interpret_targetsExplain the human implications, likely audience, and tradeoffs of a set of numeric targets.
list_templatesReturn a list of available writing templates with their metadata.
plan_revision_workflowGenerate 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.
suggest_revision_leversRank 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.
summarize_writing_profileGenerate a fingerprint profile from a text sample.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan47 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 152 days ago8/15
- Maintainer identityregistry namespace matches repository owner6/10
How Publishready compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 78/100
- higher than 57% of 48,255 servers
- Tools
- 16
- the typical server has 7
- Tools that change things
- 6%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 2
- more than 75% of 28,688 servers
- Downloads a week
- 47
- more than 39% of 12,191 servers with a package
What its tools let an agent do: 15 read · 1 change
Install Publishready in Claude Code, Cursor or VS Code
Runs npx -y @veldica/publishready-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add publishready -- npx -y @veldica/publishready-mcp
What the publisher says
From the Publishready repository's README, as published. We do not edit it. Read it on GitHub
PublishReady: Professional Writing Control
PublishReady is a deterministic writing analysis system designed to turn AI drafts into publish-ready writing. It serves as the final QA pass for AI-generated prose, providing local-first metrics, target compliance, and specific revision levers without sending text to remote services.
The PublishReady Packages
This project is structured as a professional, layered monorepo containing specialized packages:
Core Packages
- @veldica/publishready-mcp: The Model Context Protocol (MCP) server implementation (publishready-mcp).
- @veldica/publishready-cli: The command-line tool for local analysis (publishready).
- @veldica/publishready-core: The central orchestration engine.
- @veldica/publishready-schemas: Unified Zod schemas and explicit interfaces.
Underlying Libraries
- @veldica/prose-analyzer: Deterministic style signals (variety, density, repetition, narrative texture).
- @veldica/readability: Consolidated library of all major readability formulas.
- @veldica/prose-tokenizer: Standalone markdown-aware prose tokenization.
- @veldica/prose-linter: Target checks, revision levers, content integrity, and deterministic AI-sounding prose markers.
Installation
MCP Server (Recommended)
Add the server to your MCP client configuration:
{
"mcpServers": {
"publishready": {
"command": "npx",
"args": ["-y", "@veldica/publishready-mcp"]
}
}
}Command Line
npx @veldica/publishready-cli analyze sample.txtHosted MCP
For Smithery, VPS, or gateway deployments, run the server with Streamable HTTP:
npx @veldica/publishready-mcp --transport=http --port=3000The MCP endpoint is /mcp; the health endpoint is /health.
Key Features
- Template, Target, and Reference Modes: Compare writing against built-in templates, explicit numeric targets, reference text, or reusable reference profiles.
- Deterministic Metrics: Structural counts, sentence and paragraph distributions, lexical signals, scannability, fiction proxies, and readability formulas.
- Specific Revision Levers: Ranked, evidence-based suggestions such as shortenlongsentences, replacedifficultwords, and reduceabstractwording.
- AI-Sounding Prose Audit: Deterministic marker inventory for formulaic, generic, or over-polished prose, including exact matches and tracked phrase counts.
- Fiction & Non-Fiction Support: Narrative metrics for dialogue, sensory density, abstract wording, and scene pacing.
- Explainable Interpretation: Target and metric interpretation that explains audience, use cases, style implications, and tradeoffs.
- Local-First & Private: Stdio-first, deterministic, no external API calls, and no LLM wrappers.
MCP Tool Surface
The MCP server exposes 16 specialized tools for analysis and control, including auditaisounding_prose for deterministic AI-marker analysis. For a full list and documentation, see the MCP README.
Deterministic Philosophy
This package explicitly avoids perplexity and other model-dependent scores. We believe writing control should be:
- Explainable: You should know exactly why a score changed.
- Reproducible: The same text should always yield the same metrics.
- Practical: A metric is only useful if it tells you what to change.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Publishready: common questions
- Is Publishready MCP server safe?
- Mostly: it is graded B (78/100). Read the Publishready safety report
- How do I install Publishready?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Publishready need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Publishready maintained?
- The last commit was 190 days ago (2026-04-28). The latest release is v1.0.5.
- How does Publishready compare with other MCP servers?
- safety score 78/100 (higher than 57% of 48,255 servers); tools 16 (the typical server has 7); tools that change things 6% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.