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.

InvoiceForge

REMOTE · INVOICEFORGE.AGENTTOOLWORKS.COM

Generate, validate and read EN 16931 and Peppol BIS 3.0 e-invoices, in UBL and CII.

+1 this week 85 Trust /100

Last scanned (5 hours ago)

Scores higher than 91% 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 Security71
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 396 tokens (~79/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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.

  • 31 Oct 26 0
    • Stability: 0.97 → pass security
  • 30 Oct 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.

  • 28 Oct 26 +1

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

  • 26 Oct 26 +1

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

  • 24 Oct 26 +1

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

  • 22 Oct 26 +1

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

  • 20 Oct 26 +1

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

  • 18 Oct 26 +1

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

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://invoiceforge.agenttoolworks.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agenttoolworks.com CN=WE1,O=Google Trust Services,C=US 13 Oct 2026 11 Jan 2027 ECDSA 256 ECDSA-SHA256 11b17b1acfade00a13d35376ddad132a
SANs: agenttoolworks.com, invoiceforge.agenttoolworks.com, *.invoiceforge.agenttoolworks.com
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 invoiceforge.agenttoolworks.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
agenttoolworks.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

Protected resource metadata

Retrieved No
Problem no_resource_metadata

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://invoiceforge.agenttoolworks.com/mcp Verified 200
http (plaintext) http://invoiceforge.agenttoolworks.com/mcp Inconclusive 405
MCP tools · 5 exposed · ~396 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
describe_coverage ~65

Returns the exact EN 16931 rules this server checks, the syntaxes it can produce and read, and the things it deliberately does not do, such as transmitting invoices over Peppol or acting as a French accredited platform. Light read: costs 0.2 credit.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

extract_invoice ~79

Reads an incoming UBL or CII (Factur-X) invoice XML and returns the data as structured JSON, listing any field the document did not contain rather than guessing it. Use it to ingest supplier invoices before booking them. Costs 1 credit.

NameTypeReqDescription
xmlstringyesThe invoice XML, UBL 2.1 or CII

No output schema declared.

No examples provided.

generate_invoice ~113

Turns invoice data into a compliant UBL 2.1 XML document following the EN 16931 semantic model, with totals and the VAT breakdown computed for you. Choose the plain EN 16931 profile or the Peppol BIS Billing 3.0 customization. The document is validated before it is returned, so you never get back XML that would be rejected. Costs 1 credit.

NameTypeReqDescription
invoiceobjectyesThe invoice to produce
profilestring–Which specification identifier to stamp on the document

No output schema declared.

No examples provided.

get_usage ~30

Returns your current plan, remaining credit balance and call volume over the last 30 days. Free to call.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

validate_invoice ~109

Checks invoice data against a documented subset of the EN 16931 business rules: mandatory fields, code lists, VAT category consistency and the arithmetic that most often gets invoices rejected. Accepts incomplete or malformed data on purpose, since that is what you want checked, and answers with each violation, its rule identifier and its business term, plus exactly which rules were checked. It never claims full compliance with the norm. Costs 1 credit.

NameTypeReqDescription
invoiceobjectyesThe invoice to check, however incomplete

No output schema declared.

No examples provided.

Install

How do I install the InvoiceForge MCP server?

InvoiceForge is a hosted endpoint at https://invoiceforge.agenttoolworks.com/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 · invoiceforge.agenttoolworks.com

# add to Claude Code
claude mcp add --transport http com-agenttoolworks-invoiceforge 'https://invoiceforge.agenttoolworks.com/mcp'
Common questions

What is the InvoiceForge MCP server?

InvoiceForge is an MCP server listed in the public MCP registry as com.agenttoolworks/invoiceforge. Generate, validate and read EN 16931 and Peppol BIS 3.0 e-invoices, in UBL and CII. This page covers its hosted endpoint (https://invoiceforge.agenttoolworks.com/mcp).

Is the InvoiceForge MCP server safe to use?

InvoiceForge scores 85 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 InvoiceForge MCP server expose?

InvoiceForge exposes 5 tools: generate_invoice, validate_invoice, extract_invoice, describe_coverage, get_usage. Their descriptions and schemas cost roughly 396 tokens of context every time the server is loaded.

Does the InvoiceForge MCP server require authentication?

Yes. InvoiceForge 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 InvoiceForge MCP server still maintained?

InvoiceForge 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.