MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Code & DevOps

Desk365 MCP by usefulapi

Read Desk365 tickets, conversations, contacts, companies, time entries and knowledge articles.

Checks passed
14 / 22

0 failed · 8 not measured

Median response
64 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
16

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Outdated check

Last connection measurement is over 24 hours old. Current availability is unknown.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
402

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 64 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name desk365-mcp.

  • Pass
    Lists tools

    tools/list returned 16 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 64 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 64 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    61 of 72 parameters have a description (85%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-11-10T23:34:30.469068Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Start using Desk365 MCP by usefulapi

Connect to this server

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 desk365-mcp-by-usefulapi https://desk365.usefulapi.io/mcp

Capabilities

Tools 16

desk365_add_ticket_reply

WRITE: preview a public agent reply, optionally appending signature_html. With confirm:true and the approved preview_hash, SENDS AN EMAIL to the ticket contact and explicit CC/BCC recipients. Supply an explicit sender and agent. Reuse operation_id for status/retries; uncertain attempts are never replayed. Confirmed sends require hosted persistent operation storage.

Discovered
desk365_get_company

One company by exact name: description, phone, address, SLA, domains, departments, custom fields. GET /v3/companies/details.

Discovered
desk365_get_contact

One contact by primary email (or, if the primary is not known, a secondary email): name, title, phones, company, departments, custom fields. GET /v3/contacts/details.

Discovered
desk365_get_kb_article

A live knowledge base article by its exact title: HTML and plain-text content, category, folder, author, views, likes and status (0 unpublished, 1 published). GET /v3/kb/article/details.

Discovered
desk365_get_ticket

Everything on one ticket by its number: subject, description, status, priority, source, assignee, group, category, contact, company, SLA, due date, response/resolution durations (minutes), custom fields, watchers. GET /v3/tickets/details.

Discovered
desk365_get_ticket_conversations

The conversation on a ticket: customer replies, agent replies, private and public notes and forwarded messages, each with sender, recipients, HTML and plain-text body, attachment details and time. The original description is not included (it is on desk365_get_ticket). GET /v3/tickets/conversations.

Discovered
desk365_get_time_entry

One time entry by id. GET /v3/time_entries/details.

Discovered
desk365_list_companies

List companies (customer organisations), 30 per call, sorted by name. GET /v3/companies.

Discovered
desk365_list_contacts

List contacts (customers/requesters), 30 per call, sorted by name by default, optionally only those of one company. GET /v3/contacts.

Discovered
desk365_list_kb_articles

The titles of all live knowledge base articles. Open one with desk365_get_kb_article. GET /v3/kb/article/.

Discovered
desk365_list_survey_ratings

Customer satisfaction survey ratings (type 1 CSAT, 2 five-star, 3 NPS), oldest reply first, 30 per call. GET /v3/surveys/ratings.

Discovered
desk365_list_tickets

List helpdesk tickets, newest first by default, with subject, status, priority (1 Low, 5 Medium, 10 High, 20 Urgent), source, assignee, group, category, contact, company, SLA and dates. Filter by status, priority, type, group, assignee, category, contact, company or source. Use "--" in a list to match unassigned/empty. Descriptions are left out unless include_description is set. GET /v3/tickets.

Discovered
desk365_list_time_entries

List logged time entries (ticket, agent, minutes, billable, note), filtered by ticket, agent, company, billable flag, running timers or date ranges. GET /v3/time_entries.

Discovered
desk365_reply_operation_status

Read the stored state and reply ID of a previous send operation. Does not send or retry any email. If uncertain, reconcile the original attempt in Desk365; do not create a new operation ID to blindly retry it.

Discovered
desk365_search_tickets

Full-text search over tickets, most relevant first. Searches subject and ticket number by default; widen it with search_in (description, replies and notes, attachment names, custom fields, contacts and companies, archived tickets). Double quotes around a phrase match it exactly; *text* matches inside words. GET /v3/tickets/search.

Discovered
desk365_set_ticket_status

WRITE: change only a ticket's status by its ticket number, including closing or resolving it. Supply the exact status name configured in the helpdesk (for example Resolved or Closed); no priority, assignee or other fields are changed. Desk365 may run status automations and send notifications. Pass confirm=true after the user approved the ticket and destination status. PUT /v3/tickets/update?ticket_number=... with only {status}.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected64 ms16