Gorelo MCP by usefulapi
REMOTE · GORELO.USEFULAPI.IO
Read tickets, devices, alerts and invoices; create tickets, add comments, log time in Gorelo.
Available components
Last scanned (9 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 −46
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://gorelo.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gorelo.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gorelo.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/gorelo/ |
| http (plaintext) | http://gorelo.usefulapi.io/mcp | Inconclusive | 302 | http://gorelo.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
gorelo_add_ticket_comment Add a ticket comment ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Comment body as HTML. Send < and > in text as < and >. |
| ticket_id | string | yes | Ticket id (uuid). |
| visibility | string | yes | public = visible to the client; private = internal note. |
No output schema declared.
No examples provided.
gorelo_create_ticket Create a ticket ~247
WRITE: 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_asset_ids | array | – | Managed device ids (guid) to link. |
| client_id | integer | – | – |
| contact_id | integer | – | – |
| description | string | – | Ticket body as HTML. Plain text is wrapped in a paragraph. Send < and > as < and >. |
| group_id | integer | yes | Technician group id. |
| lead_assignee_id | integer | – | Technician id. |
| location_id | integer | – | Needs client_id. |
| priority_id | integer | – | – |
| send_created_email | boolean | – | Email the contact that the ticket was created (default false). |
| source_id | integer | – | – |
| status_id | integer | yes | Initial status id. |
| tag_ids | array | – | – |
| title | string | yes | Ticket title. |
| type_id | integer | yes | Ticket type id. |
No output schema declared.
No examples provided.
gorelo_get_agent_asset Get a managed device ~55
Get one managed device by id (guid). API: GET /v1/assets/agents/{agentAssetId}.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_asset_id | string | yes | Agent asset id (guid, from gorelo_list_agent_assets). |
No output schema declared.
No examples provided.
gorelo_get_agent_hardware Get device hardware ~53
Get a managed device's processors, memory and disks. API: GET /v1/assets/agents/{agentAssetId}/hardware.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_asset_id | string | yes | Agent asset id (guid). |
No output schema declared.
No examples provided.
gorelo_get_alert Get an alert ~49
Get one alert by id (guid). API: GET /v1/alerts/{alertId}.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_id | string | yes | Alert id (guid, from gorelo_list_alerts). |
No output schema declared.
No examples provided.
gorelo_get_client Get a client ~49
Get one client by id with its details. API: GET /v1/clients/{clientId}.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | Client id (integer, from gorelo_list_clients). |
No output schema declared.
No examples provided.
gorelo_get_contact Get a contact ~46
Get one contact by id. API: GET /v1/contacts/{contactId}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | Contact id (integer, from gorelo_list_contacts). |
No output schema declared.
No examples provided.
gorelo_get_invoice Get an invoice ~49
Get one invoice with its line items and attachments. API: GET /v1/invoices/{invoiceId}.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | Invoice id (from gorelo_list_invoices). |
No output schema declared.
No examples provided.
gorelo_get_ticket Get a ticket ~49
Get one ticket by id (uuid). API: GET /v1/tickets/{ticketId}.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | string | yes | Ticket id (uuid, from gorelo_list_tickets). |
No output schema declared.
No examples provided.
gorelo_list_agent_assets List managed devices ~190
List agent (RMM managed device) assets with status, OS and client. API: GET /v1/assets/agents.
| Name | Type | Req | Description |
|---|---|---|---|
| client_ids | string | – | Comma-separated client ids, for example "12,15". |
| cursor | string | – | Cursor from DataContext.Pagination.NextCursor of the previous page. Omit for the first page. |
| page_size | integer | – | Items per page, 1-200 (default 50). |
| query | string | – | Keyword matched against device name, display name and description. |
| status_ids | string | – | Comma-separated device status (2 Online, 3 Offline, 4 Pending Delete; the API also accepts 1 and 6, see the API docs) ids, for example "12,15". |
| updated_since | string | – | ISO-8601 timestamp, keep devices updated at or after it. |
No output schema declared.
No examples provided.
gorelo_list_agent_pending_updates List device pending updates ~70
List the Windows updates pending on a managed device, from its last scan (no new scan starts). API: GET /v1/assets/agents/{agentAssetId}/patches/available.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_asset_id | string | yes | Agent asset id (guid) of a Windows agent. |
No output schema declared.
No examples provided.
gorelo_list_alerts List alerts ~248
List alerts (uptime, script, external, ...) newest first. API: GET /v1/alerts.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_asset_ids | string | – | Comma-separated agent asset (guid) ids, for example "12,15". |
| client_ids | string | – | Comma-separated client ids, for example "12,15". |
| created_before | string | – | ISO-8601 timestamp, keep alerts raised before it. |
| created_since | string | – | ISO-8601 timestamp, keep alerts raised at or after it. |
| cursor | string | – | Cursor from DataContext.Pagination.NextCursor of the previous page. Omit for the first page. |
| page_size | integer | – | Items per page, 1-200 (default 50). |
| sort_order | string | – | – |
| status_ids | string | – | Comma-separated alert status (1 New, 2 Dismissed, 3 Ticketed) ids, for example "12,15". |
| type_ids | string | – | Comma-separated alert type (1 Uptime, 2 API, 3 Script, 4 External, ...) ids, for example "12,15". |
No output schema declared.
No examples provided.
gorelo_list_client_locations List client locations ~47
List the locations (sites) of one client. API: GET /v1/clients/{clientId}/locations.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | Client id (integer). |
No output schema declared.
No examples provided.
gorelo_list_clients List clients ~180
List the MSP's clients (customers). Good first call to find a client id. API: GET /v1/clients.
| Name | Type | Req | Description |
|---|---|---|---|
| created_since | string | – | ISO-8601 timestamp, keep clients created at or after it. |
| cursor | string | – | Cursor from DataContext.Pagination.NextCursor of the previous page. Omit for the first page. |
| group_ids | string | – | Comma-separated client group ids, for example "12,15". |
| page_size | integer | – | Items per page, 1-200 (default 50). |
| query | string | – | Keyword to match against the client name. |
| status_ids | string | – | Comma-separated client status ids, for example "12,15". |
| updated_since | string | – | ISO-8601 timestamp, keep clients updated at or after it. |
No output schema declared.
No examples provided.
gorelo_list_contacts List contacts ~183
List client contacts (end users). API: GET /v1/contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| client_ids | string | – | Comma-separated client ids, for example "12,15". |
| cursor | string | – | Cursor from DataContext.Pagination.NextCursor of the previous page. Omit for the first page. |
| location_ids | string | – | Comma-separated location ids, for example "12,15". |
| page_size | integer | – | Items per page, 1-200 (default 50). |
| query | string | – | Keyword matched against email, first name and last name. |
| status_ids | string | – | Comma-separated contact status (1 Active, 3 Temporary, 4 Archived) ids, for example "12,15". |
| updated_since | string | – | ISO-8601 timestamp, keep contacts updated at or after it. |
No output schema declared.
No examples provided.
gorelo_list_contracts List contracts ~127
List billing contracts with their service lines. API: GET /v1/contracts.
| Name | Type | Req | Description |
|---|---|---|---|
| client_ids | string | – | Comma-separated client ids, for example "12,15". |
| cursor | string | – | Cursor from DataContext.Pagination.NextCursor of the previous page. Omit for the first page. |
| page_size | integer | – | Items per page, 1-200 (default 50). |
| query | string | – | Keyword matched against the contract name. |
| status_ids | string | – | Comma-separated contract status ids, for example "12,15". |
No output schema declared.
No examples provided.
gorelo_list_custom_assets List custom assets ~135
List custom (non-agent) assets such as printers, switches and licences. API: GET /v1/assets/custom.
| Name | Type | Req | Description |
|---|---|---|---|
| client_ids | string | – | Comma-separated client ids, for example "12,15". |
| cursor | string | – | Cursor from DataContext.Pagination.NextCursor of the previous page. Omit for the first page. |
| page_size | integer | – | Items per page, 1-200 (default 50). |
| query | string | – | Keyword matched against the asset name. |
| updated_since | string | – | ISO-8601 timestamp, keep assets updated at or after it. |
No output schema declared.
No examples provided.
gorelo_list_groups List technician groups ~32
List technician groups (ids are needed to create a ticket). API: GET /v1/organization/groups.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gorelo_list_invoices List invoices ~252
List invoices with status, totals and client. API: GET /v1/invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| client_ids | string | – | Comma-separated client ids, for example "12,15". |
| contract_ids | string | – | Comma-separated contract ids, for example "12,15". |
| cursor | string | – | Cursor from DataContext.Pagination.NextCursor of the previous page. Omit for the first page. |
| due_date_before | string | – | Date (yyyy-mm-dd): invoices due before it (find overdue invoices). |
| invoice_date_before | string | – | Date (yyyy-mm-dd): invoices dated before it. |
| invoice_date_since | string | – | Date (yyyy-mm-dd): invoices dated at or after it. |
| page_size | integer | – | Items per page, 1-200 (default 50). |
| query | string | – | Free text matched against invoice number, reference and name. |
| sort_by | string | – | – |
| sort_order | string | – | – |
| status_ids | string | – | Comma-separated invoice status (1 Draft, 2 Submitted, 3 Paid, 4 Void, 5 Approved) ids, for example "12,15". |
No output schema declared.
No examples provided.
gorelo_list_project_tasks List project tasks ~190
List the tasks of one project. API: GET /v1/projects/{projectId}/tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_ids | string | – | Comma-separated technician ids, for example "12,15". |
| cursor | string | – | Cursor from DataContext.Pagination.NextCursor of the previous page. Omit for the first page. |
| incomplete_only | boolean | – | When true, drop tasks in the Done status. |
| page_size | integer | – | Items per page, 1-200 (default 50). |
| project_id | string | yes | Project id (guid, from gorelo_list_projects). |
| sort_by | string | – | – |
| sort_order | string | – | – |
| status_ids | string | – | Comma-separated task status (1 Not started, 2 Working on it, 3 On hold, 4 Done) ids, for example "12,15". |
No output schema declared.
No examples provided.
gorelo_list_projects List projects ~174
List projects with status, client and lead. API: GET /v1/projects.
| Name | Type | Req | Description |
|---|---|---|---|
| client_ids | string | – | Comma-separated client ids, for example "12,15". |
| cursor | string | – | Cursor from DataContext.Pagination.NextCursor of the previous page. Omit for the first page. |
| page_size | integer | – | Items per page, 1-200 (default 50). |
| query | string | – | Keyword matched against the project name. |
| sort_by | string | – | Sort field, for example updatedOn or createdOn. |
| sort_order | string | – | – |
| status_ids | string | – | Comma-separated project status ids, for example "12,15". |
| updated_since | string | – | ISO-8601 timestamp, keep projects updated at or after it. |
No output schema declared.
No examples provided.
gorelo_list_ticket_comments List ticket comments ~166
List the comments (public replies, private notes) on a ticket. API: GET /v1/tickets/{ticketId}/comments.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | – | Filter to one conversation id (from the ticket's conversations). |
| conversation_type | string | – | Conversation kinds to include: 1 Public, 2 Private, 3 Side Conversation, 4 Approval. Comma-separated, or a single value together with conversation_id. |
| cursor | string | – | Cursor from DataContext.Pagination.NextCursor of the previous page. Omit for the first page. |
| page_size | integer | – | Items per page, 1-200 (default 50). |
| sort_order | string | – | – |
| ticket_id | string | yes | Ticket id (uuid). |
No output schema declared.
No examples provided.
gorelo_list_ticket_priorities List ticket priorities ~29
List the ticket priorities. API: GET /v1/tickets/priorities.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gorelo_list_ticket_statuses List ticket statuses ~39
List the ticket statuses (id and name) used to filter or update tickets. API: GET /v1/tickets/statuses.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gorelo_list_ticket_types List ticket types ~26
List the ticket types. API: GET /v1/tickets/types.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gorelo_list_tickets List tickets ~415
List 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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_ids | string | – | Comma-separated client ids, for example "12,15". |
| closed_since | string | – | ISO-8601 timestamp, keep tickets closed at or after it. |
| contact_ids | string | – | Comma-separated contact ids, for example "12,15". |
| created_before | string | – | ISO-8601 timestamp, keep tickets created before it. |
| created_since | string | – | ISO-8601 timestamp, keep tickets created at or after it. |
| cursor | string | – | Cursor from DataContext.Pagination.NextCursor of the previous page. Omit for the first page. |
| device_ids | string | – | Comma-separated agent asset (guid) ids, for example "12,15". |
| group_ids | string | – | Comma-separated technician group ids, for example "12,15". |
| lead_assignee_ids | string | – | Comma-separated technician (lead assignee) ids, for example "12,15". |
| page_size | integer | – | Items per page, 1-200 (default 50). |
| priority_ids | string | – | Comma-separated priority ids, for example "12,15". |
| query | string | – | Keyword matched against the ticket title, number and display number. |
| sort_by | string | – | – |
| sort_order | string | – | – |
| status_ids | string | – | Comma-separated ticket status ids, for example "12,15". |
| tag_ids | string | – | Comma-separated tag ids, for example "12,15". |
| type_ids | string | – | Comma-separated ticket type ids, for example "12,15". |
| updated_since | string | – | ISO-8601 timestamp, keep tickets updated at or after it. |
No output schema declared.
No examples provided.
gorelo_list_time_entries List time entries ~225
List logged time across tickets and tasks. API: GET /v1/time-entries.
| Name | Type | Req | Description |
|---|---|---|---|
| client_ids | string | – | Comma-separated client ids, for example "12,15". |
| cursor | string | – | Cursor from DataContext.Pagination.NextCursor of the previous page. Omit for the first page. |
| invoice_ids | string | – | Comma-separated invoice ids, for example "12,15". |
| page_size | integer | – | Items per page, 1-200 (default 50). |
| started_before | string | – | ISO-8601 timestamp, keep entries whose work started before it. |
| started_since | string | – | ISO-8601 timestamp, keep entries whose work started at or after it. |
| task_ids | string | – | Comma-separated task (guid) ids, for example "12,15". |
| ticket_ids | string | – | Comma-separated ticket (uuid) ids, for example "12,15". |
| user_ids | string | – | Comma-separated user ids, for example "12,15". |
No output schema declared.
No examples provided.
gorelo_list_users List technicians ~142
List users (technicians) with role and status; use their ids as assignee ids. API: GET /v1/organization/users.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor from DataContext.Pagination.NextCursor of the previous page. Omit for the first page. |
| group_ids | string | – | Comma-separated technician group ids, for example "12,15". |
| page_size | integer | – | Items per page, 1-200 (default 50). |
| query | string | – | Keyword matched against the user name or email. |
| status_ids | string | – | Comma-separated user status ids, for example "12,15". |
No output schema declared.
No examples provided.
gorelo_log_time_entry Log time on a ticket ~216
WRITE: 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.
| Name | Type | Req | Description |
|---|---|---|---|
| actual_hours | number | – | Hours worked, decimal. |
| billable_status_id | integer | – | 1 Billable, 2 No charge, 3 Non-billable. |
| comment | string | – | Note that describes the work. |
| ended_on | string | – | ISO-8601 UTC end of the work. |
| started_on | string | – | ISO-8601 UTC start of the work. |
| task_id | string | – | Project task id (guid). Send this or ticket_id. |
| ticket_id | string | – | Ticket id (uuid). Send this or task_id. |
| user_id | integer | – | Technician id the time belongs to. |
No output schema declared.
No examples provided.
gorelo_update_alert_status Update an alert status ~105
WRITE: 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}.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_id | string | yes | Alert id (guid). |
| status | string | yes | – |
| ticket_id | string | – | Open ticket id (uuid). Required when status is ticketed. |
No output schema declared.
No examples provided.
gorelo_update_ticket Update a ticket ~166
WRITE: 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}.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | – | – |
| contact_id | integer | – | – |
| lead_assignee_id | integer | – | Technician id. Send 0 to unassign. |
| priority_id | integer | – | – |
| status_id | integer | – | – |
| tag_ids | array | – | Replaces the whole tag list; [] clears it. |
| ticket_id | string | yes | Ticket id (uuid). |
| title | string | – | – |
| type_id | integer | – | – |
No output schema declared.
No examples provided.
How do I install the Gorelo MCP by usefulapi server?
Gorelo MCP by usefulapi is a hosted endpoint at https://gorelo.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · gorelo.usefulapi.io
claude mcp add --transport http io-usefulapi-gorelo 'https://gorelo.usefulapi.io/mcp'
What is the Gorelo MCP by usefulapi server?
Gorelo MCP by usefulapi is listed in the public MCP registry as io.usefulapi/gorelo. Read tickets, devices, alerts and invoices; create tickets, add comments, log time in Gorelo. This page covers its hosted endpoint (https://gorelo.usefulapi.io/mcp).
Is the Gorelo MCP by usefulapi server safe to use?
Gorelo MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Gorelo MCP by usefulapi server expose?
Gorelo MCP by usefulapi exposes 31 tools: gorelo_list_clients, gorelo_get_client, gorelo_list_client_locations, gorelo_list_contacts, gorelo_get_contact, and 26 more. Their descriptions and schemas cost roughly 4,088 tokens of context every time the server is loaded.
Does the Gorelo MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Gorelo MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Gorelo MCP by usefulapi server still maintained?
Gorelo MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.