io.usefulapi/accelo
REMOTE · ACCELO.USEFULAPI.IO · SCANNED OCT 4
Manage Accelo companies, contacts, jobs, tasks, tickets and time.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3513 tokens (~152/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/accelo MCP server?
io.usefulapi/accelo is a hosted endpoint at https://accelo.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 · accelo.usefulapi.io
claude mcp add --transport http io-usefulapi-accelo 'https://accelo.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-accelo": {
"url": "https://accelo.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-accelo": {
"type": "http",
"url": "https://accelo.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-accelo] url = "https://accelo.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-accelo": {
"type": "remote",
"url": "https://accelo.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-accelo --url 'https://accelo.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-accelo:
url: "https://accelo.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-accelo": {
"Transport": "http",
"Url": "https://accelo.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-accelo -t streamable-http -u 'https://accelo.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-accelo": {
"type": "http",
"url": "https://accelo.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Sept 26 71
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 4 Oct 2026 · Probed https://accelo.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 accelo.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://accelo.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://accelo.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://accelo.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://accelo.usefulapi.io/mcp |
| Authorisation server | https://accelo.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://accelo.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://accelo.usefulapi.io/mcp | HTTPS enforced | 301 | https://accelo.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 →
accelo_request Raw read request ~120
Power-user escape hatch: GET any Accelo API path not wrapped by a dedicated tool. READ-ONLY — only GET is allowed. Pass the FULL API path after the host, starting with a slash, INCLUDING any query string, e.g. "/api/v0/companies?_limit=1&_filters=status(1)" or "/api/v0/tasks/123". Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Full API path after the host, starting with "/", e.g. "/api/v0/invoices?_limit=5". |
No output schema declared.
No examples provided.
create_activity Create an activity (log a note/email/call) ~301
MUTATES Accelo data: logs an activity (a note, email, call, or meeting) against an object. This is the highest-value safe write — e.g. add a note/comment to a job or company. against_type + against_id say what it is logged against (required). Accelo API: POST /api/v0/activities (form-encoded). Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| against_id | string | yes | The id of the object this activity is logged against (required). |
| against_type | string | yes | The object type this activity is logged against, e.g. "company", "job", "issue", "prospect", "contact" (required). |
| body | string | – | The activity body/message text (the note content). |
| fields | object | – | Additional documented Accelo fields to send in the write body (merged with the typed fields above). |
| medium | string | – | Communication medium, e.g. "note", "email", "call", "meeting". Defaults to a note on the Accelo side. |
| owner_id | string | – | The owner id (e.g. the staff id). |
| owner_type | string | – | The owner object type, e.g. "staff" (who logged/owns the activity). |
| subject | string | yes | Activity subject/summary line (required). |
| visibility | string | – | Visibility, e.g. "all", "internal", "private". |
No output schema declared.
No examples provided.
create_company Create a company ~163
MUTATES Accelo data: creates a new company (client organization). Accelo API: POST /api/v0/companies (form-encoded). Returns { meta, response } with the created company. (Accelo has no separate delete tool here; to UPDATE, POST to /api/v0/companies/{id}.)
| Name | Type | Req | Description |
|---|---|---|---|
| comments | string | – | Free-text comments/notes on the company. |
| fields | object | – | Additional documented Accelo fields to send in the write body (merged with the typed fields above). |
| name | string | yes | Company name (required). |
| phone | string | – | Primary phone number. |
| status_id | string | – | Company status id (from your deployment's company statuses). |
| website | string | – | Company website URL. |
No output schema declared.
No examples provided.
create_contact Create a contact ~165
MUTATES Accelo data: creates a new contact (a person). Accelo API: POST /api/v0/contacts (form-encoded). NOTE: a contact's company affiliation is set separately via an affiliation (POST /api/v0/contacts/{id}/affiliations), not on creation. Returns { meta, response } with the created contact.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Primary email address. | |
| fields | object | – | Additional documented Accelo fields to send in the write body (merged with the typed fields above). |
| firstname | string | yes | Contact's first name (required). |
| mobile | string | – | Mobile phone number. |
| phone | string | – | Landline/other phone number. |
| surname | string | – | Contact's surname/last name. |
No output schema declared.
No examples provided.
create_task Create a task ~205
MUTATES Accelo data: creates a new task. Accelo tasks are always logged AGAINST an object (a job, company, issue, etc.), so against_type + against_id are required. Accelo API: POST /api/v0/tasks (form-encoded). Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| against_id | string | yes | The id of the object this task is logged against (required). |
| against_type | string | yes | The object type this task is logged against, e.g. "job", "company", "issue", "prospect" (required). |
| date_due | integer | – | Due date as a Unix timestamp (seconds). |
| date_started | integer | – | Start date as a Unix timestamp (seconds). |
| description | string | – | Longer task description/details. |
| fields | object | – | Additional documented Accelo fields to send in the write body (merged with the typed fields above). |
| title | string | yes | Task title/name (required). |
No output schema declared.
No examples provided.
get_activity Get an activity ~80
Fetch a single activity (note/email/call/meeting). Accelo API: GET /api/v0/activities/{id}. Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | _fields: comma-separated extra fields to include in each object, or "_ALL" for every available field. |
| id | string | yes | The activities object id. |
No output schema declared.
No examples provided.
get_company Get a company ~76
Fetch a single company (client organization). Accelo API: GET /api/v0/companies/{id}. Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | _fields: comma-separated extra fields to include in each object, or "_ALL" for every available field. |
| id | string | yes | The companies object id. |
No output schema declared.
No examples provided.
get_contact Get a contact ~76
Fetch a single contact (a person). Accelo API: GET /api/v0/contacts/{id}. Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | _fields: comma-separated extra fields to include in each object, or "_ALL" for every available field. |
| id | string | yes | The contacts object id. |
No output schema declared.
No examples provided.
get_invoice Get an invoice ~73
Fetch a single invoice. Accelo API: GET /api/v0/invoices/{id}. Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | _fields: comma-separated extra fields to include in each object, or "_ALL" for every available field. |
| id | string | yes | The invoices object id. |
No output schema declared.
No examples provided.
get_issue Get an issue (ticket) ~76
Fetch a single issue (support/service ticket). Accelo API: GET /api/v0/issues/{id}. Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | _fields: comma-separated extra fields to include in each object, or "_ALL" for every available field. |
| id | string | yes | The issues object id. |
No output schema declared.
No examples provided.
get_job Get a job (project) ~74
Fetch a single job (project). Accelo API: GET /api/v0/jobs/{id}. Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | _fields: comma-separated extra fields to include in each object, or "_ALL" for every available field. |
| id | string | yes | The jobs object id. |
No output schema declared.
No examples provided.
get_prospect Get a prospect (sale) ~78
Fetch a single prospect (sales opportunity). Accelo API: GET /api/v0/prospects/{id}. Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | _fields: comma-separated extra fields to include in each object, or "_ALL" for every available field. |
| id | string | yes | The prospects object id. |
No output schema declared.
No examples provided.
get_staff Get a staff member ~74
Fetch a single staff member. Accelo API: GET /api/v0/staff/{id}. Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | _fields: comma-separated extra fields to include in each object, or "_ALL" for every available field. |
| id | string | yes | The staff object id. |
No output schema declared.
No examples provided.
get_task Get a task ~72
Fetch a single task. Accelo API: GET /api/v0/tasks/{id}. Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | _fields: comma-separated extra fields to include in each object, or "_ALL" for every available field. |
| id | string | yes | The tasks object id. |
No output schema declared.
No examples provided.
list_activities List activities ~215
List activities — notes, emails, calls, and meetings logged against objects. Accelo API: GET /api/v0/activities. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | _fields: comma-separated extra fields to include in each object, or "_ALL" for every available field. |
| filters | string | – | _filters: Accelo filter string, function-like and comma-separated. E.g. status(1), date_created_after(1704067200), order_by_desc(date_created), search(acme). Suffix _not for negation; combine with _O… |
| limit | integer | – | _limit: max objects to return (1–100, default 50). |
| page | integer | – | _page: 0-indexed page number (default 0). |
| search | string | – | _search: free-text search across the object's searchable fields. |
No output schema declared.
No examples provided.
list_companies List companies ~206
List companies (client organizations). Accelo API: GET /api/v0/companies. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | _fields: comma-separated extra fields to include in each object, or "_ALL" for every available field. |
| filters | string | – | _filters: Accelo filter string, function-like and comma-separated. E.g. status(1), date_created_after(1704067200), order_by_desc(date_created), search(acme). Suffix _not for negation; combine with _O… |
| limit | integer | – | _limit: max objects to return (1–100, default 50). |
| page | integer | – | _page: 0-indexed page number (default 0). |
| search | string | – | _search: free-text search across the object's searchable fields. |
No output schema declared.
No examples provided.
list_contacts List contacts ~206
List contacts (people at companies). Accelo API: GET /api/v0/contacts. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | _fields: comma-separated extra fields to include in each object, or "_ALL" for every available field. |
| filters | string | – | _filters: Accelo filter string, function-like and comma-separated. E.g. status(1), date_created_after(1704067200), order_by_desc(date_created), search(acme). Suffix _not for negation; combine with _O… |
| limit | integer | – | _limit: max objects to return (1–100, default 50). |
| page | integer | – | _page: 0-indexed page number (default 0). |
| search | string | – | _search: free-text search across the object's searchable fields. |
No output schema declared.
No examples provided.
list_invoices List invoices ~203
List invoices. Accelo API: GET /api/v0/invoices. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | _fields: comma-separated extra fields to include in each object, or "_ALL" for every available field. |
| filters | string | – | _filters: Accelo filter string, function-like and comma-separated. E.g. status(1), date_created_after(1704067200), order_by_desc(date_created), search(acme). Suffix _not for negation; combine with _O… |
| limit | integer | – | _limit: max objects to return (1–100, default 50). |
| page | integer | – | _page: 0-indexed page number (default 0). |
| search | string | – | _search: free-text search across the object's searchable fields. |
No output schema declared.
No examples provided.
list_issues List issues (tickets) ~206
List issues — support/service tickets. Accelo API: GET /api/v0/issues. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | _fields: comma-separated extra fields to include in each object, or "_ALL" for every available field. |
| filters | string | – | _filters: Accelo filter string, function-like and comma-separated. E.g. status(1), date_created_after(1704067200), order_by_desc(date_created), search(acme). Suffix _not for negation; combine with _O… |
| limit | integer | – | _limit: max objects to return (1–100, default 50). |
| page | integer | – | _page: 0-indexed page number (default 0). |
| search | string | – | _search: free-text search across the object's searchable fields. |
No output schema declared.
No examples provided.
list_jobs List jobs (projects) ~209
List jobs — Accelo "jobs" are projects. Accelo API: GET /api/v0/jobs. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | _fields: comma-separated extra fields to include in each object, or "_ALL" for every available field. |
| filters | string | – | _filters: Accelo filter string, function-like and comma-separated. E.g. status(1), date_created_after(1704067200), order_by_desc(date_created), search(acme). Suffix _not for negation; combine with _O… |
| limit | integer | – | _limit: max objects to return (1–100, default 50). |
| page | integer | – | _page: 0-indexed page number (default 0). |
| search | string | – | _search: free-text search across the object's searchable fields. |
No output schema declared.
No examples provided.
list_prospects List prospects (sales) ~211
List prospects — sales opportunities in the pipeline. Accelo API: GET /api/v0/prospects. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | _fields: comma-separated extra fields to include in each object, or "_ALL" for every available field. |
| filters | string | – | _filters: Accelo filter string, function-like and comma-separated. E.g. status(1), date_created_after(1704067200), order_by_desc(date_created), search(acme). Suffix _not for negation; combine with _O… |
| limit | integer | – | _limit: max objects to return (1–100, default 50). |
| page | integer | – | _page: 0-indexed page number (default 0). |
| search | string | – | _search: free-text search across the object's searchable fields. |
No output schema declared.
No examples provided.
list_staff List staff ~209
List staff (Accelo users in your deployment). Accelo API: GET /api/v0/staff. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | _fields: comma-separated extra fields to include in each object, or "_ALL" for every available field. |
| filters | string | – | _filters: Accelo filter string, function-like and comma-separated. E.g. status(1), date_created_after(1704067200), order_by_desc(date_created), search(acme). Suffix _not for negation; combine with _O… |
| limit | integer | – | _limit: max objects to return (1–100, default 50). |
| page | integer | – | _page: 0-indexed page number (default 0). |
| search | string | – | _search: free-text search across the object's searchable fields. |
No output schema declared.
No examples provided.
list_tasks List tasks ~215
List tasks (units of work logged against an object such as a job or company). Accelo API: GET /api/v0/tasks. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | _fields: comma-separated extra fields to include in each object, or "_ALL" for every available field. |
| filters | string | – | _filters: Accelo filter string, function-like and comma-separated. E.g. status(1), date_created_after(1704067200), order_by_desc(date_created), search(acme). Suffix _not for negation; combine with _O… |
| limit | integer | – | _limit: max objects to return (1–100, default 50). |
| page | integer | – | _page: 0-indexed page number (default 0). |
| search | string | – | _search: free-text search across the object's searchable fields. |
No output schema declared.
No examples provided.
What is the io.usefulapi/accelo MCP server?
io.usefulapi/accelo is an MCP server listed in the public MCP registry as io.usefulapi/accelo. Manage Accelo companies, contacts, jobs, tasks, tickets and time. This page covers its hosted endpoint (https://accelo.usefulapi.io/mcp).
Is the io.usefulapi/accelo MCP server safe to use?
io.usefulapi/accelo scores 78 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 io.usefulapi/accelo MCP server expose?
io.usefulapi/accelo exposes 23 tools: list_companies, get_company, list_contacts, get_contact, list_jobs, and 18 more. Their descriptions and schemas cost roughly 3,513 tokens of context every time the server is loaded.
Does the io.usefulapi/accelo MCP server require authentication?
Yes. io.usefulapi/accelo asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/accelo MCP server still maintained?
io.usefulapi/accelo is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.