Home / MCP registry index / io.usefulapi/atera
Atera MCP by usefulapi
io.usefulapi/atera in the official MCP registry.
Endpoint https://atera.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Check devices, alerts and tickets in Atera, and open tickets, comment or resolve alerts.
We read its 20 tools on 2026-10-22. 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
atera_get_account atera_list_customers atera_get_customer atera_list_agents atera_get_agent atera_find_agents_by_machine atera_get_agent_patches atera_list_alerts atera_list_tickets atera_get_ticket atera_list_ticket_comments atera_list_ticket_work_hours atera_list_contacts atera_list_contracts atera_list_kb_articles atera_create_ticket atera_update_ticket atera_add_ticket_comment atera_create_contact atera_resolve_alert
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-atera)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.