MCP.Market

Agent Readiness MCP server

by alipajand·io.github.alipajand/agent-readiness·v0.1.2·1 stars

Deterministic, read-only audits of repo readiness for AI coding agents and of agent context files.

A85/100grade A
What users say
No reviews yet
Be the first
Safety scan
A85/100

not scanned yet

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed Agent Readiness yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Agent Readiness tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Agent Readiness compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 73% of 4,460 AI and agents servers
GitHub stars
1
more than 50% of 2,711 AI and agents servers

Release history: 2 versions in the registry since 2026-10-13, latest 2026-10-13, typically several a day.

Install Agent Readiness in Claude Code, Cursor or VS Code

Runs npx -y @alipajand/agent-readiness-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add agent-readiness -- npx -y @alipajand/agent-readiness-mcp
Add to Cursor

What the publisher says

From the Agent Readiness repository's README, as published. We do not edit it. Read it on GitHub

agent-readiness-action

What it is

A GitHub Action that checks how ready a repository is for AI coding agents (Claude Code, Cursor, Codex, Copilot, and similar). It bundles two deterministic engines:

repository from 0 to 100: instruction files, architecture notes, scripts, tests, safety boundaries, and more. Lockfiles, version pins, test runners, linters, and formatters are scored on the files of each detected ecosystem (Node.js, Python, Go, Rust). It prints a category breakdown in the log and job summary.

  • agent-readiness-kit scores the

context-audit: 'true', checks the instruction files themselves: placeholders, risky directives, contradictions, stale commands, pasted secrets, hidden Unicode, and risky Claude Code and MCP configuration such as bypassPermissions, hooks that run remote scripts, or third-party API endpoints.

  • agent-context-doctor, with

It can fail the build below a score, block pull requests that lower the score, write a Markdown report, and post a summary comment on pull requests.

Both engines are bundled into the action at pinned commits, so nothing is downloaded or executed from a package registry at run time. There are no external API calls (other than the optional PR comment), no telemetry, and no LLM calls.

Why use it

setup docs) before it slows down day-to-day agent work.

  • Catch missing or low-quality agent context (instruction files, architecture notes,

let them run commands without asking.

  • Catch instruction files and agent settings that steer agents toward unsafe changes or

any drop from the base branch.

  • Track the readiness score over time and gate pull requests on a minimum score or on

review, not a replacement for it.

  • Give reviewers a concise, deterministic summary on each PR — a complement to human

Quick start

# .github/workflows/agent-readiness.yml
name: Agent Readiness Audit

on:
  pull_request:
  push:
    branches: [main]

permissions:
  contents: read

jobs:
  audit:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
      - uses: alipajand/agent-readiness-action@v1

Examples

Basic audit

name: Agent Readiness Audit

on:
  pull_request:
  push:
    branches: [main]

permissions:
  contents: read

jobs:
  audit:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
      - uses: alipajand/agent-readiness-action@v1

Fail below a minimum score

- uses: alipajand/agent-readiness-action@v1
  with:
    min-score: '70'
    fail-on-threshold: 'true'

Comment on pull requests

permissions:
  contents: read
  pull-requests: write
  issues: write

steps:
  - uses: actions/checkout@v7
  - uses: alipajand/agent-readiness-action@v1
    with:
      comment-on-pr: 'true'
      min-score: '70'
      github-token: ${{ github.token }}

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Agent Readiness: common questions

Is Agent Readiness MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the Agent Readiness safety report
How do I install Agent Readiness?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Agent Readiness need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Agent Readiness maintained?
The last commit was 22 days ago (2026-10-13). The latest release is v0.1.2.
What can I use instead of Agent Readiness?
Servers from other publishers that do the same job: Serena MCP: the IDE for your agent MCP server, Figma Context MCP server and Basic Memory MCP server.
How does Agent Readiness compare with other AI and agents MCP servers?
safety score 85/100 (higher than 73% of 4,460 AI and agents servers); github stars 1 (more than 50% of 2,711 AI and agents servers). Full comparison.

Alternatives to Agent Readiness

Same job from other publishers: the closest match first, then the best rated.

  • Serena MCP: the IDE for your agent
    A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
    C
  • Figma Context
    Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
    B
  • Basic Memory
    Local-first knowledge management with bi-directional LLM sync via Markdown files.
    B
  • SuperCompress
    Compress coding-agent context ~64%. Hosted Neural Keep MCP for Cursor/Claude/Codex.
    B
  • Orcareplay
    Read, replay and fork recorded coding-agent runs.
    A