Home / MCP registry index / com.agentalog/meta-agent-tools
Agentalog — Agent Auto Log
com.agentalog/meta-agent-tools in the official MCP registry.
Endpoint https://agentalog.com/mcp. Source: github.com/wrpbr/agentalog.
The registry describes it as: Agent Auto Log: MCP servers, skills and plugins, with an automatic log of every change.
We read its 36 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
search_bundles get_bundle index_stats feed_find feed_posts feed_post feed_search mcp_index_signals mcp_index_search check_tool listing_security listing_tools list_watched_tools watch_tool unwatch_tool claude_code_allowlist watch_alerts a2a_agent_search a2a_agent briefings_topics briefings_links api_index health create_guest list_listings list_mcp_servers get_listing get_listing_readme listing_history go_listing like_listing list_comments create_listing listing_status submit_okf contact
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-agentalog-meta-agent-tools)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.