MCP server · registry snapshot 2026-10-24 · last tested 2026-10-24

io.usefulapi/clio

Read Clio matters, contacts, time, tasks, calendar and bills; add matters, time entries, notes. — the publisher's description

4 of 4 record checks metRead-only · tools listed 2026-10-24version 1.5.0JavaScriptstreamable HTTP23 tools

Summary

io.usefulapi/clio is a remote MCP server listed in the official MCP registry at version 1.5.0. On 2026-10-24 ProtocolProbe connected to it in read-only mode and read its inventory: 23 tools, 0 resources and 1 prompt.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not checked: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Repository: public
Tools: 23
Last tested: 2026-10-24

Add to your client

Observed fact

This server accepted a session without any credential and lists 8 tools whose name or declaration suggests they change data (clio_create_contact, clio_create_matter, clio_create_time_entry, clio_create_task, clio_update_task and 3 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-24.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-24

Mode

read-only (no tool calls)

Latest version

1.5.0, published 2026-10-24 (registry, as of the 2026-10-24 snapshot)

First listed version

2026-10-23 (earliest version still in the registry; older removed versions would be earlier)

Version history

4 versions listed, 2026-10-23 to 2026-10-24; 4 in the 90 days before the 2026-10-24 snapshot.

Most recent 4 versions

1.5.0 · 2026-10-24
1.4.0 · 2026-10-24
1.3.0 · 2026-10-24
1.0.0 · 2026-10-23

(versions still listed in the registry only)

Registry data

snapshot 2026-10-24

Package and repository

checked 2026-10-24

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-23, listed on 2026-10-24 with version 1.5.0 (published 2026-10-24).

Source: the official MCP Registry list on 2026-10-23 and on 2026-10-24.

What it is

What does this server offer?

Observed inventory

23tools

0resources

1prompts

None of its 23 tools are described as changing anything. For 23 the reading was uncertain, so no mark is shown.

clio_who_am_i
“Fetch the Clio user this access token belongs to — name, email, subscription type, time zone and default_calendar_id (needed to create calendar entries).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
clio_list_users
“List the firm's Clio users (attorneys and staff) — use their ids for responsible attorneys, time entries and task assignees.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
7 inputs
- namestring“Only users with this name.”
- enabledboolean“Only enabled (true) or disabled (false) users.”
- subscription_typestring“Only attorneys or non-attorneys.”
- rolestring“Only users with this role.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
- limitinteger“Records per page, 1-2000 (default 50).”
- page_tokenstring“next_page.page_token from the previous page.”
clio_list_matters
“Search and list matters (the firm's cases) with their client, practice area, responsible attorney and status.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
16 inputs
- querystring“Wildcard search on display number, number, description, or the client's name.”
- statusstring“open, closed or pending — or several comma-separated, e.g.”
- client_idinteger“Only this client's (contact id) matters.”
- responsible_attorney_idinteger“Only matters with this responsible attorney (user id).”
- originating_attorney_idinteger“Only matters with this originating attorney (user id).”
- practice_area_idinteger“Only matters in this practice area.”
- billableboolean“Only billable (true) or non-billable (false) matters.”
- custom_field_idinteger“Only records whose custom field with this id (from clio_list_custom_fields) matches custom_field_value.”
- custom_field_valuestring“The value to match.”
- custom_field_operatorstring“Required for currency, date, time and numeric fields (= for an exact match); leave it out for every other field type.”
- updated_sincestring“Only records updated after this ISO-8601 timestamp, e.g.”
- orderstring“Sort order.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
- limitinteger“Records per page, 1-200 (default 50).”
- page_tokenstring“next_page.page_token from the previous page.”
- offsetinteger“next_page.offset from the previous page (used when a custom order is set; capped at 10,000 records).”
clio_get_matter
“Fetch a single matter by id, with its client, practice area, stage, attorneys and custom field values (field_name + value; a picklist value is an option id, see clio_list_custom_fields).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- matter_idintegerrequired“The matter's numeric Clio id.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
clio_list_contacts
“Search and list contacts — clients, prospective clients, companies, opposing parties and co-counsel.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
14 inputs
- querystring“Wildcard search across name, title, email, phone, address, web site and custom fields.”
- typestring“Only people or only companies.”
- client_onlyboolean“Only contacts who are clients.”
- email_onlyboolean“Only contacts that have an email address.”
- initialstring“Only contacts whose last name or company name starts with this letter (A-Z).”
- custom_field_idinteger“Only records whose custom field with this id (from clio_list_custom_fields) matches custom_field_value.”
- custom_field_valuestring“The value to match.”
- custom_field_operatorstring“Required for currency, date, time and numeric fields (= for an exact match); leave it out for every other field type.”
- updated_sincestring“Only records updated after this ISO-8601 timestamp, e.g.”
- orderstring“Sort order.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
- limitinteger“Records per page, 1-200 (default 50).”
- page_tokenstring“next_page.page_token from the previous page.”
- offsetinteger“next_page.offset from the previous page (used when a custom order is set; capped at 10,000 records).”
clio_get_contact
“Fetch a single contact by id with all email addresses, phone numbers, postal addresses, web sites and custom field values (field_name + value; a picklist value is an option id, see clio_list_custom_f…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- contact_idintegerrequired“The contact's numeric Clio id.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
clio_list_activities
“List activities — time entries, expense entries and fixed fees — with hours, rate, total and billing status.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
13 inputs
- matter_idinteger“Only this matter's activities.”
- user_idinteger“Only this user's activities.”
- typestring“Only this kind of activity.”
- statusstring“Only activities in this billing status.”
- start_datestring“Only activities dated on or after this day (ISO-8601 date or timestamp).”
- end_datestring“Only activities dated on or before this day (ISO-8601 date or timestamp).”
- querystring“Wildcard search on the activity's note.”
- updated_sincestring“Only records updated after this ISO-8601 timestamp, e.g.”
- orderstring“Sort order.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
- limitinteger“Records per page, 1-200 (default 50).”
- page_tokenstring“next_page.page_token from the previous page.”
- offsetinteger“next_page.offset from the previous page (used when a custom order is set; capped at 10,000 records).”
clio_list_tasks
“List tasks with status, priority, due date, matter and assignee.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
16 inputs
- matter_idinteger“Only this matter's tasks.”
- assignee_idinteger“Only tasks assigned to this user or contact id.”
- assignee_typestring“Whether assignee_id is a user or a contact.”
- statusstring“Only tasks in this status (without advanced tasks, only pending or complete).”
- completeboolean“Only complete (true) or incomplete (false) tasks.”
- prioritystring“Only tasks with this priority.”
- due_at_fromstring“Start of a due-date range (ISO-8601 date, YYYY-MM-DD).”
- due_at_tostring“End of a due-date range (ISO-8601 date, YYYY-MM-DD).”
- statute_of_limitationsboolean“Only statute-of-limitations tasks (true) or others (false).”
- querystring“Wildcard search on the task's name or description.”
- updated_sincestring“Only records updated after this ISO-8601 timestamp, e.g.”
- orderstring“Sort order.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
- limitinteger“Records per page, 1-200 (default 50).”
- page_tokenstring“next_page.page_token from the previous page.”
- offsetinteger“next_page.offset from the previous page (used when a custom order is set; capped at 10,000 records).”
clio_list_calendar_entries
“List calendar entries (hearings, meetings, deadlines) in a time window, optionally for one matter or calendar.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
12 inputs
- fromstring“Only entries ending on or after this ISO-8601 timestamp.”
- tostring“Only entries starting on or before this ISO-8601 timestamp.”
- matter_idinteger“Only this matter's entries.”
- calendar_idinteger“Only entries on this calendar.”
- expandedboolean“Return one record per occurrence of recurring events.”
- is_all_dayboolean“Only all-day (true) or timed (false) entries.”
- querystring“Search text.”
- updated_sincestring“Only records updated after this ISO-8601 timestamp, e.g.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
- limitinteger“Records per page, 1-200 (default 50).”
- page_tokenstring“next_page.page_token from the previous page.”
- offsetinteger“next_page.offset from the previous page (used when a custom order is set; capped at 10,000 records).”
clio_list_bills
“List bills (invoices) with state, totals, amount due and dates.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
15 inputs
- client_idinteger“Only this client's bills.”
- matter_idinteger“Only this matter's bills.”
- statestring“Only bills in this state.”
- overdue_onlyboolean“Only overdue bills.”
- issued_afterstring“Only bills issued after this day (ISO-8601 date, YYYY-MM-DD).”
- issued_beforestring“Only bills issued before this day (ISO-8601 date, YYYY-MM-DD).”
- due_afterstring“Only bills due after this day (ISO-8601 date, YYYY-MM-DD).”
- due_beforestring“Only bills due before this day (ISO-8601 date, YYYY-MM-DD).”
- typestring“Only revenue or trust bills.”
- updated_sincestring“Only records updated after this ISO-8601 timestamp, e.g.”
- orderstring“Sort order.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
- limitinteger“Records per page, 1-200 (default 50).”
- page_tokenstring“next_page.page_token from the previous page.”
- offsetinteger“next_page.offset from the previous page (used when a custom order is set; capped at 10,000 records).”
clio_get_bill
“Fetch a single bill by id with its state, totals, balance, client and matters.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- bill_idintegerrequired“The bill's numeric Clio id.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
clio_list_documents
“List documents (metadata only: name, file name, type, size, category, dates) for a matter, a contact or a folder, or search them by name.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
12 inputs
- matter_idinteger“Only this matter's documents.”
- contact_idinteger“Only this contact's documents.”
- parent_idinteger“Only documents in this folder.”
- scopestring“With parent_id: direct children only (default) or everything beneath the folder.”
- document_category_idinteger“Only documents in this category.”
- querystring“Wildcard search on the document name.”
- updated_sincestring“Only records updated after this ISO-8601 timestamp, e.g.”
- orderstring“Sort order.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
- limitinteger“Records per page, 1-200 (default 50).”
- page_tokenstring“next_page.page_token from the previous page.”
- offsetinteger“next_page.offset from the previous page (used when a custom order is set; capped at 10,000 records).”

Show 11 more tools

clio_list_notes
“List notes on a matter or a contact, with subject, body, date and author.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
10 inputs, 1 required
- typestringrequired“Matter notes or contact notes.”
- matter_idinteger“For type Matter: the matter's id.”
- contact_idinteger“For type Contact: the contact's id.”
- querystring“Wildcard search across subject and detail.”
- updated_sincestring“Only records updated after this ISO-8601 timestamp, e.g.”
- orderstring“Sort order.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
- limitinteger“Records per page, 1-200 (default 50).”
- page_tokenstring“next_page.page_token from the previous page.”
- offsetinteger“next_page.offset from the previous page (used when a custom order is set; capped at 10,000 records).”
clio_list_custom_fields
“List the firm's custom fields for matters or contacts — name, type, whether required, and the options of picklist fields (option id + text).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
10 inputs
- parent_typestring“Only matter fields or only contact fields.”
- field_typestring“Only fields of this type.”
- querystring“Wildcard search on the field name.”
- deletedboolean“Only fields deleted for future use (true) or active ones (false).”
- visible_and_requiredboolean“Only fields that are visible and required.”
- orderstring“Sort order.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
- limitinteger“Records per page, 1-200 (default 50).”
- page_tokenstring“next_page.page_token from the previous page.”
- offsetinteger“next_page.offset from the previous page (used when a custom order is set; capped at 10,000 records).”
clio_list_communications
“List logged communications — phone calls and emails recorded on matters — with subject, body, date, senders and receivers.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
14 inputs
- matter_idinteger“Only this matter's communications.”
- contact_idinteger“Only communications with this contact.”
- user_idinteger“Only communications of this user.”
- typestring“Only phone calls or only emails.”
- received_sincestring“Only communications on or after this day (ISO-8601 date, YYYY-MM-DD).”
- received_beforestring“Only communications on or before this day (ISO-8601 date, YYYY-MM-DD).”
- querystring“Wildcard search on subject and body.”
- having_time_entriesboolean“Only communications with (true) or without (false) time entries.”
- updated_sincestring“Only records updated after this ISO-8601 timestamp, e.g.”
- orderstring“Sort order.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
- limitinteger“Records per page, 1-200 (default 20: email bodies can be long).”
- page_tokenstring“next_page.page_token from the previous page.”
- offsetinteger“next_page.offset from the previous page (used when a custom order is set; capped at 10,000 records).”
clio_create_contact
“WRITE: Create a contact — a person (give first_name and/or last_name) or a company (give name) — optionally with an email address and phone number.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
12 inputs, 1 required
- typestringrequired“Person or Company.”
- first_namestring“Person: first name.”
- last_namestring“Person: last name.”
- middle_namestring“Person: middle name.”
- namestring“Company: the company name.”
- titlestring“Professional title, e.g.”
- prefixstring“Personal title, e.g.”
- emailstring“An email address to add.”
- email_typestring“Label for the email address (default Work).”
- phonestring“A phone number to add.”
- phone_typestring“Label for the phone number (default Work).”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
clio_create_matter
“WRITE: Open a new matter for an existing client contact.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
11 inputs, 2 required
- client_idintegerrequired“The client contact's numeric Clio id.”
- descriptionstringrequired“What the matter is, e.g.”
- statusstring“Initial status (Clio defaults to open).”
- open_datestring“Open date (ISO-8601 date, YYYY-MM-DD).”
- practice_area_idinteger“Practice area id.”
- responsible_attorney_idinteger“Responsible attorney (user id).”
- originating_attorney_idinteger“Originating attorney (user id).”
- billableboolean“Whether the matter is billable.”
- locationstring“Location of the matter.”
- client_referencestring“The client's own reference for this matter.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
clio_create_time_entry
“WRITE: Record billable (or non-billable) time on a matter.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
9 inputs, 3 required
- matter_idintegerrequired“The matter's numeric Clio id.”
- datestringrequired“The day the work was done (ISO-8601 date, YYYY-MM-DD).”
- hoursnumberrequired“Time spent, in hours (decimal).”
- notestring“What the time was for — this appears on the bill.”
- pricenumber“Hourly rate override.”
- user_idinteger“The user who did the work (default: the token's user).”
- activity_description_idinteger“An activity description (billing code) id.”
- non_billableboolean“Keep this entry off the bill.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
clio_create_task
“WRITE: Create a task and assign it to a firm user or a contact, optionally on a matter with a due date and priority.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
12 inputs, 4 required
- namestringrequired“Short name of the task.”
- descriptionstringrequired“Longer description of the task.”
- assignee_idintegerrequired“The user or contact to assign the task to.”
- assignee_typestringrequired“Whether assignee_id is a User or a Contact.”
- matter_idinteger“The matter the task belongs to.”
- due_atstring“Due date (ISO-8601 date, YYYY-MM-DD).”
- prioritystring“Priority.”
- statusstring“Initial status (without advanced tasks, only pending or complete).”
- permissionstring“Visibility (Clio default public).”
- notify_assigneeboolean“Notify the assignee on creation.”
- statute_of_limitationsboolean“Mark as a statute-of-limitations task.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
clio_update_task
“WRITE: Update a task — mark it complete, change its status, due date, priority, name or description, or reassign it.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
9 inputs, 1 required
- task_idintegerrequired“The task's numeric Clio id.”
- statusstring“New status, e.g.”
- due_atstring“New due date (ISO-8601 date, YYYY-MM-DD).”
- prioritystring“New priority.”
- namestring“New name.”
- descriptionstring“New description.”
- assignee_idinteger“Reassign to this user or contact.”
- assignee_typestring“Whether assignee_id is a User or a Contact.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
clio_create_note
“WRITE: Add a note to a matter (type Matter + matter_id) or to a contact (type Contact + contact_id).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
7 inputs, 2 required
- typestringrequired“Attach to a matter or a contact.”
- matter_idinteger“For type Matter: the matter's id.”
- contact_idinteger“For type Contact: the contact's id.”
- subjectstring“Note subject.”
- detailstringrequired“Note body (plain text).”
- datestring“Date of the note (ISO-8601 date, YYYY-MM-DD).”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
clio_log_communication
“WRITE: Record a phone call or an email on Clio's communication log, optionally on a matter, with who it was from and to.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
8 inputs, 4 required
- typestringrequired“A phone call or an email.”
- subjectstringrequired“Subject line, e.g.”
- bodystringrequired“What was said or written (plain text).”
- received_atstringrequired“When it took place (ISO-8601 timestamp, e.g.”
- matter_idinteger“The matter it belongs to.”
- sendersarray“Who it came from: firm users and/or contacts.”
- receiversarray“Who it went to: firm users and/or contacts.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”
clio_create_calendar_entry
“WRITE: Put an event on a Clio calendar — a hearing, meeting or deadline — optionally linked to a matter.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
10 inputs, 4 required
- calendar_idintegerrequired“The calendar's numeric Clio id.”
- summarystringrequired“Short title of the event.”
- start_atstringrequired“Start (ISO-8601 timestamp, e.g.”
- end_atstringrequired“End (ISO-8601 timestamp).”
- all_dayboolean“An all-day event.”
- descriptionstring“Longer description.”
- locationstring“Where it takes place.”
- matter_idinteger“The matter this event belongs to.”
- send_email_notificationboolean“Email the attendees.”
- fieldsstring“Override the returned fields: a comma-separated list, nested resources in braces one level deep, e.g.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-24.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 100% of 224
Tools with a description: 100% of 23
Typical description length: 206 characters

The tool set

Counted from the listing

Tools: 23
Size of the list: about 10,611 tokens for an agent to load (characters ÷ 4)
Naming: 23 of 23 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 23 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-24 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://clio.usefulapi.io/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "clio": {
      "url": "https://clio.usefulapi.io/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "clio": {
      "type": "http",
      "url": "https://clio.usefulapi.io/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"clio","type":"http","url":"https://clio.usefulapi.io/mcp"}'

Claude Code

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

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://clio.usefulapi.io/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint clio.usefulapi.io/mcp	Session opened	matches	our test · 2026-10-24
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-24
Repository github.com/m190/usefulapi-mcp	Opens publicly	matches	api.github.com · 2026-10-24

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.usefulapi · 409 servers
GitHub owner: a personal account (m190)

Repository: github.com/m190/usefulapi-mcp
Stars: 0
Repository age: 91–180 days
Last push: 0–30 days ago
Archived: no

Source: the registry entry and api.github.com · 2026-10-24.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 4 record checks met · 4 do not apply · 1 not checked

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-24. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.usefulapi/clio

Answered from the data above

Is io.usefulapi/clio safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.usefulapi/clio need an API key or sign-in?

It opened a session without any credential on 2026-10-24. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.usefulapi/clio been security tested?

Partly. 3 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

Where is the source code of io.usefulapi/clio?

In github.com/m190/usefulapi-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-24

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not run · an error was returned
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

3 exercised13 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 13

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 2

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-24, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
306 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 23 tools, 0 resources, 1 prompt.
1,275 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in the weekly update

listed 2026-10-24; not classified yet

Pricing modelAI-classified

pending: added in the weekly update

the website is not read yet

Programming language

JavaScript

api.github.com · 2026-10-24

Hosting type

remote (hosted by the publisher)

registry · 2026-10-24

MCP capability

prompts, tools

our test · 2026-10-24

Transport

streamable HTTP

registry · 2026-10-24

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-24

Lifecycle status

active

registry · 2026-10-24

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: a personal account · repository age: 91–180 days · stars: 0–9

api.github.com · 2026-10-24

Maintenance

active

api.github.com · 2026-10-24

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.usefulapi/clio: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/io.usefulapi/clio

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.usefulapi/clio)](https://protocolprobe.com/mcp/servers/io.usefulapi/clio)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology