Invoice

com.yaktoolPublished by yaktool.comv0.2.0Updated Oct 24, 2026

Check invoice mandatory fields, validate a draft before issuing, and look up EN 16931 code lists.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Local MCP server that lets an assistant check invoice mandatory fields, validate a draft before issuing, and look up EN 16931 code lists.

What you can do
  • Check mandatory fields on an invoice and flag what is missing.
  • Validate a draft invoice before it is issued.
  • Look up EN 16931 code lists used in electronic invoicing.
When to use it
Useful when preparing or reviewing electronic invoices, especially EN 16931 / e-invoicing drafts, and you want an assistant to catch missing mandatory fields or wrong code-list values before issuing.
Requirements
Runs as a local process on the user's machine via the npm package yaktool-invoice-mcp over stdio; desktop only. No authentication, environment variables or headers are declared.
Before you install
The manifest lists no tools, so the exact operations and whether anything is written or sent are not documented here. Validation results should be reviewed before an invoice is issued.

Installation

In SourceWeft

  1. Open Invoice in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

15% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.