Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Precoro MCP by usefulapi

REMOTE · PRECORO.USEFULAPI.IO

Read Precoro purchase orders, invoices, suppliers and budgets; approve, reject and submit documents.

62 Trust /100

Last scanned (3 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 25 Oct 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security78
Transport & Reachability0
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4265 tokens (~177/item across 24 items; 24 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.2.1 → 1.2.3 functional
    • Server version: 1.2.0 → 1.2.1 functional
  • 24 Oct 26 61

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Oct 2026 · Probed https://precoro.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of precoro.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690, 57355 8, 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 302

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://precoro.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Bearer realm="OAuth", resource_metadata="https://precoro.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://precoro.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://precoro.usefulapi.io/mcp
Authorisation server https://precoro.usefulapi.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://precoro.usefulapi.io/mcp Redirected 302 https://usefulapi.io/precoro/
http (plaintext) http://precoro.usefulapi.io/mcp Inconclusive 302 http://precoro.usefulapi.io/mcp
MCP tools · 24 exposed · ~4,004 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
precoro_approve_document ~151

WRITE: approve a document as the Precoro user the API key belongs to (that user must be a current approver of it). Approving can release spending: an approved purchase order may be sent to the supplier and an approved invoice can go to payment. Find candidates with the list tools and waiting_for_my_approval. Cannot be undone through this server. POST /{document}/{idn}/approve.

NameTypeReqDescription
documentstringyesDocument type: warehouserequests, purchaserequisitions, purchaseorders, receipts, invoices or expenses.
idnstringyesThe document IDN: the company's own document number as shown in Precoro (not the internal id).

No output schema declared.

No examples provided.

precoro_create_purchase_requisition ~247

WRITE: create a purchase requisition in draft (open) status for the key user; it is not submitted for approval until precoro_submit_document is called. Needs a location id, a currency, a delivery date and at least one item (a catalog item_id, or a name with quantity and price). Find ids with precoro_list_reference_data (locations, legal_entities, document_custom_fields) and precoro_list_items. All required document custom fields (for example department or project) must be passed in custom_fields. Returns the new idn and id. POST /purchaserequisitions.

NameTypeReqDescription
budget_idinteger–Budget line id.
currencystringyes–
custom_fieldsarray–Document custom field values (department, project, GL account...). Every required one must be given.
itemsarrayyes–
legal_entity_idinteger–Required when the company uses legal entities.
location_idintegeryesLocation id (must be accessible to the key user).
notestring–Plain-text note (stored as HTML).
required_datestringyesDelivery date, yyyy-mm-dd.

No output schema declared.

No examples provided.

precoro_create_supplier ~228

WRITE: create a supplier. The name must be unique in the company (a duplicate name, unique code or registration number is rejected). The supplier is available to all legal entities. Depending on the company's settings it may need approval before it can be used on orders. Returns the new supplier. POST /suppliers.

NameTypeReqDescription
citystring––
conditionsstring–Payment or delivery conditions text.
contactsarray–Supplier contacts. Precoro can email purchase orders to them.
countrystring–Country code or name as Precoro shows it, e.g. US.
currenciesarray–Currencies the supplier is paid in, e.g. ["USD"].
delivery_period_daysinteger––
legal_addressstring––
minimum_order_sumnumber––
namestringyes–
notestring––
phonestring––
postal_codestring––
statestring––
unique_codestring–Your own supplier code (unique).

No output schema declared.

No examples provided.

precoro_get_expense ~61

One expense document by IDN with items, custom fields and approval steps. GET /expenses/{idn}.

NameTypeReqDescription
idnstringyesThe document IDN: the company's own document number as shown in Precoro (not the internal id).

No output schema declared.

No examples provided.

precoro_get_invoice ~70

One supplier invoice or credit note by IDN with items, taxes, matching to purchase orders and receipts, and payments. GET /invoices/{idn}.

NameTypeReqDescription
idnstringyesThe document IDN: the company's own document number as shown in Precoro (not the internal id).

No output schema declared.

No examples provided.

precoro_get_item ~32

One catalog item by id. GET /items/{id}.

NameTypeReqDescription
idintegeryesThe item id.

No output schema declared.

No examples provided.

precoro_get_purchase_order ~70

One purchase order by IDN with all items, taxes, custom fields, approval steps, receiving and payment status. GET /purchaseorders/{idn}.

NameTypeReqDescription
idnstringyesThe document IDN: the company's own document number as shown in Precoro (not the internal id).

No output schema declared.

No examples provided.

precoro_get_purchase_requisition ~68

One purchase requisition by IDN with items, custom fields and approval steps. GET /purchaserequisitions/{idn}.

NameTypeReqDescription
idnstringyesThe document IDN: the company's own document number as shown in Precoro (not the internal id).

No output schema declared.

No examples provided.

precoro_get_receipt ~59

One goods receipt by IDN with items and approval steps. GET /receipts/{idn}.

NameTypeReqDescription
idnstringyesThe document IDN: the company's own document number as shown in Precoro (not the internal id).

No output schema declared.

No examples provided.

precoro_get_supplier ~58

One supplier by id with contacts, conditions, custom field defaults and credit balance. Bank details are never returned. GET /suppliers/{id}.

NameTypeReqDescription
idintegeryesThe supplier id (the numeric id, not the unique code).

No output schema declared.

No examples provided.

precoro_list_ap_inbox ~108

List documents in the accounts-payable inbox (uploaded or emailed supplier invoices read by OCR): file name, supplier, gross total, currency, status, upload and processed dates. GET /ap/documents.

NameTypeReqDescription
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page: 10, 20, 50, 100 or 200 (default 20).

No output schema declared.

No examples provided.

precoro_list_budgets ~105

List budgets with name, period, total sum, how much is used in purchase requisitions, purchase orders, invoices and expenses, and whether the limit is enforced. GET /budgets.

NameTypeReqDescription
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page: 10, 20, 50, 100 or 200 (default 20).

No output schema declared.

No examples provided.

precoro_list_contracts ~89

List supplier contracts with number, supplier, begin and end dates and whether they auto-prolong. GET /contracts.

NameTypeReqDescription
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page: 10, 20, 50, 100 or 200 (default 20).

No output schema declared.

No examples provided.

precoro_list_expenses ~330

List expense documents (purchases without a purchase order): supplier, totals, currency, status and payment status. Filter by status, last-modified time, approval date range, or 'waiting for my approval'. GET /expenses.

NameTypeReqDescription
approved_fromstring–Only documents whose final approval is on or after this UTC time: yyyy-mm-dd or yyyy-mm-ddThh:mm:ss.
approved_tostring–Only documents whose final approval is on or before this UTC time: yyyy-mm-dd or yyyy-mm-ddThh:mm:ss.
modified_sincestring–Only records created or changed since this UTC time: yyyy-mm-dd or yyyy-mm-ddThh:mm:ss.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page: 10, 20, 50, 100 or 200 (default 20).
statusarray–Status codes to include. 0 open (draft), 1 pending approval, 2 approved, 3 denied, 4 partly paid (invoices/expenses) or stopped (blanket PO), 5 purchased (PO/PR) or paid (invoices/expenses), 6 awaiti…
waiting_for_my_approvalboolean–true = only documents waiting for approval by the user the API key belongs to (waitingForapprove=yes).

No output schema declared.

No examples provided.

precoro_list_invoices ~369

List supplier invoices and credit notes: supplier, totals, currency, issue and due dates, paid sum, approval/payment status. Filter by status, kind, last-modified time, approval date range, or 'waiting for my approval'. GET /invoices.

NameTypeReqDescription
approved_fromstring–Only documents whose final approval is on or after this UTC time: yyyy-mm-dd or yyyy-mm-ddThh:mm:ss.
approved_tostring–Only documents whose final approval is on or before this UTC time: yyyy-mm-dd or yyyy-mm-ddThh:mm:ss.
kindarray–Invoice kinds: 0 standard, 1 credit note, 2 from order, 3 recurring, 4 from service order.
modified_sincestring–Only records created or changed since this UTC time: yyyy-mm-dd or yyyy-mm-ddThh:mm:ss.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page: 10, 20, 50, 100 or 200 (default 20).
statusarray–Status codes to include. 0 open (draft), 1 pending approval, 2 approved, 3 denied, 4 partly paid (invoices/expenses) or stopped (blanket PO), 5 purchased (PO/PR) or paid (invoices/expenses), 6 awaiti…
waiting_for_my_approvalboolean–true = only documents waiting for approval by the user the API key belongs to (waitingForapprove=yes).

No output schema declared.

No examples provided.

precoro_list_items ~130

List catalog items (products and services): name, SKU, unit, price, currency, supplier, group and custom fields. Filter by last-modified time. GET /items.

NameTypeReqDescription
modified_sincestring–Only records created or changed since this UTC time: yyyy-mm-dd or yyyy-mm-ddThh:mm:ss.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page: 10, 20, 50, 100 or 200 (default 20).

No output schema declared.

No examples provided.

precoro_list_payments ~124

List payments recorded against invoices and expenses: pay date, sum paid, status (0 paid, 8 canceled), kind (0 payment, 1 credit, 2 supplier credit balance, 3-6 prepayments/credits) and the invoice or expense paid. GET /payments.

NameTypeReqDescription
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page: 10, 20, 50, 100 or 200 (default 20).

No output schema declared.

No examples provided.

precoro_list_purchase_orders ~438

List purchase orders (POs) with number (idn), supplier, location, totals, currency, required date, approval status, receiving status (0 not received, 1 partly, 2 received) and payment status (0 needs invoice, 1 not paid, 2 partly paid, 3 paid). Line items come only from precoro_get_purchase_order. Filter by status, last-modified time, approval date range, or 'waiting for my approval'. Page with next_page. GET /purchaseorders.

NameTypeReqDescription
approved_fromstring–Only documents whose final approval is on or after this UTC time: yyyy-mm-dd or yyyy-mm-ddThh:mm:ss.
approved_tostring–Only documents whose final approval is on or before this UTC time: yyyy-mm-dd or yyyy-mm-ddThh:mm:ss.
modified_sincestring–Only records created or changed since this UTC time: yyyy-mm-dd or yyyy-mm-ddThh:mm:ss.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page: 10, 20, 50, 100 or 200 (default 20).
statusarray–Status codes to include. 0 open (draft), 1 pending approval, 2 approved, 3 denied, 4 partly paid (invoices/expenses) or stopped (blanket PO), 5 purchased (PO/PR) or paid (invoices/expenses), 6 awaiti…
typearray–PO types: 0 standard, 1 blanket, 2 from requisitions, 3 recurring, 4 blanket per total, 5 service, 6 recurring service, 7 service from requisitions.
waiting_for_my_approvalboolean–true = only documents waiting for approval by the user the API key belongs to (waitingForapprove=yes).

No output schema declared.

No examples provided.

precoro_list_purchase_requisitions ~347

List purchase requisitions (purchase requests): requester, location, totals, required date, approval status. Line items come only from precoro_get_purchase_requisition. Filter by status, last-modified time, approval date range, or 'waiting for my approval'. GET /purchaserequisitions.

NameTypeReqDescription
approved_fromstring–Only documents whose final approval is on or after this UTC time: yyyy-mm-dd or yyyy-mm-ddThh:mm:ss.
approved_tostring–Only documents whose final approval is on or before this UTC time: yyyy-mm-dd or yyyy-mm-ddThh:mm:ss.
modified_sincestring–Only records created or changed since this UTC time: yyyy-mm-dd or yyyy-mm-ddThh:mm:ss.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page: 10, 20, 50, 100 or 200 (default 20).
statusarray–Status codes to include. 0 open (draft), 1 pending approval, 2 approved, 3 denied, 4 partly paid (invoices/expenses) or stopped (blanket PO), 5 purchased (PO/PR) or paid (invoices/expenses), 6 awaiti…
waiting_for_my_approvalboolean–true = only documents waiting for approval by the user the API key belongs to (waitingForapprove=yes).

No output schema declared.

No examples provided.

precoro_list_receipts ~341

List goods receipts (what was delivered against purchase orders): purchase order, status and dates. Line items and received quantities come only from precoro_get_receipt. Filter by status, last-modified time, approval date range, or 'waiting for my approval'. GET /receipts.

NameTypeReqDescription
approved_fromstring–Only documents whose final approval is on or after this UTC time: yyyy-mm-dd or yyyy-mm-ddThh:mm:ss.
approved_tostring–Only documents whose final approval is on or before this UTC time: yyyy-mm-dd or yyyy-mm-ddThh:mm:ss.
modified_sincestring–Only records created or changed since this UTC time: yyyy-mm-dd or yyyy-mm-ddThh:mm:ss.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page: 10, 20, 50, 100 or 200 (default 20).
statusarray–Status codes to include. 0 open (draft), 1 pending approval, 2 approved, 3 denied, 4 partly paid (invoices/expenses) or stopped (blanket PO), 5 purchased (PO/PR) or paid (invoices/expenses), 6 awaiti…
waiting_for_my_approvalboolean–true = only documents waiting for approval by the user the API key belongs to (waitingForapprove=yes).

No output schema declared.

No examples provided.

precoro_list_reference_data ~201

List a configuration table: users (name, email, roles), locations, legal_entities, taxes, payment_terms, units, warehouses, product_groups, document_custom_fields (departments, projects, classes, GL accounts), item_custom_fields or supplier_custom_fields. Use it to find the ids that purchase requisitions and suppliers need (location, legal entity, custom field). Bank details are never returned. GET /users, /locations, /legalentities, /taxes, /paymentterms, /units, /warehouses, /groups, /documentcustomfields, /itemcustomfields, /suppliercustomfields.

NameTypeReqDescription
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page: 10, 20, 50, 100 or 200 (default 20).
tablestringyesWhich table to list.

No output schema declared.

No examples provided.

precoro_list_suppliers ~140

List suppliers: name, unique code, currencies, payment conditions, minimum order sum, contact and address fields, accounting ids, status. Bank details are never returned. Filter by last-modified time. GET /suppliers.

NameTypeReqDescription
modified_sincestring–Only records created or changed since this UTC time: yyyy-mm-dd or yyyy-mm-ddThh:mm:ss.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page: 10, 20, 50, 100 or 200 (default 20).

No output schema declared.

No examples provided.

precoro_reject_document ~128

WRITE: reject (deny) a document that is waiting for the key user's approval. A comment is required; the creator is notified and sees it. POST /{document}/{idn}/reject.

NameTypeReqDescription
commentstringyesWhy it is rejected (required, up to 800 characters).
documentstringyesDocument type: warehouserequests, purchaserequisitions, purchaseorders, receipts, invoices or expenses.
idnstringyesThe document IDN: the company's own document number as shown in Precoro (not the internal id).

No output schema declared.

No examples provided.

precoro_submit_document ~110

WRITE: confirm a draft (open) document so it enters the approval flow (or is approved at once if no approval is needed). Approvers are notified. POST /{document}/{idn}/confirm.

NameTypeReqDescription
documentstringyesDocument type: warehouserequests, purchaserequisitions, purchaseorders, receipts, invoices or expenses.
idnstringyesThe document IDN: the company's own document number as shown in Precoro (not the internal id).

No output schema declared.

No examples provided.

Install

How do I install the Precoro MCP by usefulapi server?

Precoro MCP by usefulapi is a hosted endpoint at https://precoro.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · precoro.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-precoro 'https://precoro.usefulapi.io/mcp'
Common questions

What is the Precoro MCP by usefulapi server?

Precoro MCP by usefulapi is listed in the public MCP registry as io.usefulapi/precoro. Read Precoro purchase orders, invoices, suppliers and budgets; approve, reject and submit documents. This page covers its hosted endpoint (https://precoro.usefulapi.io/mcp).

Is the Precoro MCP by usefulapi server safe to use?

Precoro MCP by usefulapi scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Precoro MCP by usefulapi server expose?

Precoro MCP by usefulapi exposes 24 tools: precoro_list_purchase_orders, precoro_get_purchase_order, precoro_list_purchase_requisitions, precoro_get_purchase_requisition, precoro_list_invoices, and 19 more. Their descriptions and schemas cost roughly 4,004 tokens of context every time the server is loaded.

Does the Precoro MCP by usefulapi server require authentication?

Yes. Precoro MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Precoro MCP by usefulapi server still maintained?

Precoro MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.