# Indian Cyber Regulation Register (BitScore) (remote · www.bitscore.in)

Indian cyber regulation register and incident-reporting deadlines (India, US, EU), read at source.

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

## Components

- remote · `www.bitscore.in`: 77/100 (this document), [markdown](https://verifymcp.io/servers/nimitt-in-india-cyber-regulations/www.md), [page](https://verifymcp.io/servers/nimitt-in-india-cyber-regulations/www)

## Channel facts

- Endpoint: `https://www.bitscore.in/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-10-07.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1950 tokens (~243/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Indian Cyber Regulation Register (BitScore) MCP server?

Indian Cyber Regulation Register (BitScore) is a hosted endpoint at https://www.bitscore.in/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.

### Claude

```bash
claude mcp add --transport http nimitt-in-india-cyber-regulations 'https://www.bitscore.in/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "nimitt-in-india-cyber-regulations": {
      "url": "https://www.bitscore.in/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nimitt-in-india-cyber-regulations": {
      "type": "http",
      "url": "https://www.bitscore.in/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.nimitt-in-india-cyber-regulations]
url = "https://www.bitscore.in/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nimitt-in-india-cyber-regulations": {
      "type": "remote",
      "url": "https://www.bitscore.in/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nimitt-in-india-cyber-regulations --url 'https://www.bitscore.in/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nimitt-in-india-cyber-regulations:
    url: "https://www.bitscore.in/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "nimitt-in-india-cyber-regulations": {
      "Transport": "http",
      "Url": "https://www.bitscore.in/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add nimitt-in-india-cyber-regulations -t streamable-http -u 'https://www.bitscore.in/mcp'
```

### Other

```json
{
  "mcpServers": {
    "nimitt-in-india-cyber-regulations": {
      "type": "http",
      "url": "https://www.bitscore.in/mcp"
    }
  }
}
```

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-10-07 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 30. That category is still filling its 30-day observation window: 7 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-10-04 (score 76, +1)

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

### 2026-10-02 (score 75, +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-09-30 (score 74, +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-09-29 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-28 (score 73)

First indexed and scored.

## MCP tools (8)

### `search_instruments` (~164 tokens)

Search the Indian cyber regulation register

Search every cyber and data-protection instrument binding Indian regulated entities (RBI, SEBI, IRDAI, IFSCA, CERT-In, MeitY/DPDP): reference number, issue date, status, who it binds and the deadlines it sets. Filter by free text, issuer or status. Returns summaries; use get_instrument for one entry in full.

Input parameters:

- `issuer` (string): Only instruments from this issuer.
- `limit` (integer): Maximum results, 1–50. Default 20.
- `query` (string): Words to match against the name, reference number and who it binds, e.g. "outsourcing", "NBFC", "2024/113".
- `status` (string): Only instruments with this status.

### `get_instrument` (~92 tokens)

Get one instrument from the register

Full register entry for one instrument by its id (from search_instruments): formal name, reference, issue date, status, who it binds, every dated deadline it sets, the regulator’s own URL and the date it was last re-read there.

Input parameters:

- `id` (string, required): Register id, e.g. "rbi-cyber-2026-nbfc" or "sebi-cscrf".

### `find_applicable_regulations` (~144 tokens)

Which Indian cyber regulations apply to an entity

Given an Indian entity class, whether it is listed and whether it handles personal data, returns the cyber and data-protection instruments that bind it, why each applies, a caution where one is commonly misapplied, and its next dated deadline. RBI classes each map to their own 2026 Directions; RRBs and LABs have none, and the result says so.

Input parameters:

- `entity_class` (string, required): The entity’s class.
- `handles_personal_data` (boolean, required): Processes digital personal data of individuals in India (brings DPDP).
- `listed` (boolean, required): Listed on an Indian stock exchange (brings SEBI LODR disclosure).

### `india_incident_reporting_deadlines` (~315 tokens)

Indian cyber incident reporting deadlines

Every incident-reporting clock an Indian entity owes — CERT-In six hours, the sectoral regulator (RBI, SEBI, IRDAI, IFSCA), SEBI LODR, NCIIPC, DPDP — each with its trigger, recipient, channel and source clause. Give noticed_at to get wall-clock IST due times. Clocks run in parallel; none discharges another.

Input parameters:

- `ifsca_exempt` (boolean): IFSCA RE inside either exemption tier of the 2025 Guidelines.
- `ifsca_mii` (boolean): IFSC market infrastructure institution (stock exchange, clearing corporation, depository).
- `listed` (boolean, required): Listed on an Indian stock exchange.
- `nbfc_layer` (string): For an NBFC: its layer under Scale-Based Regulation.
- `noticed_at` (string): Optional. When the incident was noticed or brought to notice, ISO 8601 with offset, e.g. 2026-10-01T14:30:00+05:30.
- `personal_data` (boolean, required): The incident involves digital personal data.
- `protected_system` (boolean, required): Operates a notified Protected System (brings NCIIPC).
- `rbi_class` (string): Required when sector is "rbi".
- `sebi_broker_or_dp` (boolean): SEBI stock broker or depository participant (adds a six-hour leg to the exchanges/depositories).
- `sector` (string, required): Sectoral regulator, or "none".

### `us_eu_incident_reporting_deadlines` (~311 tokens)

US and EU cyber incident reporting deadlines

Incident-reporting clocks under SEC Form 8-K/6-K, NYDFS Part 500, the US bank 36-hour rule, HIPAA, the FTC Safeguards Rule, NIS2, DORA, GDPR and the EU Cyber Resilience Act, each from its own trigger. Give aware_at (and decided_at for materiality/classification clocks) for wall-clock due times.

Input parameters:

- `aware_at` (string): Optional. When the entity became aware, ISO 8601 with offset.
- `bank_service_provider` (boolean, required): A bank service provider under the same rule.
- `cra_manufacturer` (boolean, required): A manufacturer of products with digital elements under the EU CRA.
- `decided_at` (string): Optional. When materiality/reportability/major classification was determined, ISO 8601 with offset.
- `dora` (string, required): DORA status.
- `ftc_safeguards` (boolean, required): A non-bank financial institution under the FTC Safeguards Rule.
- `gdpr` (string, required): GDPR role for the personal data involved.
- `hipaa` (string, required): HIPAA role.
- `nis2` (boolean, required): An essential or important entity under NIS2.
- `nydfs` (boolean, required): Regulated by the New York DFS (23 NYCRR 500).
- `sec` (string, required): SEC status.
- `us_bank` (boolean, required): A US banking organisation under the 36-hour computer-security incident rule.

### `find_global_cyber_regulations` (~342 tokens)

Which cyber regulations apply across India, the US and the EU

For an organisation operating across India, the US and the EU, lists the cyber and data-protection regimes that apply, may apply (check) or are pending, with why and a caution for each. All flags default to false and sizes/sectors to none.

Input parameters:

- `cra_manufacturer` (boolean): Manufacturer of products with digital elements sold in the EU.
- `dora_financial_entity` (boolean): EU financial entity under DORA.
- `eu_personal_data` (boolean): Processes personal data of people in the EU.
- `ftc_safeguards` (boolean): Non-bank financial institution under the FTC Safeguards Rule.
- `hipaa` (boolean): Covered entity or business associate under HIPAA.
- `ict_provider_to_eu_finance` (boolean): ICT third-party provider to EU financial entities.
- `india_financial_regulated` (boolean): Regulated by RBI, SEBI, IRDAI or IFSCA.
- `india_listed` (boolean): Listed on an Indian stock exchange.
- `india_operations` (boolean): Operates in India.
- `india_personal_data` (boolean): Processes digital personal data of individuals in India.
- `nis2_sector` (string): NIS2 sector annex.
- `nydfs` (boolean): Regulated by the New York DFS.
- `sec` (string): SEC status.
- `size` (string): Enterprise size.
- `us_bank` (boolean): US banking organisation.
- `us_critical_infrastructure` (boolean): US critical-infrastructure sector.
- `us_personal_data` (boolean): Holds personal data of US residents.

### `sebi_cscrf_category` (~341 tokens)

SEBI CSCRF category for a regulated entity

Works out a SEBI regulated entity’s CSCRF category (MII, Qualified, Mid-size, Small-size, Self-certification or Exempt) from the current thresholds, and the obligations that category carries. Call with only entity_type to see which figures it needs. Boundary values the circulars leave uncategorised are reported as such, not guessed.

Input parameters:

- `auc` (number): Figure for the "auc" criterion (see entity_type's required figures). ₹ crore values in crore; counts as plain numbers.
- `aum` (number): Figure for the "aum" criterion (see entity_type's required figures). ₹ crore values in crore; counts as plain numbers.
- `clientele_trading_volume` (number): Figure for the "clientele-trading-volume" criterion (see entity_type's required figures). ₹ crore values in crore; counts as plain numbers.
- `collateral_with_ccs` (number): Figure for the "collateral-with-ccs" criterion (see entity_type's required figures). ₹ crore values in crore; counts as plain numbers.
- `corpus` (number): Figure for the "corpus" criterion (see entity_type's required figures). ₹ crore values in crore; counts as plain numbers.
- `entity_type` (string, required): The SEBI entity type.
- `folios` (number): Figure for the "folios" criterion (see entity_type's required figures). ₹ crore values in crore; counts as plain numbers.
- `registered_clients` (number): Figure for the "registered-clients" criterion (see entity_type's required figures). ₹ crore values in crore; counts as plain numbers.

### `india_threat_scorecard` (~78 tokens)

India Cyber Threat Scorecard

Aggregate counts of publicly observed cyber threat activity affecting Indian organisations, by industry vertical and category, for one edition (latest by default). Aggregate only: no organisation is named. A vertical the source did not cover is unmeasured, not zero.

Input parameters:

- `edition` (string): Edition slug, YYYY-MM. Omit for the latest.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/nimitt-in-india-cyber-regulations/www#diagnostics

## Score history

- 2026-10-07: 77
- 2026-10-05: 76
- 2026-10-04: 76
- 2026-10-03: 75
- 2026-10-02: 75
- 2026-10-01: 74
- 2026-09-30: 74
- 2026-09-29: 73
- 2026-09-28: 73

## Common questions

### What is the Indian Cyber Regulation Register (BitScore) MCP server?

Indian Cyber Regulation Register (BitScore) is an MCP server listed in the public MCP registry as io.github.nimitt-IN/india-cyber-regulations. Indian cyber regulation register and incident-reporting deadlines (India, US, EU), read at source. This page covers its hosted endpoint (https://www.bitscore.in/mcp).

### Is the Indian Cyber Regulation Register (BitScore) MCP server safe to use?

Indian Cyber Regulation Register (BitScore) scores 77 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 Cyber Regulation Register (BitScore) MCP server expose?

Indian Cyber Regulation Register (BitScore) exposes 8 tools: search_instruments, get_instrument, find_applicable_regulations, india_incident_reporting_deadlines, us_eu_incident_reporting_deadlines, and 3 more. Their descriptions and schemas cost roughly 1,787 tokens of context every time the server is loaded.

### Does the Indian Cyber Regulation Register (BitScore) MCP server require authentication?

No. We connected to Indian Cyber Regulation Register (BitScore) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Indian Cyber Regulation Register (BitScore) MCP server still maintained?

Indian Cyber Regulation Register (BitScore) is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.bitscore.in/mcp
- Website: https://www.bitscore.in/data/connector
- Changelog RSS feed: https://verifymcp.io/servers/nimitt-in-india-cyber-regulations/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/nimitt-in-india-cyber-regulations/www.json
- HTML version of this page: https://verifymcp.io/servers/nimitt-in-india-cyber-regulations/www