Home / MCP registry index / ai.mekler/agent-discovery
Mekler AI
ai.mekler/agent-discovery in the official MCP registry.
Endpoint https://api.mekler.ai/mcp.
The registry describes it as: Research, inference, data/web/email tools, and x402 conformance, service catalog and grade feeds.
We read its 24 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
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
search_services get_service scan_origin get_scan_status get_scan_report list_conformance_checks search_listings retrieve_listing export_listings list_grade_changes start_ownership_proof confirm_ownership_proof update_listing_preferences get_trial_offer get_trial_access rotate_trial referral_accept_terms referral_acknowledge referral_notices referral_receipts referral_register referral_rotate referral_status referral_program
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-mekler-agent-discovery)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.