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.

Mercoa MCP by usefulapi

REMOTE · MERCOA.USEFULAPI.IO

Query and manage Mercoa AP/AR bill-pay: entities, invoices, transactions and payment methods.

−58 this week 18 Trust /100

Last scanned (6 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 5 Nov 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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (4)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 2 Nov 26 −61
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Stability: 0.97 → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +2
    • Authorization: partial → pass ▲ security
    • MCP protocol: fail → pass ▲ functional
    • Stability: pass → 0.93 functional
    • New prompt “check_payment_transactions_for_an_invoice_or_entity” functional
    • New prompt “create_a_bill_update_it_or_add_a_comment” functional
    • New prompt “find_bills_that_wait_for_approval” functional
    • New prompt “find_or_add_a_vendor_or_customer” functional
    • New prompt “see_the_history_of_an_invoice” functional
    • New prompt “total_invoice_amounts_per_entity_and_currency” functional
    • MCP protocol version: 2025-06-18 → 2025-11-25 functional
    • Server version: 1.31.0 → 1.33.0 functional
    • Server version: 1.30.0 → 1.31.0 functional
    • Server version: 1.29.2 → 1.30.0 functional
  • 30 Oct 26 0
    • Server version: 1.29.1 → 1.29.2 functional
    • Server version: 1.29.0 → 1.29.1 functional
  • 29 Oct 26 0
    • Server version: 1.28.0 → 1.29.0 functional
    • Server version: 1.27.0 → 1.28.0 functional
  • 28 Oct 26 0
    • Server version: 1.25.0 → 1.27.0 functional
  • 27 Oct 26 0
    • Server version: 1.24.0 → 1.25.0 functional
  • 25 Oct 26 0
    • Server version: 1.23.0 → 1.24.0 functional
    • Server version: 1.22.0 → 1.23.0 functional
    • Server version: 1.21.3 → 1.22.0 functional
    • Server version: 1.21.0 → 1.21.3 functional
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 5 Nov 2026 · Probed https://mercoa.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 mercoa.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
usefulapi.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mercoa.usefulapi.io/mcp Redirected 302 https://usefulapi.io/mercoa/
http (plaintext) http://mercoa.usefulapi.io/mcp Inconclusive 302 http://mercoa.usefulapi.io/mcp
MCP tools · 17 exposed · ~2,638 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
mercoa_add_invoice_comment ~75

WRITE — adds a comment to an invoice (visible in its activity log). POST /invoice/{invoiceId}/comment.

NameTypeReqDescription
invoiceIdstringyesInvoice ID to comment on.
textstringyesComment text.
userIdstring–ID or foreign ID of the user creating the comment.

No output schema declared.

No examples provided.

mercoa_create_entity ~211

WRITE — creates a real entity (customer/vendor/payor/payee) in Mercoa. Supply role flags, accountType, and a nested `profile` object (business or individual details). POST /entity.

NameTypeReqDescription
accountTypestring–business or individual.
emailstring–Primary email for the entity.
foreignIdstring–Your system's ID for this entity.
isCustomerboolean–Whether this entity has a direct relationship with your organization.
isPayeeboolean–Whether this entity can receive payments (AR / vendor).
isPayorboolean–Whether this entity can pay invoices (AP).
profileobject–Nested profile object, e.g. { "business": { "legalBusinessName": "Acme Inc.", "email": "ap@acme.com", "businessType": "llc" } } or { "individual": { "name": {...}, "email": "..." } }.

No output schema declared.

No examples provided.

mercoa_create_invoice ~335

WRITE — creates a real invoice/bill in Mercoa. Set status (DRAFT to stage, NEW to submit), amount, currency, payer/vendor, dates and line items. POST /invoice.

NameTypeReqDescription
amountnumber–Total invoice amount.
creatorEntityIdstring–Entity ID on whose behalf the invoice is created.
creatorUserIdstring–User ID creating the invoice.
currencystring–Currency code, e.g. USD.
deductionDatestring–Scheduled payment/deduction date (ISO 8601).
dueDatestring–Due date (ISO 8601).
invoiceDatestring–Invoice date (ISO 8601).
invoiceNumberstring–Human-readable invoice number, e.g. INV-123.
lineItemsarray–Line items array, e.g. [{ "amount": 100, "currency": "USD", "description": "Product A", "quantity": 1, "unitPrice": 100 }].
metadataobject–Arbitrary key/value metadata.
noteToSelfstring–Internal note.
payerIdstring–Payer entity ID (who owes).
paymentDestinationIdstring–Payment method ID to pay to (vendor's).
paymentSourceIdstring–Payment method ID to pay from (payer's).
statusstring–Invoice status, e.g. DRAFT, NEW, APPROVED, SCHEDULED.
vendorIdstring–Vendor entity ID (who is paid).

No output schema declared.

No examples provided.

mercoa_find_entities ~213

Find/search entities (buyers, vendors, payors, payees). Use to look up counterparties by name/email/foreignId or list all. GET /entity.

NameTypeReqDescription
foreignId––Your system's ID(s) for the entity.
isCustomerboolean–If true, only entities with a direct relationship to your organization.
isPayeeboolean–Filter entities marked as payees.
isPayorboolean–Filter entities marked as payors.
limitinteger–Max entities to return (1-100, default 10).
paymentMethodsboolean–If true, include payment methods in the response.
returnMetadata––Metadata key(s) to include in the response.
searchstring–Search by name, email, emailTo, entity ID, or foreign ID (partial matches).
startingAfterstring–Entity ID cursor for pagination.
status––Entity status filter (e.g. verified, pending).

No output schema declared.

No examples provided.

mercoa_find_invoices ~429

Find/search invoices (bills) across payers and vendors. Filter by status, entity, date, approver and more. GET /invoices (plural list endpoint).

NameTypeReqDescription
approverAction––Filter by approver action (use with approverId), e.g. APPROVE.
approverId––Filter by assigned approver user ID(s).
creatorUserId––Filter by the user ID(s) that created the invoice.
dateTypestring–Date type to filter by (e.g. CREATED_AT, DUE_DATE).
endDatestring–End date filter (ISO 8601).
entityGroupIdstring–Filter by entity group ID.
entityId––Filter by entity (payer or vendor) ID(s) or foreign ID(s).
invoiceId––Filter by invoice ID(s) or foreign ID(s).
invoiceTemplateId––Filter by invoice template ID(s).
limitinteger–Max invoices to return (1-100, default 10).
orderBystring–Field to order by (e.g. CREATED_AT, AMOUNT, DUE_DATE).
orderDirectionstring–asc or desc.
payerId––Filter by payer ID(s) or foreign ID(s).
paymentType––Filter by payment type (e.g. recurring).
returnPayerMetadataboolean–Include payer metadata in the response.
returnPaymentTimingboolean–Include payment timing in the response.
returnVendorMetadataboolean–Include vendor metadata in the response.
searchstring–Search by vendor name, invoice number, check number, or amount.
startDatestring–Start date filter (ISO 8601).
startingAfterstring–Invoice ID cursor for pagination.
status––Invoice status filter (e.g. DRAFT, NEW, APPROVED, SCHEDULED, PAID).
vendorId––Filter by vendor ID(s) or foreign ID(s).

No output schema declared.

No examples provided.

mercoa_find_transactions ~216

List/search payment transactions. Filter by entity, invoice, status, type and date. GET /transactions.

NameTypeReqDescription
endDatestring–CREATED_AT end date filter (ISO 8601).
entityGroupIdstring–Filter by entity group ID.
entityId––Filter by entity ID(s) or foreign ID(s).
invoiceId––Filter by invoice ID(s) or foreign ID(s).
limitinteger–Max transactions to return (1-100, default 10).
payerId––Filter by payer ID(s).
searchstring–Search by vendor name, invoice number, check number, or amount.
startDatestring–CREATED_AT start date filter (ISO 8601).
startingAfterstring–Transaction ID cursor for pagination.
status––Transaction status filter.
transactionId––Filter by transaction ID(s).
transactionType––Filter by transaction type.
vendorId––Filter by vendor ID(s).

No output schema declared.

No examples provided.

mercoa_get_entity ~48

Get a single entity by ID (or foreign ID). GET /entity/{entityId}.

NameTypeReqDescription
entityIdstringyesEntity ID (e.g. ent_...) or foreign ID.

No output schema declared.

No examples provided.

mercoa_get_entity_events ~103

Get the event/audit log for an entity. GET /entity/{entityId}/events.

NameTypeReqDescription
endDatestring–End date filter (ISO 8601).
entityIdstringyesEntity ID or foreign ID.
limitinteger–Max events to return (1-100).
startDatestring–Start date filter (ISO 8601).
startingAfterstring–Event ID cursor for pagination.

No output schema declared.

No examples provided.

mercoa_get_entity_invoice_metrics ~331

Get aggregate invoice metrics (totals/counts, grouped by currency) for an entity's payables/receivables — for AP/AR dashboards and aging. GET /entity/{entityId}/invoice-metrics.

NameTypeReqDescription
approverId––Filter by assigned approver user ID(s).
currency––Currency code(s) to filter on, e.g. USD.
dateTypestring–Date type to filter by (e.g. CREATED_AT, DUE_DATE).
endDatestring–End date filter (ISO 8601).
entityIdstringyesEntity ID or foreign ID.
excludePayablesboolean–Only return receivables (exclude payables).
excludeReceivablesboolean–Only return payables (exclude receivables).
groupBy––Additional grouping (e.g. by status).
invoiceId––Filter by invoice ID(s) or foreign ID(s).
payerId––Filter by payer ID(s).
returnByDatestring–Group metrics by date, e.g. CREATION_DATE or DUE_DATE.
returnByDateFrequencystring–Frequency for date grouping (e.g. DAILY, MONTHLY).
searchstring–Search by vendor name, invoice number, check number, or amount.
startDatestring–Start date filter (ISO 8601).
status––Invoice status filter (e.g. NEW, SCHEDULED, PAID).
vendorId––Filter by vendor ID(s).

No output schema declared.

No examples provided.

mercoa_get_invoice ~47

Get a single invoice (bill) by ID. GET /invoice/{invoiceId}.

NameTypeReqDescription
invoiceIdstringyesInvoice ID (e.g. in_...) or foreign ID.

No output schema declared.

No examples provided.

mercoa_get_invoice_events ~110

Get the event/audit log for an invoice (status changes, approvals, payments). GET /invoice/{invoiceId}/events.

NameTypeReqDescription
endDatestring–End date filter (ISO 8601).
invoiceIdstringyesInvoice ID or foreign ID.
limitinteger–Max events to return (1-100).
startDatestring–Start date filter (ISO 8601).
startingAfterstring–Event ID cursor for pagination.

No output schema declared.

No examples provided.

mercoa_get_organization ~32

Get the caller's Mercoa organization configuration (settings, payment methods enabled, etc.). GET /organization.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mercoa_get_payment_method ~66

Get a single payment method for an entity. GET /entity/{entityId}/paymentMethod/{paymentMethodId}.

NameTypeReqDescription
entityIdstringyesEntity ID or foreign ID.
paymentMethodIdstringyesPayment method ID (e.g. pm_...).

No output schema declared.

No examples provided.

mercoa_get_transaction ~35

Get a single payment transaction by ID. GET /transaction/{transactionId}.

NameTypeReqDescription
transactionIdstringyesTransaction ID.

No output schema declared.

No examples provided.

mercoa_list_entity_payment_methods ~73

List an entity's payment methods (bank accounts, cards, check, etc.). GET /entity/{entityId}/paymentMethods.

NameTypeReqDescription
entityIdstringyesEntity ID or foreign ID.
typestring–Filter by payment method type (e.g. bankAccount, card, check).

No output schema declared.

No examples provided.

mercoa_list_entity_users ~48

List the users belonging to an entity (approvers, admins, etc.). GET /entity/{entityId}/users.

NameTypeReqDescription
entityIdstringyesEntity ID or foreign ID.

No output schema declared.

No examples provided.

mercoa_update_invoice ~266

WRITE — updates an existing invoice/bill (all fields optional). Commonly used to advance status (e.g. DRAFT→NEW→SCHEDULED) or change amounts, dates, or payment methods. POST /invoice/{invoiceId}.

NameTypeReqDescription
amountnumber–Total invoice amount.
currencystring–Currency code, e.g. USD.
deductionDatestring–Scheduled payment/deduction date (ISO 8601).
dueDatestring–Due date (ISO 8601).
invoiceDatestring–Invoice date (ISO 8601).
invoiceIdstringyesInvoice ID to update.
invoiceNumberstring–Human-readable invoice number.
lineItemsarray–Replacement line items array.
metadataobject–Arbitrary key/value metadata.
noteToSelfstring–Internal note.
payerIdstring–Payer entity ID.
paymentDestinationIdstring–Payment method ID to pay to.
paymentSourceIdstring–Payment method ID to pay from.
statusstring–New invoice status, e.g. NEW, APPROVED, SCHEDULED.
vendorIdstring–Vendor entity ID.

No output schema declared.

No examples provided.

Install

How do I install the Mercoa MCP by usefulapi server?

Mercoa MCP by usefulapi is a hosted endpoint at https://mercoa.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 · mercoa.usefulapi.io

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

What is the Mercoa MCP by usefulapi server?

Mercoa MCP by usefulapi is listed in the public MCP registry as io.usefulapi/mercoa. Query and manage Mercoa AP/AR bill-pay: entities, invoices, transactions and payment methods. This page covers its hosted endpoint (https://mercoa.usefulapi.io/mcp).

Is the Mercoa MCP by usefulapi server safe to use?

Mercoa MCP by usefulapi scores 18 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 Mercoa MCP by usefulapi server expose?

Mercoa MCP by usefulapi exposes 17 tools: mercoa_find_entities, mercoa_get_entity, mercoa_get_entity_events, mercoa_get_entity_invoice_metrics, mercoa_list_entity_payment_methods, and 12 more. Their descriptions and schemas cost roughly 2,638 tokens of context every time the server is loaded.

Does the Mercoa MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Mercoa MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Mercoa MCP by usefulapi server still maintained?

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

What did VerifyMCP test on the Mercoa MCP by usefulapi server?

VerifyMCP ran 4 checks on Mercoa MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Mercoa MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.