accelo

Status

Newest check: answered with tools, from the daily check, 2026-10-04, 310 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-052026-10-04

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in Documents and knowledge, ranked by days answering.

Tools

23 tools: 19 read-only, 0 change data, 4 high risk (delete, pay, send or run code).

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 5,462 tokens of tool definitions and a 310 ms handshake.

• high riskcreate_companyMUTATES 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}.)
• high riskcreate_contactMUTATES 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.
• high riskcreate_taskMUTATES 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 }.
• high riskcreate_activityMUTATES 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). Re...
• read-onlylist_companiesList companies (client organizations). Accelo API: GET /api/v0/companies. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.
• read-onlyget_companyFetch a single company (client organization). Accelo API: GET /api/v0/companies/{id}. Returns { meta, response }.
• read-onlylist_contactsList contacts (people at companies). Accelo API: GET /api/v0/contacts. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.
• read-onlyget_contactFetch a single contact (a person). Accelo API: GET /api/v0/contacts/{id}. Returns { meta, response }.
• read-onlylist_jobsList jobs - Accelo "jobs" are projects. Accelo API: GET /api/v0/jobs. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.
• read-onlyget_jobFetch a single job (project). Accelo API: GET /api/v0/jobs/{id}. Returns { meta, response }.
• read-onlylist_tasksList 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 }.
• read-onlyget_taskFetch a single task. Accelo API: GET /api/v0/tasks/{id}. Returns { meta, response }.
• read-onlylist_activitiesList activities - notes, emails, calls, and meetings logged against objects. Accelo API: GET /api/v0/activities. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.
• read-onlyget_activityFetch a single activity (note/email/call/meeting). Accelo API: GET /api/v0/activities/{id}. Returns { meta, response }.
• read-onlylist_invoicesList invoices. Accelo API: GET /api/v0/invoices. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.
• read-onlyget_invoiceFetch a single invoice. Accelo API: GET /api/v0/invoices/{id}. Returns { meta, response }.
• read-onlylist_prospectsList prospects - sales opportunities in the pipeline. Accelo API: GET /api/v0/prospects. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.
• read-onlyget_prospectFetch a single prospect (sales opportunity). Accelo API: GET /api/v0/prospects/{id}. Returns { meta, response }.
• read-onlylist_staffList staff (Accelo users in your deployment). Accelo API: GET /api/v0/staff. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.
• read-onlyget_staffFetch a single staff member. Accelo API: GET /api/v0/staff/{id}. Returns { meta, response }.
• read-onlylist_issuesList issues - support/service tickets. Accelo API: GET /api/v0/issues. Supports _page/_limit/_fields/_filters/_search. Returns { meta, response }.
• read-onlyget_issueFetch a single issue (support/service ticket). Accelo API: GET /api/v0/issues/{id}. Returns { meta, response }.
• read-onlyaccelo_requestPower-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,...

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

What agents looked for

This week agents asked 7Maps for documents and knowledge servers 1 time; this server was shown 0 times and picked 0 times.

Owners see the keywords, the servers picked instead, failure reasons and a comparison with similar servers in Owner Insights.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/accelo.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/accelo.usefulapi.io/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=accelo.usefulapi.io%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/accelo.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/accelo.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=accelo.usefulapi.io%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.