Skip to main content
Glama

Indian Cyber Regulation Register (BitScore)

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
BitScore — Indian Cyber Regulations

TDQS

A3.9/5.0

Scored across 9 tools

Disambiguation4/5

The verb-style tools (search_instruments vs get_instrument) are explicitly paired by their descriptions, and the two deadline tools are cleanly split by jurisdiction (India vs US/EU). The main potential overlap is find_applicable_regulations vs find_global_cyber_regulations and cyber_weather_today vs india_threat_scorecard, but the descriptions make the entity-class vs cross-border and daily-condition vs aggregate-counts distinction clear enough.

Naming Consistency4/5

All names are snake_case and follow recognisable groups: find_*/get_*/search_* for retrieval, <jurisdiction>_incident_reporting_deadlines for the clock tools, and india_*/sebi_*/us_eu_* for scoping. It is not a strict uniform verb_noun pattern (cyber_weather_today and india_threat_scorecard are noun phrases), but the conventions are predictable and readable.

Tool Count5/5

Nine tools for a regulatory register covering search, lookup, applicability, deadline computation, threat context and one specialised categorisation helper is well-scoped. Each tool occupies a distinct slice of the workflow and none looks like filler.

Completeness4/5

The core lifecycle is covered: discover instruments (search), read one fully (get), determine applicability (India entity-class and cross-border), enumerate incident clocks with computed due times, and classify SEBI entities. Remaining gaps are minor — there is no tool to enumerate upcoming deadlines calendar-wide across instruments, no obligation/control mapping for a given entity, and no change-tracking or comparison between instruments.

Available Tools

9 tools
cyber_weather_todayCyber Weather todayA
Read-onlyIdempotent
Inspect

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.

Inputs: no named parameters.

find_applicable_regulationsWhich Indian cyber regulations apply to an entityA
Read-onlyIdempotent
Inspect

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.

Inputs: listed (required), entity_class (required), handles_personal_data (required).

find_global_cyber_regulationsWhich cyber regulations apply across India, the US and the EUA
Read-onlyIdempotent
Inspect

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.

Inputs: sec, size, hipaa, nydfs, +13 more.

get_instrumentGet one instrument from the registerA
Read-onlyIdempotent
Inspect

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.

Inputs: id (required).

india_incident_reporting_deadlinesIndian cyber incident reporting deadlinesA
Read-onlyIdempotent
Inspect

Every incident-reporting clock an Indian entity owes — CERT-In six hours, the sectoral regulator (RBI, including non-bank payment system operators, SEBI, IRDAI, PFRDA, 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.

Inputs: listed (required), sector (required), personal_data (required), protected_system (required), +8 more.

india_threat_scorecardIndia Cyber Threat ScorecardA
Read-onlyIdempotent
Inspect

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.

Inputs: edition.

search_instrumentsSearch the Indian cyber regulation registerA
Read-onlyIdempotent
Inspect

Search every cyber and data-protection instrument binding Indian regulated entities (RBI, SEBI, IRDAI, PFRDA, 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.

Inputs: limit, query, issuer, status.

sebi_cscrf_categorySEBI CSCRF category for a regulated entityA
Read-onlyIdempotent
Inspect

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.

Inputs: entity_type (required), auc, aum, corpus, +4 more.

us_eu_incident_reporting_deadlinesUS and EU cyber incident reporting deadlinesB
Read-onlyIdempotent
Inspect

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.

Inputs: sec (required), dora (required), gdpr (required), nis2 (required), +8 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to answer questions offline, with no dependencies, about Gulf cyber incident notification duties, including which authorities to alert, their deadlines, and the official source behind each one.
      8
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Broadcasts Article 73 incident reports simultaneously to EU AI Act, DORA, NIS2, GDPR, and ISO 42001 regulators, with escalation workflows and audit trails.
      100 PyPI
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query upcoming Indian statutory obligations, inspect individual rules and their penalty exposure, search filings, derive downstream deadlines from corporate events, check dates against holidays, and read regulator updates. It reads the published calendar data, with the data source configurable via an environment variable.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources