Feeds, API and MCP
The same rules feed people and machines. Subscribe in Google Calendar or Outlook, pull JSON into your own tools, or let an AI agent query the calendar over MCP.
Calendar subscriptions
All-day events in India time, refreshed with every daily build, with reminders 7 days and 1 day before. Each event carries the period, the law, the cost of a 30-day delay and a link to the official source. In Outlook, choose Add calendar, From internet, and paste the https link.
Feeds are the same for everyone, so they count company-law and SEBI dates from an April-March year and chained filings, such as AOC-4 and MGT-7, from their earlier step's deadline. A team with another financial year, or that records when its AGM was held, gets its own dates in the overview, and each one can be added to a calendar from its detail panel.
By law
By who files
Holiday calendars
Every obligation has its own feed too: open its entry and choose Subscribe to this obligation. For a feed shaped to your profile and filed status, use Add to calendar in the overview, the planner's Download ICS, or the report's CSV.
JSON API
Static files, regenerated daily, free to use with attribution. No key, no rate limit beyond GitHub Pages' own.
| Endpoint | Contents |
|---|---|
/api/v1/bundle.json | Rules, holidays, planner events and metadata in one file. What the site itself loads. |
/api/v1/rules.json | Every obligation as a structured rule: schedule, applicability, law, penalty exposure, sources. |
/api/v1/occurrences.json | Every dated occurrence from the start of the current financial year to 25 months ahead. |
/api/v1/holidays.json | Central gazetted and restricted holidays, exchange and bank holidays where published, and the Canadian, Ontario and US holiday calendars. |
/api/v1/events.json | Event types for the planner and the deadlines that follow each one. |
/api/v1/updates.json | The latest regulator updates collected by the daily job. |
/api/v1/sources.json | The catalogue of open datasets and official sources behind the calendar. |
/api/v1/meta.json | Build time, rule counts, the verified window and the list of endpoints. |
curl -s https://dgomesbr.github.io/india-compliance-calendar/api/v1/occurrences.json | jq '.items[] | select(.due >= "2026-10-01" and .due <= "2026-10-31")'MCP server for AI agents
The repository ships a Model Context Protocol server, so assistants such as Claude, Cursor or any MCP client can ask what is due, what a filing costs if late, or which deadlines follow an AGM. It has no dependencies and runs on Node 22.18 or later; it reads the published data above, so it is always as current as the site.
upcoming_obligations- due items for a horizon (1 week to 24 months), filtered by law, audience or state, ordered by due date or penalty exposure.get_obligation- one rule with its schedule, law, penalty, sources and next due dates.search_obligations- find rules by form, law, authority or keyword.event_deadlines- every deadline that follows an event on a given date.check_date- holidays and obligations on a date.list_holidaysandregulatory_updates- holiday lists and the latest regulator updates.
Clone the repository, then add it to your client. For Claude Code:
git clone https://github.com/dgomesbr/india-compliance-calendar
claude mcp add india-compliance-calendar -- node ./india-compliance-calendar/mcp/server.tsFor Claude Desktop and other clients that read an mcpServers file:
{
"mcpServers": {
"india-compliance-calendar": {
"command": "node",
"args": [
"/path/to/india-compliance-calendar/mcp/server.ts"
]
}
}
}
Agents that read llms.txt find the endpoints and conventions there. Set
ICC_DATA_URL to point the server at a fork's published bundle.