Should my agent depend on the MCP server com.agentery/agentery?

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

agentery

com.agentery/agentery

Search agents & MCP servers by capability, with daily-observed pricing, liveness and market data.

— the operator's own registry description reported

Publisher com.agentery · first seen 2026-08-12 · endpoint https://agentery.com/api/mcp

allow

verdict

stale-mid-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — stale-mid-slow-solo — safe to depend on

Cluster stale-mid-slow-solo · distinctiveness 0.531 (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

latency405 ms

vs populationslow

protocolbehind

authopen

Use — can it use it?

tools19

vs populationmid

capabilities3

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_8a68129d8b73e97429a9cdb2 · 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

compare_providers create_custom_benchmark delete_custom_benchmark demand_signals find_niche get_custom_benchmark get_price_index get_price_index_history get_provider get_provider_profile market_gaps niche_report price_benchmark rank_providers_for_workflow report_outcome research_capability search_providers suggest_alternatives update_custom_benchmark

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	19/19	✓
has a description	19/19	✓
description is substantive	19/19	✓
parameters are typed	19/19	✓
parameters are described	18/19	18/19

19 of 19 tools graded · 19 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-03-26

protocol version

—

session model

1.8.0

server version agentery

Capabilities: prompts resources 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 (2 events)

date	type	what changed
2026-08-14	outcome	ok_tools (was timeout)
2026-08-12	outcome	first probe: timeout

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:57:53Z	ok_tools	200	405	2025-03-26
2026-08-12T05:33:09Z	timeout		12245

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/com.agentery/agentery.svg)](https://robinsaige.com/s/com.agentery/agentery)

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