GST Validator MCP Server

Validate Indian GSTINs locally (Verhoeff), extract PAN, identify issuing state. The gst validator mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.

What it actually does

Hosted MCP server for structural validation of Indian GSTINs (15-character Goods & Services Tax Identification Numbers). Verifies length, character set, state code, embedded PAN format, and the GSTN mod-36 (Verhoeff) check digit. Extracts the embedded PAN and resolves the state from the TIN prefix. For Indian invoicing, KYC, and procurement LLMs.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• validate_gstin — gstin
• extract_pan — gstin
• state_from_gstin — gstin_or_prefix

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the gst validator mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. GST Validator's toolset — validate_gstin, extract_pan, state_from_gstin — is a fair guide to whether it matches your workflow. It is maintained by guptaprakhariitr; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.