io.github.nimitt-IN/india-cyber-regulations

Est-ce que io.github.nimitt-IN/india-cyber-regulations est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.nimitt-IN/india-cyber-regulations » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 9 outils

• cyber_weather_today≈ 164 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "cyber_weather_today", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_applicable_regulations≈ 312 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • listed · boolean · requis
    Listed on an Indian stock exchange (brings SEBI LODR disclosure).
  • entity_class · string · requis · commercial-bank | sfb | payments-bank | ucb | aifi | nbfc | cic | rrb
    The entity’s class.
  • handles_personal_data · boolean · requis
    Processes digital personal data of individuals in India (brings DPDP).

  Exemple d'appel

  {"name": "find_applicable_regulations", "arguments": {"listed": true, "entity_class": "commercial-bank", "handles_personal_data": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_global_cyber_regulations≈ 590 tokens

  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.

  Paramètres, retour & exemple (17)

  Paramètres

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

  Exemple d'appel

  {"name": "find_global_cyber_regulations", "arguments": {"sec": "none", "size": "small", "hipaa": true, "nydfs": true, "us_bank": true, "nis2_sector": "none"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_instrument≈ 177 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Register id, e.g. "rbi-cyber-2026-nbfc" or "sebi-cscrf".

  Exemple d'appel

  {"name": "get_instrument", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• india_incident_reporting_deadlines≈ 529 tokens

  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.

  Paramètres, retour & exemple (10)

  Paramètres

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

  Exemple d'appel

  {"name": "india_incident_reporting_deadlines", "arguments": {"listed": true, "sector": "rbi", "personal_data": true, "protected_system": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• india_threat_scorecard≈ 180 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • edition · string · optionnel · 2026-09 | 2026-08
    Edition slug, YYYY-MM. Omit for the latest.

  Exemple d'appel

  {"name": "india_threat_scorecard", "arguments": {"edition": "2026-09"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_instruments≈ 310 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer · optionnel
    Maximum results, 1–50. Default 20.
  • query · string · optionnel
    Words to match against the name, reference number and who it binds, e.g. "outsourcing", "NBFC", "2024/113".
  • issuer · string · optionnel · RBI | SEBI | IRDAI | IFSCA | CERT-In | MeitY
    Only instruments from this issuer.
  • status · string · optionnel · in-force | partly-in-force | superseded
    Only instruments with this status.

  Exemple d'appel

  {"name": "search_instruments", "arguments": {"limit": 1, "query": "texte", "issuer": "RBI", "status": "in-force"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• sebi_cscrf_category≈ 630 tokens

  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.

  Paramètres, retour & exemple (8)

  Paramètres

  • auc · number · optionnel
    Figure for the "auc" criterion (see entity_type's required figures). ₹ crore values in crore; counts as plain numbers.
  • aum · number · optionnel
    Figure for the "aum" criterion (see entity_type's required figures). ₹ crore values in crore; counts as plain numbers.
  • corpus · number · optionnel
    Figure for the "corpus" criterion (see entity_type's required figures). ₹ crore values in crore; counts as plain numbers.
  • folios · number · optionnel
    Figure for the "folios" criterion (see entity_type's required figures). ₹ crore values in crore; counts as plain numbers.
  • entity_type · string · requis · mii | stock-broker | proprietary-stock-broker | depository-participant | portfolio-manager | merchant-banker | aif-vcf-manager | mutual-fund-amc
    The SEBI entity type.
  • registered_clients · number · optionnel
    Figure for the "registered-clients" criterion (see entity_type's required figures). ₹ crore values in crore; counts as plain numbers.
  • collateral_with_ccs · number · optionnel
    Figure for the "collateral-with-ccs" criterion (see entity_type's required figures). ₹ crore values in crore; counts as plain numbers.
  • clientele_trading_volume · number · optionnel
    Figure for the "clientele-trading-volume" criterion (see entity_type's required figures). ₹ crore values in crore; counts as plain numbers.

  Exemple d'appel

  {"name": "sebi_cscrf_category", "arguments": {"entity_type": "mii"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• us_eu_incident_reporting_deadlines≈ 559 tokens

  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.

  Paramètres, retour & exemple (12)

  Paramètres

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

  Exemple d'appel

  {"name": "us_eu_incident_reporting_deadlines", "arguments": {"sec": "none", "dora": "none", "gdpr": "none", "nis2": true, "hipaa": "none", "nydfs": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://www.bitscore.in/mcp