mcp-registry/com.indiainsurances/mcp · v1.0.0
As of 2026-10-26 17:26 UTC, the Indiainsurances MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Every Indian insurance policy, clause by clause, with verbatim quotes. Free, no API key.
Point your MCP client at this streamable-http endpoint: https://indiainsurances.com/mcp
16 of 16 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
12 parameter(s) across 7 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 7 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.indiainsurances%2Fmcp/fixes
{
"name": "compare_policies",
"description": "Two to four products side by side on the same fields, with differences flagged and each value sourced. Products of the same category compare best. Nothing is scored: explain the trade-offs to the user.",
"inputSchema": {
"type": "object",
"required": [
"uins"
],
"properties": {
"uins": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 4,
"minItems": 2
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "find_forms",
"description": "An insurer's forms: claim forms, complaint and grievance forms, service requests (nominee, refund, surrender, KYC) and proposal forms, with field counts and the original PDF.",
"inputSchema": {
"type": "object",
"properties": {
"q": {
"type": "string",
"description": "Words in the title or in what the form is for, e.g. death, nominee, cashless"
},
"insurer": {
"type": "string",
"description": "Insurer slug"
},
"purpose": {
"enum": [
"claim",
"complaint",
"service",
"proposal"
],
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_form",
"description": "One form, field by field as printed: sections, each field's label, type, whether required and what to write; documents to attach; where to send it; deadlines; and, for fillable PDFs, the PDF's own field names. Walk the user through it one field at a time; never invent answers.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "integer",
"description": "Form id from find_forms or complaint_path"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.indiainsurances/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.indiainsurances/mcp"}) over MCP.
draft_complaint ~435 tokensrequest_help ~251 tokenssearch_policies ~227 tokenscomplaint_path ~219 tokensget_policy ~161 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.indiainsurances%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.indiainsurances%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.indiainsurances%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.indiainsurances%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.indiainsurances%2Fmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b4820ab15e2ed111…, first seen 2026-10-21, included at leaf 36607 of 74,435. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable retrieval servers · most reliable data servers · most reliable communication servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 17:26 UTC, the Indiainsurances MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Indiainsurances MCP server advertises 16 tools, including about_dataset, compare_policies, complaint_path, draft_complaint, find_forms.
Point your MCP client at this streamable-http endpoint: https://indiainsurances.com/mcp
Glimind scanned all 16 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.