Skip to content

Accelo MCP by usefulapi

io.usefulapi/accelousefulapi.iostreamable-httpv1.41.4Scanned

Manage Accelo companies, contacts, jobs, tasks, tickets and time.

23 tools: 4 can delete or cancel things, 1 change things and 18 only read.

Tools: 4 delete, 0 irreversible, 1 write, 18 read.
  • Reads private data · 4
  • Reads text others write · 4
  • Can send data out · 0
  • 1 finding

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Accelo MCP by usefulapi can do

The Accelo MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 23 tools. It can delete or cancel things (4 tools: accelo_create_company, accelo_create_contact, accelo_create_task and accelo_create_activity) and create or change data (1 tool: accelo_request). 18 tools only read.

4 tools read private data (accelo_list_contacts, accelo_get_contact, accelo_list_activities and 1 more); 4 tools bring in text other people can write (accelo_list_activities, accelo_get_activity, accelo_list_issues and 1 more).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its tools changed once since Anlyon Radar first saw them.

Last scanned Oct 25, 2026, version 1.41.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

23 tools

Deletes or cancels 4Claude Code: deny
  • accelo_create_activityMUTATES Accelo data: logs an activity (a note, email, call, or meeting) against an object.No findings

    Why it is in this group

    • The name "accelo_create_activity" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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 }.

    Annotations the server declares

    • title: Create an activity (log a note/email/call)
    • destructiveHint: true
  • accelo_create_companyMUTATES Accelo data: creates a new company (client organization).No findings

    Why it is in this group

    • The name "accelo_create_company" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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}.)

    Annotations the server declares

    • title: Create a company
    • destructiveHint: true
  • accelo_create_contactMUTATES Accelo data: creates a new contact (a person).No findings

    Why it is in this group

    • The name "accelo_create_contact" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a contact
    • destructiveHint: true
  • accelo_create_taskMUTATES Accelo data: creates a new task.No findings

    Why it is in this group

    • The name "accelo_create_task" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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 }.

    Annotations the server declares

    • title: Create a task
    • destructiveHint: true
Changes things 1Claude Code: ask
  • accelo_requestPower-user escape hatch: GET any Accelo API path not wrapped by a dedicated tool.1 finding

    Why it is in this group

    • The name "accelo_request" says "request": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "accelo_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "accelo_request" says "request": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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 }.

    Annotations the server declares

    • title: Raw read request
    • readOnlyHint: true
