Verfahrensdoku Gobd Check

io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.5Updated Oct 24, 2026

17 Regeln aus den GoBD und §147 AO gegen Ihre Markdown-Verfahrensdokumentation — im Editor, ohne Upl

The publisher's own server: check.tattoo: tattoo size and placement guide

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Checks Markdown procedure documentation against 17 GoBD and §147 AO rules locally, without uploading files.

What you can do
  • The manifest lists no tools and the server sends no instructions, so capabilities are known only from the short registry description.
  • According to that description, it evaluates a Markdown procedure document against 17 rules drawn from the GoBD and §147 AO.
  • The check is described as running in the editor without uploading the document.
When to use it
Worth considering if you keep German tax-relevant procedure documentation (Verfahrensdokumentation) in Markdown and want a quick local rule check before review or audit.
Requirements
Runs as a local process via npx from the npm package @readystack/verfahrensdoku-gobd-check; desktop only. No authentication, environment variables or headers are declared.
Before you install
The README describes unrelated VS Code themes, so documentation is thin and the actual behavior cannot be verified from the listing. A rule check is not a legal compliance guarantee; review results yourself before relying on them.

Installation

In SourceWeft

  1. Open Verfahrensdoku Gobd Check 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.

Other MCP clients

Follow the launch instructions in the repository.

README

readystack-themes

Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack

Source: README.md at commit ee1c884

Tools

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

Version history

1
  1. v1.0.5LatestSep 25, 2026

Score

40% 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
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Check integrations