INDIVIDUAL MCP TOOL

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

bitscore.innone authenticationAvailability not checked

LIVE ENDPOINT

https://www.bitscore.in/mcp

No auth detected

Connect to this endpoint to inspect the live schema for india_threat_scorecard and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

bitscore.in

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.bitscore-india-cyber-regulations]
url = "https://www.bitscore.in/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: bitscore-india-cyber-regulations
Remote MCP URL: https://www.bitscore.in/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "bitscore-india-cyber-regulations": {
      "url": "https://www.bitscore.in/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "bitscore-india-cyber-regulations",
  "transport": "streamable-http",
  "url": "https://www.bitscore.in/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

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