Indian Cyber Regulation Register (BitScore)
REMOTE · WWW.BITSCORE.IN · SCANNED OCT 7
Indian cyber regulation register and incident-reporting deadlines (India, US, EU), read at source.
Available components
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · www.bitscore.in
claude mcp add --transport http nimitt-in-india-cyber-regulations 'https://www.bitscore.in/mcp'
{
"mcpServers": {
"nimitt-in-india-cyber-regulations": {
"url": "https://www.bitscore.in/mcp"
}
}
} {
"servers": {
"nimitt-in-india-cyber-regulations": {
"type": "http",
"url": "https://www.bitscore.in/mcp"
}
}
} [mcp_servers.nimitt-in-india-cyber-regulations] url = "https://www.bitscore.in/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nimitt-in-india-cyber-regulations": {
"type": "remote",
"url": "https://www.bitscore.in/mcp",
"enabled": true
}
}
} openclaw mcp add nimitt-in-india-cyber-regulations --url 'https://www.bitscore.in/mcp' --transport streamable-http
mcp_servers:
nimitt-in-india-cyber-regulations:
url: "https://www.bitscore.in/mcp" {
"McpServers": {
"nimitt-in-india-cyber-regulations": {
"Transport": "http",
"Url": "https://www.bitscore.in/mcp"
}
}
} assistant mcp add nimitt-in-india-cyber-regulations -t streamable-http -u 'https://www.bitscore.in/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 7 Oct 26 +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.
- 4 Oct 26 +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.
- 2 Oct 26 +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.
- 30 Sept 26 +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.
- 29 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Sept 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Oct 2026 · Probed https://www.bitscore.in/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.bitscore.in | CN=YR2,O=Let's Encrypt,C=US | 7 Sept 2026 | 6 Dec 2026 | RSA 2048 | SHA256-RSA | 6ac61cd521c5700b36f7fc49dec8c1b7a2f |
| SANs: www.bitscore.in | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of www.bitscore.in. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| in. | present | 10094 | 13 | Verified |
| bitscore.in. | present | 50853 | 13 | Verified |
| www.bitscore.in. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; script-src 'self' 'nonce-NWRjMzRhZTktZWJlMS00OWQyLTllYmEtMTQ1ZTI1MzdiYWU5' 'strict-dynamic' https://snap.licdn.com https://www.clarity.ms https://*.clarity.ms https://www.googletagmanager.com https://www.google-analytics.com; style-src 'self' 'nonce-NWRjMzRhZTktZWJlMS00OWQyLTllYmEtMTQ1ZTI1MzdiYWU5'; style-src-attr 'unsafe-inline'; font-src 'self' data:; img-src 'self' data: https://px.ads.linkedin.com https://www.linkedin.com https://px4.ads.linkedin.com https://www.clarity.ms https://*.clarity.ms https://c.bing.com https://www.googletagmanager.com https://*.googletagmanager.com https://www.google-analytics.com https://*.google-analytics.com https://analytics.google.com https://region1.google-analytics.com https://www.google.com https://www.google.co.in https://googleads.g.doubleclick.net https://stats.g.doubleclick.net; connect-src 'self' https://px.ads.linkedin.com https://www.clarity.ms https://*.clarity.ms |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.bitscore.in/mcp | Verified | 200 | |
| http (plaintext) | http://www.bitscore.in/mcp | HTTPS enforced | 308 | https://www.bitscore.in/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_applicable_regulations Which Indian cyber regulations apply to an entity ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_class | string | yes | The entity’s class. |
| handles_personal_data | boolean | yes | Processes digital personal data of individuals in India (brings DPDP). |
| listed | boolean | yes | Listed on an Indian stock exchange (brings SEBI LODR disclosure). |
No output schema declared.
No examples provided.
find_global_cyber_regulations Which cyber regulations apply across India, the US and the EU ~342
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_instrument Get one instrument from the register ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Register id, e.g. "rbi-cyber-2026-nbfc" or "sebi-cscrf". |
No output schema declared.
No examples provided.
india_incident_reporting_deadlines Indian cyber incident reporting deadlines ~315
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The incident involves digital personal data. |
| protected_system | boolean | yes | 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 | yes | Sectoral regulator, or "none". |
No output schema declared.
No examples provided.
india_threat_scorecard India Cyber Threat Scorecard ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| edition | string | – | Edition slug, YYYY-MM. Omit for the latest. |
No output schema declared.
No examples provided.
search_instruments Search the Indian cyber regulation register ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
sebi_cscrf_category SEBI CSCRF category for a regulated entity ~341
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
us_eu_incident_reporting_deadlines US and EU cyber incident reporting deadlines ~311
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.
| Name | Type | Req | Description |
|---|---|---|---|
| aware_at | string | – | Optional. When the entity became aware, ISO 8601 with offset. |
| bank_service_provider | boolean | yes | A bank service provider under the same rule. |
| cra_manufacturer | boolean | yes | 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 | yes | DORA status. |
| ftc_safeguards | boolean | yes | A non-bank financial institution under the FTC Safeguards Rule. |
| gdpr | string | yes | GDPR role for the personal data involved. |
| hipaa | string | yes | HIPAA role. |
| nis2 | boolean | yes | An essential or important entity under NIS2. |
| nydfs | boolean | yes | Regulated by the New York DFS (23 NYCRR 500). |
| sec | string | yes | SEC status. |
| us_bank | boolean | yes | A US banking organisation under the 36-hour computer-security incident rule. |
No output schema declared.
No examples provided.
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.