Home / MCP registry index / com.agentery/agentery
com.agentery/agentery
com.agentery/agentery in the official MCP registry.
Endpoint https://agentery.com/api/mcp.
The registry describes it as: Price benchmarks, alternatives & daily price history across 17,000+ AI agents and MCP servers.
We read its 23 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
research_capability search_providers find_market compare_providers get_price_index price_benchmark request_research get_research stop_research_updates refine_results get_group_fair_price get_price_index_history market_gaps suggest_alternatives demand_signals report_outcome get_provider_profile get_provider market_report create_custom_benchmark get_custom_benchmark update_custom_benchmark delete_custom_benchmark
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-agentery-agentery)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.