Skip to content

Nityaflow GST credit match MCP server

in.nityaflow/gst-credit-matchnityaflow.instreamable-httpv1.0.1Scanned

India GST credit check: matches GSTR-2B with the purchase register and signs a receipt.

3 tools: 1 do something that can't be undone and 2 change things.

Tools: 0 delete, 1 irreversible, 2 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Nityaflow GST credit match MCP server can do

The Nityaflow GST credit match MCP server is published by nityaflow.in, a domain the MCP Registry verified. It has 3 tools. It can do things that cannot be undone, such as sending, paying or publishing (agent_payment_check) and create or change data (2 tools: gst_credit_match and verify_receipt), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Can't be undone 1Claude Code: ask
  • agent_payment_checkWhen the user asks for a payment check, checks a proposed AI-agent payment against the person's mandate (who allowed it, limits per payment and per period, allowed shops and UPI ID…1 finding

    Why it is in this group

    • The name "agent_payment_check" says "payment": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "agent_payment_check" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "agent_payment_check" says "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    When the user asks for a payment check, checks a proposed AI-agent payment against the person's mandate (who allowed it, limits per payment and per period, allowed shops and UPI IDs, end date) and against what the person actually asked for (items, quantities, budget, shop). It works the total out again from the cart lines, and flags lookalike payees, extra items, too much quantity, going over a limit and repeat payments. Returns every check and a receipt signed by Nityaflow. It never pays, holds or moves money: a licensed bank or payment app does that, only after a person approves.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
Changes things 2Claude Code: ask
  • gst_credit_matchIndia GST input tax credit check.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    India GST input tax credit check. Matches the supplier invoices in GSTR-2B against the purchase register from the books (Tally, Zoho Books, Busy, QuickBooks or any list) and sorts every invoice into: matched, amount mismatch, entered twice (duplicate bills), possible match (invoice number or GSTIN written differently), in books but not in GSTR-2B (credit at risk), in GSTR-2B but not in books. A separate checker re-derives the totals, and the result comes with a receipt signed by Nityaflow. Invoices are processed in memory and not stored. It never files or accepts anything on the GST portal.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
  • verify_receiptChecks that a Nityaflow receipt (from gst_credit_match or a Nityaflow workflow) was not changed and was signed by Nityaflow.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Checks that a Nityaflow receipt (from gst_credit_match or a Nityaflow workflow) was not changed and was signed by Nityaflow.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:23 UTC, unchanged since Oct 25, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/wf/mcp-gst: tools/list returned 3 tools to an anonymous client, including agent_payment_check (irreversible), gst_credit_match (write), verify_receipt (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "agent_payment_check" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "agent_payment_check" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http gst-credit-match https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/wf/mcp-gst
claude mcp add --transport http gst-credit-match https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/wf/mcp-gst

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__gst-credit-match__gst_credit_match",
      "mcp__gst-credit-match__verify_receipt",
      "mcp__gst-credit-match__agent_payment_check"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as gst-credit-match. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/in.nityaflow/gst-credit-match/verify?hash=31ffe50800d744e4c7eaa50d9e4289f3fd9370269d04de3954188f234e64ce41" | jq -e '.changed == false'

Pinned hash 31ffe50800d7, from Nov 10, 2026, 17:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/in.nityaflow/gst-credit-match/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for in.nityaflow/gst-credit-match
[![Anlyon Radar](https://radar.anlyon.com/badge/in.nityaflow/gst-credit-match.svg)](https://radar.anlyon.com/servers/in.nityaflow/gst-credit-match)

Source: MCP Registry. Synced Oct 29, 2026, 08:17 UTC.

Nityaflow GST credit match MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Nityaflow GST credit match MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Nityaflow GST credit match MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Nityaflow GST credit match MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: agent_payment_check.

What tools does the Nityaflow GST credit match MCP server have?

3 tools: 1 irreversible, 2 write. agent_payment_check, gst_credit_match and verify_receipt.

Does the Nityaflow GST credit match MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Nityaflow GST credit match MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Nityaflow GST credit match MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.