Only reads 18Show 18 read-only tools
  • accelo_get_activityFetch a single activity (note/email/call/meeting).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "accelo_get_activity" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "note": it reads notes.
    • untrusted-inputThe description's first sentence says "fetch" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Fetch a single activity (note/email/call/meeting). Accelo API: GET /api/v0/activities/{id}. Returns { meta, response }.

    Annotations the server declares

    • title: Get an activity
    • readOnlyHint: true
  • accelo_get_companyFetch a single company (client organization).No findings

    Why it is in this group

    • The name "accelo_get_company" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single company (client organization). Accelo API: GET /api/v0/companies/{id}. Returns { meta, response }.

    Annotations the server declares

    • title: Get a company
    • readOnlyHint: true
  • accelo_get_contactFetch a single contact (a person).Reads private dataNo findings

    Why it is in this group

    • The name "accelo_get_contact" says "get": a word for reading.

    What it can reach

    • private-dataThe name "accelo_get_contact" says "get" and "contact": it reads contacts.
    • private-dataThe description's first sentence says "fetch" and "contact": it reads contacts.
    Description, as the server wrote it
    Fetch a single contact (a person). Accelo API: GET /api/v0/contacts/{id}. Returns { meta, response }.

    Annotations the server declares

    • title: Get a contact
    • readOnlyHint: true
  • accelo_get_invoiceFetch a single invoice.No findings

    Why it is in this group

    • The name "accelo_get_invoice" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single invoice. Accelo API: GET /api/v0/invoices/{id}. Returns { meta, response }.

    Annotations the server declares

    • title: Get an invoice
    • readOnlyHint: true
  • accelo_get_issueFetch a single issue (support/service ticket).Reads text others writeNo findings

    Why it is in this group

    • The name "accelo_get_issue" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "accelo_get_issue" says "get" and "issue": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "fetch" and "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    Fetch a single issue (support/service ticket). Accelo API: GET /api/v0/issues/{id}. Returns { meta, response }.

    Annotations the server declares

    • title: Get an issue (ticket)
    • readOnlyHint: true
  • accelo_get_jobFetch a single job (project).No findings

    Why it is in this group

    • The name "accelo_get_job" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single job (project). Accelo API: GET /api/v0/jobs/{id}. Returns { meta, response }.

    Annotations the server declares

    • title: Get a job (project)
    • readOnlyHint: true
  • accelo_get_prospectFetch a single prospect (sales opportunity).No findings

    Why it is in this group

    • The name "accelo_get_prospect" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single prospect (sales opportunity). Accelo API: GET /api/v0/prospects/{id}. Returns { meta, response }.

    Annotations the server declares

    • title: Get a prospect (sale)
    • readOnlyHint: true
  • accelo_get_staffFetch a single staff member.No findings

    Why it is in this group

    • The name "accelo_get_staff" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single staff member. Accelo API: GET /api/v0/staff/{id}. Returns { meta, response }.

    Annotations the server declares

    • title: Get a staff member
    • readOnlyHint: true
  • accelo_get_taskFetch a single task.No findings

    Why it is in this group

    • The name "accelo_get_task" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single task. Accelo API: GET /api/v0/tasks/{id}. Returns { meta, response }.

    Annotations the server declares

    • title: Get a task
    • readOnlyHint: true
  • accelo_list_activitiesList activities — notes, emails, calls, and meetings logged against objects.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "accelo_list_activities" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "note": it reads notes.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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 }.

    Annotations the server declares

    • title: List activities
    • readOnlyHint: true
  • accelo_list_companiesList companies (client organizations).No findings

    Why it is in this group

    • The name "accelo_list_companies" says "list": a word for reading.
    Description, as the server wrote it
    List companies (client organizations). Accelo API: GET /api/v0/companies. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.

    Annotations the server declares

    • title: List companies
    • readOnlyHint: true
  • accelo_list_contactsList contacts (people at companies).Reads private dataNo findings

    Why it is in this group

    • The name "accelo_list_contacts" says "list": a word for reading.

    What it can reach

    • private-dataThe name "accelo_list_contacts" says "list" and "contact": it reads contacts.
    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    List contacts (people at companies). Accelo API: GET /api/v0/contacts. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.

    Annotations the server declares

    • title: List contacts
    • readOnlyHint: true
  • accelo_list_invoicesList invoices.No findings

    Why it is in this group

    • The name "accelo_list_invoices" says "list": a word for reading.
    Description, as the server wrote it
    List invoices. Accelo API: GET /api/v0/invoices. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.

    Annotations the server declares

    • title: List invoices
    • readOnlyHint: true
  • accelo_list_issuesList issues — support/service tickets.Reads text others writeNo findings

    Why it is in this group

    • The name "accelo_list_issues" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe name "accelo_list_issues" says "list" and "issue": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "list" and "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    List issues — support/service tickets. Accelo API: GET /api/v0/issues. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.

    Annotations the server declares

    • title: List issues (tickets)
    • readOnlyHint: true
  • accelo_list_jobsList jobs — Accelo "jobs" are projects.No findings

    Why it is in this group

    • The name "accelo_list_jobs" says "list": a word for reading.
    Description, as the server wrote it
    List jobs — Accelo "jobs" are projects. Accelo API: GET /api/v0/jobs. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.

    Annotations the server declares

    • title: List jobs (projects)
    • readOnlyHint: true
  • accelo_list_prospectsList prospects — sales opportunities in the pipeline.No findings

    Why it is in this group

    • The name "accelo_list_prospects" says "list": a word for reading.
    Description, as the server wrote it
    List prospects — sales opportunities in the pipeline. Accelo API: GET /api/v0/prospects. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.

    Annotations the server declares

    • title: List prospects (sales)
    • readOnlyHint: true
  • accelo_list_staffList staff (Accelo users in your deployment).No findings

    Why it is in this group

    • The name "accelo_list_staff" says "list": a word for reading.
    Description, as the server wrote it
    List staff (Accelo users in your deployment). Accelo API: GET /api/v0/staff. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.

    Annotations the server declares

    • title: List staff
    • readOnlyHint: true
  • accelo_list_tasksList tasks (units of work logged against an object such as a job or company).No findings

    Why it is in this group

    • The name "accelo_list_tasks" says "list": a word for reading.
    Description, as the server wrote it
    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 }.

    Annotations the server declares

    • title: List tasks
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data4
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:31 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://accelo.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://accelo.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "accelo_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "accelo_request" says "request": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://accelo.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://accelo.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed
  2. Tools22 added, 22 removed.+22 added−22 removedView diff

