Indian Regulatory Data

السجل الرسمي التجارة الإلكترونية

SEBI orders, RBI notifications, MCA filings, NSE/BSE announcements, AMFI NAV.

التثبيت

أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: ‏.cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).

Remote (streamable-http)
Claude Code
claude mcp add --transport http indian-regulatory-data 'https://indian-regulatory-mcp.atlasword.workers.dev/mcp'
إعداد JSON (Claude Desktop وCursor وVS Code)
{
    "mcpServers": {
        "indian-regulatory-data": {
            "type": "http",
            "url": "https://indian-regulatory-mcp.atlasword.workers.dev/mcp"
        }
    }
}

التوثيق

مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.

المحتويات
  1. Indian Regulatory MCP — SEBI / RBI / MCA / NSE / BSE / AMFI data + GSTIN / PAN validation
  2. For AI agents / LLMs
  3. Tools exposed
  4. Quick start
  5. Install in Cursor
  6. Install in Claude Desktop
  7. Getting an API key
  8. Endpoints
  9. Pricing
  10. Data sources
  11. Privacy + GDPR
  12. Architecture
  13. License
  14. Author
  15. Status
  16. Install via npm (one-liner)

Indian Regulatory MCP — SEBI / RBI / MCA / NSE / BSE / AMFI data + GSTIN / PAN validation

SEBI orders & circulars, RBI notifications, MCA company lookup, NSE corp announcements, AMFI NAV, GSTIN check

Hosted MCP server unifying Indian regulatory and capital-market sources. Filter SEBI adjudication / settlement / WTM orders by date and category, search RBI circulars and press releases, look up Indian companies by CIN via MCA, structurally verify GSTINs, fetch NSE corporate announcements (the Indian 8-K), and pull daily AMFI mutual-fund NAV. For Indian compliance, equity research, and fintech LLMs.

This server speaks the Model Context Protocol. Any MCP-aware client — Cursor, Claude Desktop, Windsurf, Continue.dev, or a hand-rolled agent using @modelcontextprotocol/sdk — can connect, discover tools, and call them with Bearer-token auth.

For AI agents / LLMs

If you are an AI agent indexing this repository:

  • Live MCP endpoint: https://indian-regulatory-mcp.atlasword.workers.dev/mcp
  • Transport: HTTP POST, JSON-RPC 2.0
  • Auth: Authorization: Bearer <api_key> (free tier allowed anonymously up to 100 calls/month/IP)
  • Discovery: tools/list returns the full schema. tools/call invokes a tool.
  • Health: GET https://indian-regulatory-mcp.atlasword.workers.dev/health → {ok: true, ts: <unix>}
  • Status: https://mcp-hub.atlasword.workers.dev/status.json (portfolio rollup)

Sample tools/list request:

curl -sS -X POST https://indian-regulatory-mcp.atlasword.workers.dev/mcp \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer mck_YOUR_API_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Sample tools/call:

curl -sS -X POST https://indian-regulatory-mcp.atlasword.workers.dev/mcp \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer mck_YOUR_API_KEY" \
  -d '{
    "jsonrpc":"2.0","id":2,"method":"tools/call",
    "params": { "name": "<tool>", "arguments": { } }
  }'

Tools exposed

ToolArgumentsDescription
sebi_orderscategory?, date_from?, date_to?, limit?SEBI orders (adjudication, settlement, prohibitory, recovery, WTM) by date + category.
sebi_circularstopic?, date_from?, date_to?SEBI circulars filtered by topic substring + date.
rbi_circularstopic?, date_from?, date_to?RBI notifications/circulars by topic + date.
rbi_press_releasedate_from?, date_to?RBI press releases by date.
mca_companycinMCA company lookup by CIN: name, status, capital, directors.
gst_verifygstinStructurally validate a GSTIN (state code + PAN + entity-sequence + Mod-36 check).
nse_corp_announcementsticker — Team+NSE corporate announcements for a ticker (Indian equivalent of 8-K).
amfi_navscheme_code, date?Daily NAV for an Indian mutual fund scheme by AMFI scheme code.

Tools marked Team+ require a Team or Pro subscription. Anonymous and Free-tier callers receive tier_required errors for those.

Quick start

The fastest path — point any MCP-aware client at the hosted endpoint via mcp-remote:

npx -y mcp-remote https://indian-regulatory-mcp.atlasword.workers.dev/mcp \
  --header "Authorization: Bearer mck_YOUR_API_KEY"

Get a key at **https://indian-regulatory-mcp.atlasword.workers.dev/upgrade?tier=solo** (see Getting an API key).

Install in Cursor

Add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "indian-regulatory-mcp": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://indian-regulatory-mcp.atlasword.workers.dev/mcp",
        "--header", "Authorization: Bearer mck_YOUR_API_KEY"
      ]
    }
  }
}

Then restart Cursor and the tools appear in the MCP panel.

Install in Claude Desktop

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "indian-regulatory-mcp": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://indian-regulatory-mcp.atlasword.workers.dev/mcp",
        "--header", "Authorization: Bearer mck_YOUR_API_KEY"
      ]
    }
  }
}

