Home / MCP registry index / io.usefulapi/gorelo

Gorelo MCP by usefulapi

io.usefulapi/gorelo in the official MCP registry. Endpoint https://gorelo.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Read tickets, devices, alerts and invoices; create tickets, add comments, log time in Gorelo.

We read its 31 tools on 2026-10-31. 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.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http gorelo https://gorelo.usefulapi.io/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "gorelo": {
      "url": "https://gorelo.usefulapi.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"gorelo","type":"http","url":"https://gorelo.usefulapi.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

gorelo_list_clients gorelo_get_client gorelo_list_client_locations gorelo_list_contacts gorelo_get_contact gorelo_list_tickets gorelo_get_ticket gorelo_list_ticket_comments gorelo_list_ticket_statuses gorelo_list_ticket_types gorelo_list_ticket_priorities gorelo_list_agent_assets gorelo_get_agent_asset gorelo_get_agent_hardware gorelo_list_agent_pending_updates gorelo_list_custom_assets gorelo_list_alerts gorelo_get_alert gorelo_list_projects gorelo_list_project_tasks gorelo_list_time_entries gorelo_list_invoices gorelo_get_invoice gorelo_list_contracts gorelo_list_users gorelo_list_groups gorelo_create_ticket gorelo_update_ticket gorelo_add_ticket_comment gorelo_update_alert_status gorelo_log_time_entry

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 9914b0f411a2743f. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-gorelo/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-gorelo)

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.