Check Indian IPO allotment by PAN and list mainboard and SME IPOs with listing gains.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Takes an IPO and a PAN and returns whether that PAN was allotted shares in the Indian IPO (allotted, not allotted or no record), from the registrar's official records. PAN is used once for the lookup and never stored. Example input: {"ipo":"jio","pan":"ABCDE1234F"}
IPO slug, id or name fragment, e.g. "jio"
The applicant's 10-character PAN, e.g. ABCDE1234F
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
claude mcp add --transport http ipoallotment https://ipoallotmentcheck.com/mcp
Takes an IPO and a PAN and returns whether that PAN was allotted shares in the Indian IPO (allotted, not allotted or no record), from the registrar's official records. PAN is used once for the lookup and never stored. Example input: {"ipo":"jio","pan":"ABCDE1234F"}
| Argument | Type | Description |
|---|---|---|
| ipo* | string | IPO slug, id or name fragment, e.g. "jio" |
| pan* | string | The applicant's 10-character PAN, e.g. ABCDE1234F |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"ipo",
"pan"
],
"properties": {
"ipo": {
"type": "string",
"maxLength": 80,
"minLength": 1,
"description": "IPO slug, id or name fragment, e.g. \"jio\""
},
"pan": {
"type": "string",
"maxLength": 20,
"minLength": 1,
"description": "The applicant's 10-character PAN, e.g. ABCDE1234F"
}
}
}Takes a phase and returns up to 50 Indian IPOs in it (default allotment-this-week): upcoming, open, closed, allotted, listed, or allotment-this-week (default, allotment dates from 2 days ago to 7 days ahead). Up to 50 rows, newest first, with dates, price, lot size and the page that checks allotment. Example input: {"phase":"allotment-this-week"}
| Argument | Type | Description |
|---|---|---|
| phase | string | Which IPOs to list: upcoming, open, closed, allotted, listed or allotment-this-week |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"phase": {
"enum": [
"upcoming",
"open",
"closed",
"allotted",
"listed",
"allotment-this-week"
],
"type": "string",
"default": "allotment-this-week",
"description": "Which IPOs to list: upcoming, open, closed, allotted, listed or allotment-this-week"
}
}
}Takes an IPO slug or name fragment and returns the full public details of that Indian IPO: dates, price band, lot size, registrar and status URL, phase and listing-day gains. Example input: {"ipo":"jio"}
| Argument | Type | Description |
|---|---|---|
| ipo* | string | IPO slug, id or name fragment, e.g. "jio" |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"ipo"
],
"properties": {
"ipo": {
"type": "string",
"maxLength": 80,
"minLength": 1,
"description": "IPO slug, id or name fragment, e.g. \"jio\""
}
}
}Takes an IPO name fragment and returns up to 25 matching Indian mainboard and SME IPOs with dates, price band, lot size, registrar and status URL, and listing-day gain. Pure lookup, no network calls. Example input: {"query":"jio"}
| Argument | Type | Description |
|---|---|---|
| query* | string | IPO name or part of it, e.g. "jio" |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"maxLength": 80,
"minLength": 1,
"description": "IPO name or part of it, e.g. \"jio\""
}
}
}Takes an optional board and row limit and returns listing-day gains of listed Indian IPOs against the issue price, at open and at close, newest listing first. Example input: {"board":"all","limit":20}
| Argument | Type | Description |
|---|---|---|
| board | string | Which board to include: mainboard, sme or all |
| limit | integer | Maximum rows to return, 1 to 100 |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"board": {
"enum": [
"mainboard",
"sme",
"all"
],
"type": "string",
"default": "all",
"description": "Which board to include: mainboard, sme or all"
},
"limit": {
"type": "integer",
"default": 20,
"maximum": 100,
"minimum": 1,
"description": "Maximum rows to return, 1 to 100"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Oct 30, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.