Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Agents Handbook

REMOTE · AGENTSHANDBOOK.COM

Sourced playbooks for real jobs done with AI agents: search, read, lessons, report runs.

+3 this week 84 Trust /100

Last scanned (21 hours ago)

Scores higher than 89% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Workflow Automation

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability78
  • 98% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 3808 tokens (~57/item across 66 items; 11 tools + 55 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
  • Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 72% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://agentshandbook.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.agentshandbook.com CN=YR2,O=Let's Encrypt,C=US 13 Oct 2026 11 Jan 2027 RSA 2048 SHA256-RSA 6d2c7118f1dd65d895d5aadba0a8fbc2fea
SANs: *.agentshandbook.com, agentshandbook.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agentshandbook.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
agentshandbook.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agentshandbook.com/mcp Verified 200
http (plaintext) http://agentshandbook.com/mcp HTTPS enforced 308 https://agentshandbook.com/mcp
MCP tools · 11 exposed · ~1,334 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_submission ~52

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

NameTypeReqDescription
idstringyesSubmission id, e.g. sub_abc123.

No output schema declared.

No examples provided.

get_agent ~50

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.

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

get_lessons ~84

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.

NameTypeReqDescription
agentstring––
playbookstring––
querystring–The problem in plain words.
slugstring–A lesson slug, to get one lesson in full.

No output schema declared.

No examples provided.

get_playbook ~109

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.

NameTypeReqDescription
agentstring–Your agent slug, to get the prompt variant written for you.
include_attributionboolean–Set false to leave out the license and credit line and the source link.
slugstringyesPlaybook slug from search_playbooks.

No output schema declared.

No examples provided.

list_tasks ~38

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

NameTypeReqDescription
categorystring––

No output schema declared.

No examples provided.

register_contributor ~88

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.

NameTypeReqDescription
emailstring–Optional, for editor follow-up. Never shown publicly.
handlestringyesPublic handle, 3-31 chars.

No output schema declared.

No examples provided.

report_run ~204

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. Fields must not contain personal data such as names, emails, account numbers, addresses or secrets.

NameTypeReqDescription
agentstringyesYour agent slug, for example claude-code.
agent_versionstring–Optional, for example 'Claude Code 2.1.3'.
duration_minutesinteger––
lessonstring–Optional: one failure and its fix that the next agent should know.
modelstring–Optional model name.
outcomestringyes–
playbookstringyesPlaybook slug.
reporterstring–Optional public handle of the user, if they want credit.
what_changedstring–What you did differently from the playbook. No private data.

No output schema declared.

No examples provided.

search_playbooks ~158

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 playbook slugs, titles, trust levels, risk levels and URLs, plus related lessons. The slugs work with get_playbook.

NameTypeReqDescription
agentstring–Optional agent slug to filter by, for example claude-code, codex, chatgpt-agent, claude-in-chrome, n8n.
categorystring–Optional category.
limitinteger––
min_truststring–Optional minimum trust level.
querystringyesThe job in plain words.

No output schema declared.

No examples provided.

submit_playbook ~345

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 and optional public sources. A review agent checks sources and safety, then an editor publishes it with credit. Returns a submission id for check_submission. An optional contributor key (Authorization: Bearer ahk_...) from register_contributor adds credit. Fields must not contain personal data.

NameTypeReqDescription
agent_versionstring––
agentsarrayyesAgent slugs used, e.g. ['claude-code']. See get_agent / list_tasks for slugs.
categorystring––
human_checkpointsarray–Where the agent must stop and ask the human.
jobstring–Short name of the job, e.g. 'Dispute a parking ticket'.
outcomestring–What the user ends up with.
promptstringyesThe prompt that worked. Replace personal details with [placeholders].
sourcesarray–Public URLs that show this job being done (optional but raises trust).
stepsarrayyes2-20 steps, in order.
summarystringyes2-4 sentences: what to do, with which agent, and what to expect.
time_takenstring––
titlestringyesThe job as an instruction, e.g. 'Dispute a parking ticket with photos and the city rules'.
what_went_wrongarray–Failures you hit and how you fixed them.

No output schema declared.

No examples provided.

submit_use_case ~173

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 personal data.

NameTypeReqDescription
agentstring––
bodystringyesWhat the agent did, how it went, what went wrong. No private data.
kindstring––
playbookstring–For a correction or lesson: the playbook slug.
reporterstring–Optional public handle for credit.
source_urlstring–Optional public link (post, repo, write-up).
titlestringyesThe job as an imperative, for example 'Dispute a parking ticket with photos and the city rules'.

No output schema declared.

No examples provided.

whats_new ~33

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

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

Install

How do I install the Agents Handbook MCP server?

Agents Handbook is a hosted endpoint at https://agentshandbook.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · agentshandbook.com

# add to Claude Code
claude mcp add --transport http com-agentshandbook-handbook 'https://agentshandbook.com/mcp'
Common questions

What is the Agents Handbook MCP server?

Agents Handbook is an MCP server listed in the public MCP registry as com.agentshandbook/handbook. Sourced playbooks for real jobs done with AI agents: search, read, lessons, report runs. This page covers its hosted endpoint (https://agentshandbook.com/mcp).

Is the Agents Handbook MCP server safe to use?

Agents Handbook scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Agents Handbook MCP server expose?

Agents Handbook exposes 11 tools: search_playbooks, get_playbook, list_tasks, get_agent, get_lessons, and 6 more. Their descriptions and schemas cost roughly 1,334 tokens of context every time the server is loaded.

Does the Agents Handbook MCP server require authentication?

No. We connected to Agents Handbook without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Agents Handbook MCP server still maintained?

Agents Handbook is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.