sortly

Status

Newest check: answered with tools, from the daily check, 2026-10-03, 781 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-042026-10-03

answered with toolssign-in or payment askednot answeringnot checked

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

Tools

20 tools: 11 read-only, 0 change data, 9 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 7,058 tokens of tool definitions and a 781 ms handshake.

• high risksortly_get_purchase_orderFetch a single purchase order with its line_items (quantity vs received_quantity), vendor, addresses, charges, totals and version. Sortly: GET /api/v1/purchase_orders/{purchase_order_id}.
• high risksortly_create_itemCreate a trackable item (type item) or a folder (type folder), optionally inside a folder via parent_id, with quantity, price, tags, custom fields, barcodes and a measured quantity. WRITE. Sortly: POST /api/v1/items.
• high risksortly_update_itemChange fields on an existing item or folder - e.g. set a new quantity after a stock count, rename it, or relocate a folder via parent_id. Only the fields you pass change; pass null to clear a nullable field. Sending tags or custom_attribute_values replaces them. WRITE. Sortly: PUT /api/v1/items/{...
• high risksortly_move_itemMove some or all of an item's quantity to another folder (items only - relocate a folder with sortly_update_item parent_id). A partial move splits off a new item with the same sid; a full move relocates the item; a matching item at the destination is merged, and the returned id is the destination...
• high risksortly_create_alertCreate a stock alert on an item (type Quantity, e.g. threshold_method quantity_less_than with threshold_value 5, or less_than_or_equal_to_min_quantity), or a DateReminder on a datetime custom field (custom_attribute_id + before/after/same_day + threshold_interval). WRITE. Sortly: POST /api/v1/ale...
• high risksortly_create_jobCreate a job (and its job folder) in not_started status. Name must be unique in the company. Then use sortly_pull_items_into_job to record the stock it uses. WRITE. Sortly: POST /api/v1/jobs.
• high risksortly_pull_items_into_jobMove quantities of existing items (from any folders) into a job's folder - how usage on a job is recorded. Up to 100 items per call; items are processed independently, so ALWAYS check data.errors (a partial failure still returns 200). Undo with sortly_return_items_from_job. Returns 403 on a compl...
• high risksortly_return_items_from_jobMove items off a job's folder back into inventory (destination_folder_id, or All Items if omitted). Up to 100 per call; check data.errors - items are processed one by one. WRITE. Sortly: POST /api/v1/jobs/{job_id}/items/return.
• high risksortly_create_purchase_orderCreate a purchase order in draft status (no stock or ordering happens until it is moved on in Sortly). Sortly computes amounts, sub_total and total from the lines; omit purchase_order_number to have one generated. Needs Purchase Orders on the plan (else 402). WRITE. Sortly: POST /api/v1/purchase_...
• read-onlysortly_list_itemsList items and folders, newest first. By default the root level; pass folder_id for a folder's direct contents, plus include_subfolders for everything nested under it. Paginated via meta.next_page_url / total_pages. Sortly: GET /api/v1/items.
• read-onlysortly_get_itemFetch a single item or folder by numeric id: quantity, min_quantity, price, tags, sid, barcodes, and optionally custom field values and photos. Sortly: GET /api/v1/items/{item_id}.
• read-onlysortly_search_itemsSearch items and folders by name, optionally limited to items or folders and scoped to specific folders. Read-only despite being a POST. Paginated: send the same arguments with the next page number. Sortly: POST /api/v1/items/search.
• read-onlysortly_list_recently_updated_itemsList items and folders changed since a Unix timestamp - the incremental-sync read ('what moved since yesterday?'). Without updated_since it behaves like sortly_list_items. Sortly: GET /api/v1/items/recent.
• read-onlysortly_list_custom_fieldsList the account's custom fields (id, name, type, applies_to). Call this before writing custom_attribute_values to get the right custom_attribute_id. Sortly: GET /api/v1/custom_fields.
• read-onlysortly_list_unitsList the units of measure available to the account (unit_name, unit_type, scale) - the values measured_quantity and purchase-order lines expect. Sortly: GET /api/v1/units.
• read-onlysortly_list_alertsList stock (Quantity) and date (DateReminder) alerts, with is_fired showing which have already triggered - the quick way to find low-stock items. Sortly: GET /api/v1/alerts.
• read-onlysortly_list_jobsList jobs (work orders that pull stock out), most recently updated first, filterable by name prefix and status. Paginated via meta.pagination.has_next. Sortly: GET /api/v1/jobs.
• read-onlysortly_get_jobFetch a single job: status, folder_id (where its pulled items sit), dates, notes, custom field values and the version needed for updates. Sortly: GET /api/v1/jobs/{job_id}.
• read-onlysortly_list_purchase_ordersList purchase orders, most recently updated first, filterable by PO number and status. The list leaves out notes, terms, sub_total and line_items - use sortly_get_purchase_order for those. Needs Purchase Orders on the plan (else 402). Sortly: GET /api/v1/purchase_orders.
• read-onlysortly_get_purchase_order_receive_statusReport the most recent receive against a purchase order: pending / completed / failed, with the line ids received, pending and failed (and why). Returns 404 until something has been received. Sortly: GET /api/v1/purchase_orders/{purchase_order_id}/receive/status.

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

Badge

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

[![7Maps](https://7it.co.il/7maps/badge/sortly.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/sortly.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=sortly.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/sortly.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/sortly.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=sortly.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.