Home / MCP registry index / io.usefulapi/accelo
Accelo MCP by usefulapi
io.usefulapi/accelo in the official MCP registry.
Endpoint https://accelo.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Manage Accelo companies, contacts, jobs, tasks, tickets and time.
We read its 23 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
list_companies get_company list_contacts get_contact list_jobs get_job list_tasks get_task list_activities get_activity list_invoices get_invoice list_prospects get_prospect list_staff get_staff list_issues get_issue accelo_request create_company create_contact create_task create_activity
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-accelo)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.