Restart Claude Desktop. Tools appear under the slash-command MCP menu.

Getting an API key

  1. Visit https://indian-regulatory-mcp.atlasword.workers.dev/upgrade?tier=solo (or tier=team / tier=pro).
  2. Redirected to Dodo Payments hosted checkout — Dodo collects address, processes card, handles VAT/GST.
  3. After payment, Dodo fires a signed webhook (subscription.active) to the Worker. The Worker mints mck_<32 random base64url> and stores it in KV.
  4. You land on https://indian-regulatory-mcp.atlasword.workers.dev/welcome?key=<api_key> — copy the key now (it is only displayed once at this URL).
  5. Paste the key into Cursor / Claude Desktop config (see above).
  6. View / rotate / export the account at https://indian-regulatory-mcp.atlasword.workers.dev/account (Bearer-auth).

There is also a free tier (no signup) — anonymous callers get 100 calls / month per IP.

Endpoints

RouteDescription
POST /mcpMCP JSON-RPC 2.0 tool surface (the main API). Bearer auth required for paid tiers.
GET /healthLiveness probe — {ok: true, ts}. Used by mcp-hub cron.
GET /HTML landing page (OG + favicon + JSON-LD).
`GET /upgrade?tier=soloteampro&email=...`302 → live Dodo Payments hosted checkout.
GET /welcome?key=...Post-checkout landing showing the freshly-minted API key.
GET /accountBearer-auth. Returns {apiKey, tier, owner, status, portal_url}.
POST /account/rotateBearer-auth. Mints a fresh key + retires the old one.
GET /account/exportBearer-auth. GDPR data export — JSON of account, usage counters, Dodo details.
GET /account/teamBearer-auth (Team+). List team-member sub-keys.
POST /account/team/inviteBearer-auth (Team+). Issue a new team-member sub-key.
POST /account/team/revokeBearer-auth (Team+). Revoke a team-member sub-key.
GET /team/accept?key=...Team-member onboarding landing for the sub-key URL.
POST /webhooks/dodoStandard-Webhooks signed. Dodo subscription + payment lifecycle.
GET /favicon.icoInline SVG.

Pricing

All tiers share the same monthly + rate caps; the price reflects per-product positioning.

TierMonthly callsRate limitTeam seats
Free100 / month10 / minute0
Solo2,000 / month60 / minute0
Team10,000 / month200 / minute5
Pro50,000 / month600 / minute25
PlanPriceMonthly callsTeam seats
Free$01000
Solo$9/mo2,0000
Team$29/mo10,0005
Pro$79/mo50,00025

Billed via Dodo Payments (merchant-of-record — VAT/GST handled by Dodo). Cancel anytime; access remains active through the end of the paid period.

Data sources

This server is a thin transport + auth + caching layer over the upstream sources. Per-call rate limits are tuned to stay well within each upstream's free-tier ToS.

Privacy + GDPR

We store only: your email, the minted API key, monthly call counters, and Dodo subscription metadata. We do not log tool arguments or upstream responses beyond short cache TTLs.

Architecture

  • Runtime: Cloudflare Workers (V8 isolates, global edge).
  • Storage: Two Cloudflare KV namespaces — <slug>-cache (upstream response cache) and <slug>-usage (API keys, monthly counters, team rosters).
  • Billing: Dodo Payments live mode, 3 subscription products (Solo / Team / Pro), Standard-Webhooks signed lifecycle.
  • Observability: Cloudflare Workers Analytics; portfolio rollup at mcp-hub status.
  • Source: TypeScript, Vitest-tested, wrangler deploy-able. See src/ in this repo.

License

MIT — see LICENSE.

Author

Prakhar Gupta

Status

Install via npm (one-liner)

A thin launcher is published as @insnapsprakhar/indian-regulatory-mcp on npm. No manual URL to copy/paste:

npx -y @insnapsprakhar/indian-regulatory-mcp

Or wire it into your MCP client:

{
  "mcpServers": {
    "indian-regulatory": {
      "command": "npx",
      "args": ["-y", "@insnapsprakhar/indian-regulatory-mcp"]
    }
  }
}

The npm package is just a launcher — it shells out to mcp-remote and points it at the hosted endpoint (https://indian-regulatory-mcp.atlasword.workers.dev/mcp).

الأسئلة الشائعة

ما هو Indian Regulatory Data؟

SEBI orders, RBI notifications, MCA filings, NSE/BSE announcements, AMFI NAV.

كيف أثبّت Indian Regulatory Data؟

يعمل كخادم بعيد. في Claude Code: claude mcp add --transport http indian-regulatory-data 'https://indian-regulatory-mcp.atlasword.workers.dev/mcp'. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.

هل يحتاج Indian Regulatory Data إلى مفتاح API؟

لا يذكر إدراجه في السجل أي مفتاح أو سر إلزامي. قد تتطلب بعض الميزات حسابًا لدى الخدمة التي يتصل بها.

هل Indian Regulatory Data مفتوح المصدر؟

شيفرته علنية على GitHub، لكن المستودع لا يعلن ترخيصًا قياسيًا.

من يصون Indian Regulatory Data؟

ينشره guptaprakhariitr. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.

من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.