Should my agent depend on the MCP server ai.agentplaybooks/agentplaybooks?

Verdict: allow — rich-slow-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

AgentPlaybooks

ai.agentplaybooks/agentplaybooks

Manage portable AI agent playbooks, Agent Skills, MCP configurations, personas, and memory.

— the operator's own registry description reported

Publisher ai.agentplaybooks · first seen 2026-08-12 · endpoint https://agentplaybooks.ai/api/mcp/manage

allow

verdict

rich-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-slow-solo — safe to depend on

Cluster rich-slow-solo · distinctiveness 0.557 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency559 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools47

vs populationhigh

capabilities1

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_0e98e27a7eb75f9e4b359aa3 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

archive_memories call_connected_tool consolidate_memories create_mcp_server create_persona create_playbook create_run create_skill create_task_graph delete_mcp_server delete_memory delete_persona delete_playbook delete_run delete_secret delete_skill get_canvas_toc get_memory_context get_memory_tree get_playbook get_skill list_canvas list_mcp_servers list_playbooks list_runs list_secrets list_skill_versions list_skills lock_canvas_section patch_canvas_section promote_memory read_canvas read_memory rollback_skill rotate_secret search_memory store_secret unlock_canvas_section update_mcp_server update_persona update_playbook update_run update_skill update_task_status use_secret write_canvas write_memory

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	47/47	✓
has a description	47/47	✓
description is substantive	47/47	✓
parameters are typed	47/47	✓
parameters are described	47/47	✓

47 of 47 tools graded · 47 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

1.0.0

server version agentplaybooks-management

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:57:33Z	ok_tools	200	559	2025-06-18
2026-08-12T05:32:52Z	ok_tools	200	161	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/ai.agentplaybooks/agentplaybooks.svg)](https://robinsaige.com/s/ai.agentplaybooks/agentplaybooks)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview