Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Payments & trading
Read tickets, devices, alerts and invoices; create tickets, add comments, log time in Gorelo.
0 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Outdated check
Last connection measurement is over 24 hours old. Current availability is unknown.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 4 | 0 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using Gorelo MCP by usefulapi
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http gorelo-mcp-by-usefulapi https://gorelo.usefulapi.io/mcpCapabilities
WRITE: add a comment to a ticket's main thread. A 'public' comment is a reply the client sees and may be emailed to them; a 'private' comment is an internal note. Do not retry after an unclear error: that can post twice. API: POST /v1/tickets/{ticketId}/comments.
DiscoveredWRITE: create a service ticket. Needs status_id, group_id and type_id (use gorelo_list_ticket_statuses, gorelo_list_groups, gorelo_list_ticket_types). Set send_created_email true only if the contact must get a 'ticket created' email. API: POST /v1/tickets.
DiscoveredGet one managed device by id (guid). API: GET /v1/assets/agents/{agentAssetId}.
DiscoveredGet a managed device's processors, memory and disks. API: GET /v1/assets/agents/{agentAssetId}/hardware.
DiscoveredGet one alert by id (guid). API: GET /v1/alerts/{alertId}.
DiscoveredGet one client by id with its details. API: GET /v1/clients/{clientId}.
DiscoveredGet one contact by id. API: GET /v1/contacts/{contactId}.
DiscoveredGet one invoice with its line items and attachments. API: GET /v1/invoices/{invoiceId}.
DiscoveredGet one ticket by id (uuid). API: GET /v1/tickets/{ticketId}.
DiscoveredList agent (RMM managed device) assets with status, OS and client. API: GET /v1/assets/agents.
DiscoveredList the Windows updates pending on a managed device, from its last scan (no new scan starts). API: GET /v1/assets/agents/{agentAssetId}/patches/available.
DiscoveredList alerts (uptime, script, external, ...) newest first. API: GET /v1/alerts.
DiscoveredList the locations (sites) of one client. API: GET /v1/clients/{clientId}/locations.
DiscoveredList the MSP's clients (customers). Good first call to find a client id. API: GET /v1/clients.
DiscoveredList client contacts (end users). API: GET /v1/contacts.
DiscoveredList billing contracts with their service lines. API: GET /v1/contracts.
DiscoveredList custom (non-agent) assets such as printers, switches and licences. API: GET /v1/assets/custom.
DiscoveredList technician groups (ids are needed to create a ticket). API: GET /v1/organization/groups.
DiscoveredList invoices with status, totals and client. API: GET /v1/invoices.
DiscoveredList the tasks of one project. API: GET /v1/projects/{projectId}/tasks.
DiscoveredList projects with status, client and lead. API: GET /v1/projects.
DiscoveredList the comments (public replies, private notes) on a ticket. API: GET /v1/tickets/{ticketId}/comments.
DiscoveredList the ticket priorities. API: GET /v1/tickets/priorities.
DiscoveredList the ticket statuses (id and name) used to filter or update tickets. API: GET /v1/tickets/statuses.
DiscoveredList the ticket types. API: GET /v1/tickets/types.
DiscoveredList service tickets, newest activity first, with status, priority, client, assignees and SLA. Use the list_ticket_statuses/types/priorities tools to learn the ids for filters. API: GET /v1/tickets.
DiscoveredList logged time across tickets and tasks. API: GET /v1/time-entries.
DiscoveredList users (technicians) with role and status; use their ids as assignee ids. API: GET /v1/organization/users.
DiscoveredWRITE: log work time against a ticket (or a project task). Give any two of started_on, ended_on and actual_hours (the API derives the third). Billing role, work type and billable status default from the ticket. Do not retry after an unclear error: that can log twice. API: POST /v1/time-entries.
DiscoveredWRITE: dismiss an alert, restore it to New, or link it to an open ticket (status 'ticketed' needs ticket_id). The change applies to the alert's whole stack, as in the app. API: PATCH /v1/alerts/{alertId}.
DiscoveredWRITE: change fields of a ticket (status, priority, assignee, title, tags). Only the fields you send change. Each change notifies and logs as in the app. Changing the client clears the ticket's contact and assets. API: PATCH /v1/tickets/{ticketId}.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 173 ms | 31 |