Install

Pinned to version 1.41.4. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__accelo__accelo_list_companies",
      "mcp__accelo__accelo_get_company",
      "mcp__accelo__accelo_list_contacts",
      "mcp__accelo__accelo_get_contact",
      "mcp__accelo__accelo_list_jobs",
      "mcp__accelo__accelo_get_job",
      "mcp__accelo__accelo_list_tasks",
      "mcp__accelo__accelo_get_task",
      "mcp__accelo__accelo_list_activities",
      "mcp__accelo__accelo_get_activity",
      "mcp__accelo__accelo_list_invoices",
      "mcp__accelo__accelo_get_invoice",
      "mcp__accelo__accelo_list_prospects",
      "mcp__accelo__accelo_get_prospect",
      "mcp__accelo__accelo_list_staff",
      "mcp__accelo__accelo_get_staff",
      "mcp__accelo__accelo_list_issues",
      "mcp__accelo__accelo_get_issue"
    ],
    "ask": [
      "mcp__accelo__accelo_request"
    ],
    "deny": [
      "mcp__accelo__accelo_create_company",
      "mcp__accelo__accelo_create_contact",
      "mcp__accelo__accelo_create_task",
      "mcp__accelo__accelo_create_activity"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as accelo. Review it before you use it.

Capability tags behind 6 rules
  • mcp__accelo__accelo_list_contacts private-data
  • mcp__accelo__accelo_get_contact private-data
  • mcp__accelo__accelo_list_activities private-data, untrusted-input
  • mcp__accelo__accelo_get_activity private-data, untrusted-input
  • mcp__accelo__accelo_list_issues untrusted-input
  • mcp__accelo__accelo_get_issue untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/accelo/verify?hash=a3cae3af46195b7dfe3b227f4605ba20b055a1c39a48bdd54175c318a7c45bcf" | jq -e '.changed == false'

Pinned hash a3cae3af4619, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/accelo/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/accelo
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/accelo.svg)](https://radar.anlyon.com/servers/io.usefulapi/accelo)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Accelo MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Accelo MCP by usefulapi safe?

No scan can promise that. What its definitions show: 23 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Accelo MCP by usefulapi delete data?

Yes. 4 tools can delete, cancel or revoke something: accelo_create_company, accelo_create_contact, accelo_create_task and accelo_create_activity.

Can the Accelo MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Accelo MCP by usefulapi have?

23 tools: 4 destructive, 1 write, 18 read. accelo_create_company, accelo_create_contact, accelo_create_task, accelo_create_activity, accelo_request, accelo_list_companies, accelo_get_company, accelo_list_contacts and 15 more.

Does the Accelo MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Accelo MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Accelo MCP by usefulapi changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 23, 2026. Every change is on this page and in its Atom feed.