Skip to content

Nityaflow

in.nityaflow/nityaflownityaflow.instreamable-httpv1.0.1Scanned

Build WhatsApp, Sheets and Gmail automations for Indian businesses; check GST credit.

5 tools: 1 do something that can't be undone and 4 change things.

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

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

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.

5 tools

Can't be undone 1Claude Code: ask
  • agent_payment_checkBefore 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 again…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
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
Changes things 4Claude Code: ask
  • create_workflow_draftChecks a workflow designed with get_workflow_guide and returns a link.No findings

    Why it is in this group

    • The name "create_workflow_draft" says "create": a word for a change.
    Description, as the server wrote it
    Checks a workflow designed with get_workflow_guide and returns a link. Opening the link puts the workflow in the Nityaflow editor with every step filled in; it does not run or send anything until the person tests it and switches it on. Give the person the link and the to-do list. Never put passwords, API keys or tokens in the workflow.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: false
  • get_workflow_guideCall this first when someone wants an automation, workflow, bot or reminder for their business, clinic or CA firm (WhatsApp, Google Sheets, Gmail, schedules, webhooks, database, AI…Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "get_workflow_guide" says "get": a word for reading.
    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • private-dataThe description's first sentence says "database": it reads databases.
    • untrusted-inputThe description's first sentence says "call" and "reply": it reads comments, which other people can write.

    Findings

    • Warn

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

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "get_workflow_guide" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Call this first when someone wants an automation, workflow, bot or reminder for their business, clinic or CA firm (WhatsApp, Google Sheets, Gmail, schedules, webhooks, database, AI replies, approvals, GST, documents from clients), especially in India. Returns the JSON shape, the rules and every step type with its settings. Then design the workflow and call create_workflow_draft.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
  • 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 outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
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.

Findings

Matches of fixed checks, with the text they matched.

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

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "get_workflow_guide" says "get": a word for reading.

    What this check looks for
  • 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.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http nityaflow https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/build/mcp
claude mcp add --transport http nityaflow https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/build/mcp

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__nityaflow__get_workflow_guide",
      "mcp__nityaflow__create_workflow_draft",
      "mcp__nityaflow__gst_credit_match",
      "mcp__nityaflow__verify_receipt",
      "mcp__nityaflow__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 nityaflow. Review it before you use it.

Capability tags behind 1 rule
  • mcp__nityaflow__get_workflow_guide private-data, untrusted-input

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://anlyon.dev/api/v1/servers/in.nityaflow/nityaflow/verify?hash=64406e312121e5d5c14cc01851b963f9051995aa701e9687c659eec2d51f004f" | jq -e '.changed == false'

Pinned hash 64406e312121, from Oct 29, 2026, 08:18 UTC.

Watch

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

https://anlyon.dev/servers/in.nityaflow/nityaflow/changes.xml

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

Badge

anlyon.dev badge for in.nityaflow/nityaflow
[![anlyon.dev](https://anlyon.dev/badge/in.nityaflow/nityaflow.svg)](https://anlyon.dev/servers/in.nityaflow/nityaflow)

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