# Indian Cyber Regulation Register (BitScore)

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

- name: io.github.nimitt-IN/india-cyber-regulations
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 80/100 flags: no-repository
- quality: 100/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.nimitt-IN%2Findia-cyber-regulations
- tools: https://api.protogrid.dev/v1/servers/io.github.nimitt-IN%2Findia-cyber-regulations/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 45
- drivers: +website +reachable +uptime-100% +updated-23d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 100/100 (strong)

### protocol: 100 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- pass `protocol.list_ttl`: tool list is cacheable (ttlMs 3600000)

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 9 of 9 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 3,048 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 3 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 9, about 3,048 tokens to load them all
- tool set hash: ca3bded3f550e2e60c89c25988ea0b91
- tools last changed: 2026-10-19T05:43:53.346Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.nimitt-IN/india-cyber-regulations.svg)](https://protogrid.dev/servers/io.github.nimitt-IN/india-cyber-regulations)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-19 `cyber_weather_today` added
  - Today’s global cyber threat condition (Clear, Cloudy, Showers, Storm or Severe) from BitScore’s Cyber Weather, refreshed daily at 07:30 IST: points per instrument, CISA KEV additions, EPSS risers, outlook, patch calendar, outages and three actions. Each field names its source and licence. Indicative, not a measure of any organisation’s risk.
- 2026-09-30 `india_threat_scorecard` changed (inputSchema)
- 2026-09-29 `sebi_cscrf_category` changed (inputSchema)

Full history: https://api.protogrid.dev/v1/servers/io.github.nimitt-IN%2Findia-cyber-regulations/changes

## Remotes

- https://www.bitscore.in/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (9)

- `cyber_weather_today`: Today’s global cyber threat condition (Clear, Cloudy, Showers, Storm or Severe) from BitScore’s Cyber Weather, refreshed daily at 07:30 IST: points per instrument, CISA KEV additions, EPSS risers, outlook, patch calendar, outages and three actions. Each field names its source and licence. Indicative, not a measure of any organisation’s risk.
- `find_applicable_regulations`: 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.
- `find_global_cyber_regulations`: 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.
- `get_instrument`: 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.
- `india_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.
- `india_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.
- `search_instruments`: 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.
- `sebi_cscrf_category`: 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.
- `us_eu_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.