Indian Regulatory Data
REMOTE · INDIAN-REGULATORY-MCP.ATLASWORD.WORKERS.DEV · SCANNED SEP 20
SEBI orders, RBI notifications, MCA filings, NSE/BSE announcements, AMFI NAV.
Available components
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 500. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Indian Regulatory Data MCP server?
Indian Regulatory Data is a hosted endpoint at https://indian-regulatory-mcp.atlasword.workers.dev/mcp, 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.
remote · indian-regulatory-mcp.atlasword.workers.dev
claude mcp add --transport http guptaprakhariitr-indian-regulatory-mcp 'https://indian-regulatory-mcp.atlasword.workers.dev/mcp'
{
"mcpServers": {
"guptaprakhariitr-indian-regulatory-mcp": {
"url": "https://indian-regulatory-mcp.atlasword.workers.dev/mcp"
}
}
} {
"servers": {
"guptaprakhariitr-indian-regulatory-mcp": {
"type": "http",
"url": "https://indian-regulatory-mcp.atlasword.workers.dev/mcp"
}
}
} [mcp_servers.guptaprakhariitr-indian-regulatory-mcp] url = "https://indian-regulatory-mcp.atlasword.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"guptaprakhariitr-indian-regulatory-mcp": {
"type": "remote",
"url": "https://indian-regulatory-mcp.atlasword.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add guptaprakhariitr-indian-regulatory-mcp --url 'https://indian-regulatory-mcp.atlasword.workers.dev/mcp' --transport streamable-http
mcp_servers:
guptaprakhariitr-indian-regulatory-mcp:
url: "https://indian-regulatory-mcp.atlasword.workers.dev/mcp" {
"McpServers": {
"guptaprakhariitr-indian-regulatory-mcp": {
"Transport": "http",
"Url": "https://indian-regulatory-mcp.atlasword.workers.dev/mcp"
}
}
} assistant mcp add guptaprakhariitr-indian-regulatory-mcp -t streamable-http -u 'https://indian-regulatory-mcp.atlasword.workers.dev/mcp'
{
"mcpServers": {
"guptaprakhariitr-indian-regulatory-mcp": {
"type": "http",
"url": "https://indian-regulatory-mcp.atlasword.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Sept 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 15 Sept 26 +49
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 11 Sept 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 6 Sept 26 +49
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 5 Sept 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Aug 26 0
- Stability: 0.97 → pass security
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://indian-regulatory-mcp.atlasword.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=atlasword.workers.dev | CN=WE1,O=Google Trust Services,C=US | 8 Aug 2026 | 6 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 72d2f5e4594f5fb3135c7c7ae3e41553 |
| SANs: atlasword.workers.dev, *.atlasword.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of indian-regulatory-mcp.atlasword.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 500 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://indian-regulatory-mcp.atlasword.workers.dev/mcp | HTTP error | 500 | |
| http (plaintext) | http://indian-regulatory-mcp.atlasword.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
amfi_nav ~38
Daily NAV for an Indian mutual fund scheme by AMFI scheme code.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | – |
| scheme_code | string | yes | – |
No output schema declared.
No examples provided.
gst_verify ~66
Validate a GSTIN structurally (state code + PAN + entity-sequence + Mod-36 check digit). Note: this checks *structure*, not whether the GSTIN is currently active — for active-status, an authorized GST API call is required.
| Name | Type | Req | Description |
|---|---|---|---|
| gstin | string | yes | – |
No output schema declared.
No examples provided.
rbi_circulars ~51
RBI notifications/circulars by topic and date.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | – |
| date_to | string | – | – |
| limit | integer | – | – |
| topic | string | – | – |
No output schema declared.
No examples provided.
rbi_press_release ~39
RBI press releases by date.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | – |
| date_to | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
sebi_circulars ~50
SEBI circulars by topic substring and date.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | – |
| date_to | string | – | – |
| limit | integer | – | – |
| topic | string | – | – |
No output schema declared.
No examples provided.
sebi_orders ~111
SEBI orders (adjudication, settlement, prohibitory, recovery, WTM, etc.) filtered by date and category. Returns title + date + URL to the official order PDF.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | adjudication / settlement / prohibitory / wtm / recovery / informal_guidance / consent. Case-insensitive (fix in 0.1.1). |
| date_from | string | – | ISO YYYY-MM-DD. |
| date_to | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
What is the Indian Regulatory Data MCP server?
Indian Regulatory Data is an MCP server listed in the public MCP registry as io.github.guptaprakhariitr/indian-regulatory-mcp. SEBI orders, RBI notifications, MCA filings, NSE/BSE announcements, AMFI NAV. This page covers its hosted endpoint (https://indian-regulatory-mcp.atlasword.workers.dev/mcp).
Is the Indian Regulatory Data MCP server safe to use?
Indian Regulatory Data scores 18 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 Indian Regulatory Data MCP server expose?
Indian Regulatory Data exposes 6 tools: sebi_orders, sebi_circulars, rbi_circulars, rbi_press_release, gst_verify, amfi_nav. Their descriptions and schemas cost roughly 355 tokens of context every time the server is loaded.
Does the Indian Regulatory Data MCP server require authentication?
No. We connected to Indian Regulatory Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Indian Regulatory Data MCP server still maintained?
Indian Regulatory Data is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.