Hmrc Fraud Prevention Header Lint

io.github.jmshinhwaPublished by GitHub account jmshinhwav0.1.2Updated Oct 24, 2026

Finds the Gov-Client and Gov-Vendor header mistakes HMRC rejects, in your editor, offline, before yo

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Local stdio MCP server that lints HMRC Gov-Client and Gov-Vendor fraud prevention headers offline, flagging mistakes HMRC rejects.

What you can do
  • Check Gov-Client and Gov-Vendor fraud prevention headers for errors HMRC would reject.
  • Run the lint offline, without sending header data to a remote service.
  • Surface header problems inside the editor before submission.
  • No individual tools are listed in the manifest, so exact operations are not documented.
When to use it
Useful when building or testing an HMRC Making Tax Digital integration and you want to catch fraud prevention header mistakes early, in the editor, rather than after an HMRC rejection.
Requirements
Runs as a local process over stdio, launched with npx from the npm package @readystack/hmrc-fraud-prevention-header-lint, so Node.js and npx are needed. Desktop only; no authentication, environment variables or headers are declared.
Before you install
The README content does not match the described purpose, so documentation is thin; verify what the package actually does before installing. It is a local npm package run via npx, so review the package source and pin a version if you need reproducibility.

Installation

In SourceWeft

  1. Open Hmrc Fraud Prevention Header Lint 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

2
  1. v0.1.2LatestSep 19, 2026
  2. v0.1.1Sep 18, 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.