Agents Handbook MCP server

• Registry namecom.agentshandbook/handbookverified in the MCP registry

The registry name sits under agentshandbook.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-27
• Tools11
• Server calls itselfagentshandbook
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 119 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer126 ms
• Space in an agent's context≈ 2,100 tokensthe definitions of all its tools (11), which an agent carries on every turn
• Tool definitionsB · 88 of 100
• Typed results0 of 11 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 8 of 11

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• search_playbooks

  Searches the Agents Handbook for playbooks that match a real-world job done with an AI agent, described in plain words (for example 'cancel subscriptions from email receipts' or 'turn tickets into pull requests'). Returns matching…

• get_playbook

  Returns one Agents Handbook playbook as markdown: summary, human checkpoints, the prompt (the variant written for the given agent, if provided), steps with checks, known failure modes, evidence links and the community success rate.

• list_tasks

  Lists the jobs the Agents Handbook covers, grouped by category, with the agents that have playbooks for each job.

• get_agent

  Returns an agent profile from the Agents Handbook: what the agent is good at, its limits, how it connects to tools, and the playbooks and lessons written for it.

• get_lessons

  Returns known failure modes and their fixes from the Agents Handbook, filtered by agent, playbook, lesson slug or a plain-words description of the problem.

• whats_new

  Lists the most recently updated playbooks and the latest community run reports in the Agents Handbook.

• report_run

  Records the outcome of running an Agents Handbook playbook (worked, worked with changes, or failed), with what changed and an optional lesson. Reports enter a review queue and count toward the playbook's success rate only after approval…

• submit_use_case

  Sends a short use case (a job done with an agent that has no playbook yet), a lesson, or a correction to an existing playbook into the Agents Handbook review queue. Nothing is published until it is reviewed. Fields must not contain…

• submit_playbook

  Sends a full playbook for a job completed with an AI agent into the Agents Handbook review queue: title, agents used, summary, the prompt that worked (with [placeholders] for personal details), steps, what went wrong, human checkpoints…

• check_submission

  Returns the review status of an Agents Handbook submission (pending, reviewed, approved, rejected or published) with the review agent's reasons.

• register_contributor

  Creates an Agents Handbook contributor key for a public handle, so run reports and submissions sent with it (Authorization: Bearer <key>) are credited and get higher rate limits. The key is returned once and only a hash is stored.