@pipeworx/in-irdai-penalties
by pipeworx-io
README.md
# @pipeworx/in-irdai-penalties
Has India's insurance regulator issued a penalty or enforcement order against this insurer, broker, bank agent or administrator? The IRDAI warnings-and-penalties register, firms only.
Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 2007+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
## Tools
- `in_irdai_penalties_list(page?, pages?, name?)` — one page (twenty orders, firms and individuals mixed) of the authority's own list per page number, up to 3 consecutive pages, newest first: order title, publication date, the authority's reference number and a link to the document page. `name` keeps rows whose title contains it. Returns `result` (`rows`, `no_title_match_on_pages_read`, `no_firm_order_on_pages_read`, `beyond_last_page`), `pages_read`, `orders_scanned`, `person_or_unclassified_dropped`, `total_orders_in_register`, `coverage` and `data_as_of`.
## Auth
Keyless.
## Data sources
- Insurance Regulatory and Development Authority of India, warnings and penalties register, read from the publisher on request. Page numbers are the authority's own. `data_as_of` is the day of the read.
## Behaviour worth knowing
- Firms only. Individual agents, surveyors and advisers are dropped and counted in `person_or_unclassified_dropped`.
- Titles are the authority's, Hindi and English together; the English part is returned. The order document behind the link holds the findings and the penalty.
- A name filter covers titles on the pages read, and `coverage` says so; no row is not a clearance.
- A page that cannot be read or has changed shape is an error, never "no order found".
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"in-irdai-penalties": {
"url": "https://gateway.pipeworx.io/in-irdai-penalties/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/in-irdai-penalties/mcp` returns the tools in the table
above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's `initialize` response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
`ask_pipeworx`, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed
directly, instead of just this one's:
```json
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
```
Both URLs reach the same gateway and the same 2007+ data sources. The
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
reaches all of them from either one.
## No MCP client? Call it over HTTP
```bash
curl -X POST https://gateway.pipeworx.io/v1/tools/in_irdai_penalties_list \
-H 'Content-Type: application/json' \
-d '{"page":1}'
```
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/in_irdai_penalties_list`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-in-irdai-penalties` is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with `npx`, and it forwards every call to the same
`https://gateway.pipeworx.io/in-irdai-penalties/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"in-irdai-penalties": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-in-irdai-penalties"]
}
}
}
```
Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
`"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.
It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
also list `ask_pipeworx` and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
your Node version's documentation.
## Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English —
this works on the pack endpoint above as well as on the full gateway:
```
ask_pipeworx({ question: "your question about In Irdai Penalties data" })
```
The gateway picks the right tool and fills the arguments automatically.
## More
- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)
## License
MIT
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues