Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Tools
inspect_json_contract
Check whether a JSON document contains specified top-level keys; this is a deterministic structural check, not a certification.
json string · required
required_keys array · required
A call is made on an account: it counts against an allowance and the publisher sees it, which is why this one asks who you are first.
3
tools declared
—
trust score
remote
via our gateway
—
p95 latency
What it does
Prepare AI agents and MCP tools for cleaner integrations with three practical checks. Inspect JSON structures for missing required keys, review agent endpoint URL formats, and analyze capability descriptions for clarity and completeness.
Get structured feedback that helps developers identify common readiness issues before publishing or integrating tools. URL checks examine formatting only; they do not test whether a live endpoint is reachable.
Quickstart
# 1 — buy it first ($9 a month): mcprush.com/checkout?server=creator-desk-agent-readiness-toolkit-mcp
# a key alone is not enough: the gateway refuses every call until it is bought
# 2 — sign in with a key of the account that bought it: npx mcprush@latest login
# the key is at mcprush.com/dashboard#access
# 3 — install
npx mcprush@latest add stephen-harvey/creator-desk-agent-readiness-toolkit-mcp
# 4 — ask your agent for something these tools do
# inspect_json_contract, inspect_agent_url, analyze_capability_description
Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither.
PublisherVerified · since 2026
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine — this server runs on the publisher’s own infrastructure behind our gateway, and what you install is the connection to it.
Claude Codenot declared — it may still work
Claude Code has its own MCP command, and the key rides on it as a header — the gateway refuses a call that carries none. Claude Code reads MCPRUSH_KEY each time it connects, so the key stays out of its config: export your key from Access in your shell profile (macOS, Linux), or run setx MCPRUSH_KEY <your key> and open a new terminal (Windows). Or let npx mcprush@latest add stephen-harvey/creator-desk-agent-readiness-toolkit-mcp write the entry with the key for you; --scope user makes it available in every project.
Buy it first — $9 a month. A key alone is not enough: until this account has bought it, the gateway refuses every call. Subscribe, then use a key of the account that bought it.
claude mcp add --transport http --scope user creator-desk-agent-readiness-toolkit-mcp https://mcprush.com/gw/creator-desk-agent-readiness-toolkit-mcp/mcp --header 'Authorization: Bearer ${MCPRUSH_KEY}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
This is a paid listing: the gateway answers only a key of an account whose subscription to it is active — how the login works. Until then add writes nothing: signed out, it names the price and the checkout link; signed in, it prints the checkout link, or why the subscription is held (ended, paused, an unpaid invoice) and the link that lifts it. The gateway refuses every call the same way, and most clients only show the server as failed.
What it writes
One config entry pointing at the gateway. The server itself runs on the publisher’s own infrastructure, so nothing from this listing executes on your machine.
What you approve
3 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Check whether a JSON document contains specified top-level keys; this is a deterministic structural check, not a certification.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| json | string | yes | — |
| required_keys | array | yes | — |
Parse an HTTP(S) agent endpoint URL and report its origin, path and transport suitability; no network request is performed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | — |
Analyze readability of a machine-tool description using transparent deterministic signals, not AI-generated claims.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | yes | — |
Starter
$9 / month
- 100 calls a month, included
- 5 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against the 100 calls a month on Starter
| Tool | Unit | Calls used | Out of the monthly allowance |
|---|---|---|---|
| inspect_json_contract | call | 1 | 1.0000% |
| inspect_agent_url | call | 1 | 1.0000% |
| analyze_capability_description | call | 1 | 1.0000% |
Failed calls, timeouts and anything the gateway rejects never count. When the allowance runs out the gateway returns an error naming the plan limit — nothing is billed beyond the subscription, ever.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is a hosted endpoint: the publisher runs it and we connect to it. The scanner reads packages and source, and neither exists to read here, so there is no grade — not a withheld one, an unmeasured one. What can be checked instead is on Installation: what it asks to reach and what it writes.
Release history
The gateway serves every install the publisher’s current release, so a release cannot be pinned or rolled back to here yet. The history below is for reading; the current release on file is 0.1.0.
0.1.0
12 Oct 2026
latest- The version this listing went live with, after review.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Creator Desk Agent Readiness Toolkit can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.