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.

Conecto Invoices

REMOTE · API.CONECTO.CHAT

Quotes and invoices numbered without gaps, sent as PDFs, paid online. Pay per action.

Available components

61 Trust /100

Last scanned (5 hours ago)

Scores higher than 43% 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 Security57
Transport & Reachability100
Schema Quality & AI Usability56
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 10833 tokens (~208/item across 52 items; 52 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 Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 70% 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
  • All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 53 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 3 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 2 Nov 26 60

    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 5 Nov 2026 · Probed https://api.conecto.chat/mcp/invoices

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.conecto.chat CN=WR3,O=Google Trust Services,C=US 6 Oct 2026 4 Jan 2027 RSA 2048 SHA256-RSA e65363629d99e1e21050aed0a4a3b3ce
SANs: api.conecto.chat
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.conecto.chat. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
chat. present 33026 8 Verified
conecto.chat. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
x-frame-options DENY
referrer-policy same-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.conecto.chat/mcp/invoices Verified 200
http (plaintext) http://api.conecto.chat/mcp/invoices HTTPS enforced 302 https://api.conecto.chat/mcp/invoices
MCP tools · 52 exposed · ~10,726 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
invoices_use_credit ~236

Put a customer's credit (a prepayment or an overpayment) on one of their sent invoices, like Xero's allocate credit: invoice_id, and amount (default all it can: what is left on the credit or the invoice, the smaller); the invoice records it as a payment with method credit, and its share of the credit's VAT comes back off. Or refund: true pays what is left (or amount) back to the customer, with date and method; or void: true takes back a prepayment recorded by mistake while none of it is used. Same customer and currency only. Costs $0.01 per call; nothing if it fails.

NameTypeReqDescription
amountnumber|string––
creditstringyesThe credit's number, like "CR-0001" (invoices_list_credits).
datestring–YYYY-MM-DD
invoice_idstring–The invoice_id invoices_create returned (quotes and credit notes have one too).
methodstring––
referencestring––
refundboolean––
voidboolean––

No output schema declared.

No examples provided.

invoices_void ~168

Void a document. A sent one keeps its number (numbers stay gapless) but can no longer be paid, accepted or viewed; a draft is simply discarded. Refused while payments are recorded on it, on an invoice with credit notes and on a credit note (correct those with another credit note or a new invoice), and on an invoice that may be in the customer's hands (emailed, opened, or its PDF downloaded through a link): that one is cancelled with a credit note for all of it, as the law asks. An invoice posted to the books is reversed there. Costs $0.01 per call; nothing if it fails.

NameTypeReqDescription
invoice_idstringyesThe invoice_id invoices_create returned (quotes and credit notes have one too).
reasonstring––

No output schema declared.

No examples provided.

Install

How do I install the Conecto Invoices MCP server?

Conecto Invoices is a hosted endpoint at https://api.conecto.chat/mcp/invoices, 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 · api.conecto.chat

# add to Claude Code
claude mcp add --transport http chat-conecto-invoices 'https://api.conecto.chat/mcp/invoices'
Common questions

What is the Conecto Invoices MCP server?

Conecto Invoices is an MCP server listed in the public MCP registry as chat.conecto/invoices. Quotes and invoices numbered without gaps, sent as PDFs, paid online. Pay per action. This page covers its hosted endpoint (https://api.conecto.chat/mcp/invoices).

Is the Conecto Invoices MCP server safe to use?

Conecto Invoices scores 61 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 Conecto Invoices MCP server expose?

Conecto Invoices exposes 52 tools: invoices_connect_stripe, invoices_set_profile, invoices_get_profile, invoices_create, invoices_set_expected_date, and 47 more. Their descriptions and schemas cost roughly 10,726 tokens of context every time the server is loaded.

Does the Conecto Invoices MCP server require authentication?

No. We connected to Conecto Invoices without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Conecto Invoices MCP server still maintained?

Conecto Invoices 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.