agent-readiness-mcp
MCP server exposing agent-readiness to coding agents (Claude Desktop,
Cursor, custom hosts).
Five tools, all backed by the agent-readiness
engine wheel:
detect_workspace(path)— classify the path assingle_repo/monorepo/multi_repo_workspace. Returns the engine'sdetect_v1envelope (repos list withAGENTS.mdenrichment, drift warnings, signals fired). Call this first when the user-supplied path is ambiguous; the result tells you whether to chainscan_repoorscan_workspace. Added in0.2.0/agent-readiness 2.5.0.scan_workspace(path, select=None)— fan out scans across every detected repo in a multi-repo workspace (or a named subset viaselect). Returns one envelope with ascannedlist of reports and askippedlist of not-selected / failed / unmatched names. Also works on single-repo paths (single-entryscanned) so the caller can branch on classification alone.scan_repo(path)— scan a repo and return the readiness report (overall score, per-pillar scores, every check, and thetop_actionpin). On a multi-repo path the tool returns a structuredmulti_repo_workspaceerror payload pointing atscan_workspace/detect_workspace, mirroringagent-readiness scan's CLI contract.list_friction(path)— return every WARN/ERROR finding paired with its paste-readyfix_prompt, sorted byscore_impactdescending. Drops findings without a prompt (the contract is "paste-ready only").apply_top_action(path, run_verify=True)— apply the structured fix the engine pinned and run its verify command. Returns anApplyResultso the caller can decide whether to commit. Requiresagent-readiness >= 2.4.0(the engine release that ships theapply_actionmodule).
Install
pip install agent-readiness-mcp
Run
Start the server on stdio (the format Claude Desktop and Cursor speak):
agent-readiness-mcp --transport stdio
For a Claude Desktop install, add to ~/.claude/claude_desktop_config.json:
{
"mcpServers": {
"agent-readiness": {
"command": "agent-readiness-mcp",
"args": ["--transport", "stdio"]
}
}
}
License
MIT.
Metadata
Release files for agent-readiness-mcp 0.8.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| agent_readiness_mcp-0.8.0.tar.gz | 33.3 kB | With provenance | Details for agent_readiness_mcp-0.8.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agent_readiness_mcp-0.8.0-py3-none-any.whl | Python 3 | none | any | Details for agent_readiness_mcp-0.8.0-py3-none-any.whl |
Total release size: 53.7 kB
Release files / agent_readiness_mcp-0.8.0.tar.gz
| Download URL | agent_readiness_mcp-0.8.0.tar.gz |
|---|---|
| Size | 33.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4b500cddb712e75e1f4a360429808706e1d490c90794dc2cb0a05166fd9e9084
|
|
BLAKE2b-256 checksum How to use checksums |
4208d79c1c4df831baece88c635c02648df37626d366f38158c8dec58fccf305
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 28, 2026.
Transparency logRelease files / agent_readiness_mcp-0.8.0-py3-none-any.whl
| Download URL | agent_readiness_mcp-0.8.0-py3-none-any.whl |
|---|---|
| Size | 20.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d852abc3dddc77bcd096299bf26fa4c343afd395d6a436be04d4eaaf4a46b10e
|
|
BLAKE2b-256 checksum How to use checksums |
6b8284b613b0224c348fc5b5099702ed373999bf7ee0eaf346e5074935a0c656
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 28, 2026.
Transparency logSecurity for agent-readiness-mcp 0.8.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for agent_readiness_mcp-0.8.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 28, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.