# Indian Cyber Regulation Register \(BitScore\)

- Registry name: `io.github.nimitt-IN/india-cyber-regulations` · version 1.0.0
- Categories (automatic, keyword rules): Government & law, Monitoring & logs, Infrastructure & security, Security
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.nimitt-IN%2Findia-cyber-regulations
- Server page: https://mcpstation.net/s/io.github.nimitt-IN--india-cyber-regulations.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://www.bitscore.in/mcp`

## Tools (as reported by the server, not verified)

- `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
- `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.
- `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
- `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
- `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.
- `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.
- `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
- `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.
- `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

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html