# Nityaflow GST credit match (remote · aeerptxvpnbzqglebhyt.supabase.co)

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

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `aeerptxvpnbzqglebhyt.supabase.co`: 79/100 (this document), [markdown](https://verifymcp.io/servers/in-nityaflow-gst-credit-match/functions-v1-wf-mcp-gst.md), [page](https://verifymcp.io/servers/in-nityaflow-gst-credit-match/functions-v1-wf-mcp-gst)

## Channel facts

- Endpoint: `https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/wf/mcp-gst`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 777 tokens (~259/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Nityaflow GST credit match MCP server?

Nityaflow GST credit match is a hosted endpoint at https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/wf/mcp-gst, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http in-nityaflow-gst-credit-match 'https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/wf/mcp-gst'
```

### Cursor

```json
{
  "mcpServers": {
    "in-nityaflow-gst-credit-match": {
      "url": "https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/wf/mcp-gst"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "in-nityaflow-gst-credit-match": {
      "type": "http",
      "url": "https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/wf/mcp-gst"
    }
  }
}
```

### Codex

```toml
[mcp_servers.in-nityaflow-gst-credit-match]
url = "https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/wf/mcp-gst"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "in-nityaflow-gst-credit-match": {
      "type": "remote",
      "url": "https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/wf/mcp-gst",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add in-nityaflow-gst-credit-match --url 'https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/wf/mcp-gst' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  in-nityaflow-gst-credit-match:
    url: "https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/wf/mcp-gst"
```

### Netclaw

```json
{
  "McpServers": {
    "in-nityaflow-gst-credit-match": {
      "Transport": "http",
      "Url": "https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/wf/mcp-gst"
    }
  }
}
```

### Vellum

```bash
assistant mcp add in-nityaflow-gst-credit-match -t streamable-http -u 'https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/wf/mcp-gst'
```

### Other

```json
{
  "mcpServers": {
    "in-nityaflow-gst-credit-match": {
      "type": "http",
      "url": "https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/wf/mcp-gst"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 74, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “gst_credit_match” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 218 → 259
- [functional improvement] Stability: unverified → 0.03
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “check-agent-payment”
- [functional] New prompt “reconcile-gst”
- [functional] New tool “agent_payment_check”

### 2026-10-25 (score 71)

First indexed and scored.

## MCP tools (3)

### `gst_credit_match` (~305 tokens)

Match GSTR-2B with the purchase register

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.

Input parameters:

- `books` (array, required): Purchase register from the books: a list of invoices like {gstin, invoice, date, name, taxable, igst, cgst, sgst, cess, value}. Use the supplier's bill number, not the voucher number.
- `client` (string): Client or business name, for the receipt.
- `gstr2b` (required): GSTR-2B: either the JSON file downloaded from the GST portal, or a list of invoices like {gstin, invoice, date, taxable, igst, cgst, sgst, cess}.
- `period` (string): Return period, for example 2026-09.
- `tolerance` (number): Allowed difference in rupees before amounts count as different. Default 1.

### `verify_receipt` (~58 tokens)

Verify a Nityaflow receipt

Checks that a Nityaflow receipt (from gst_credit_match or a Nityaflow workflow) was not changed and was signed by Nityaflow.

Input parameters:

- `receipt` (object, required): The receipt object, exactly as it was given.

### `agent_payment_check` (~298 tokens)

Check an AI agent's payment against the mandate and the instruction

Before an AI agent pays, checks the proposed 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.

Input parameters:

- `action` (object, required): The payment the agent proposes: {merchant, vpa, lines: [{name, qty, unit, price}], fees, total}.
- `history` (array): Earlier payments under this mandate: [{at, total, vpa, status: paid}]. Used for the period limit and repeat check.
- `intent` (object, required): What the person asked for: {text, items: [{name, qty, unit}], budget, merchant}. Units: kg, g, l, ml, pc, pack, dozen.
- `mandate` (object, required): The permission: {authorised_by, purpose, per_payment, per_period, period (day, week, month or 90 days), merchants: [{name, vpa, category}], approve_above, valid_from, valid_to}.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/in-nityaflow-gst-credit-match/functions-v1-wf-mcp-gst#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 76
- 2026-10-28: 75
- 2026-10-27: 75
- 2026-10-26: 74
- 2026-10-25: 71

## Common questions

### What is the Nityaflow GST credit match MCP server?

Nityaflow GST credit match is an MCP server listed in the public MCP registry as in.nityaflow/gst-credit-match. India GST credit check: matches GSTR-2B with the purchase register and signs a receipt. This page covers its hosted endpoint (https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/wf/mcp-gst).

### Is the Nityaflow GST credit match MCP server safe to use?

Nityaflow GST credit match scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Nityaflow GST credit match MCP server expose?

Nityaflow GST credit match exposes 3 tools: gst_credit_match, verify_receipt, agent_payment_check. Their descriptions and schemas cost roughly 661 tokens of context every time the server is loaded.

### Does the Nityaflow GST credit match MCP server require authentication?

No. We connected to Nityaflow GST credit match without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Nityaflow GST credit match MCP server still maintained?

Nityaflow GST credit match is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Nityaflow GST credit match MCP server?

VerifyMCP ran 13 checks on Nityaflow GST credit match, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/wf/mcp-gst
- Website: https://app.nityaflow.in/ai.html
- Changelog RSS feed: https://verifymcp.io/servers/in-nityaflow-gst-credit-match/functions-v1-wf-mcp-gst.xml
- Changelog JSON feed: https://verifymcp.io/servers/in-nityaflow-gst-credit-match/functions-v1-wf-mcp-gst/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/in-nityaflow-gst-credit-match/functions-v1-wf-mcp-gst.json
- HTML version of this page: https://verifymcp.io/servers/in-nityaflow-gst-credit-match/functions-v1-wf-mcp-gst