mcp-meroshare
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MERO_SHARE_PASSWORD | Yes | Your account password | |
| MERO_SHARE_USERNAME | Yes | Your BOID (username) | |
| MERO_SHARE_CLIENT_ID | Yes | Your DP client ID (e.g., 162) | |
| MERO_SHARE_CRN_NUMBER | Yes | Your CASBA CRN number | |
| MERO_SHARE_TRANSACTION_PIN | Yes | Your transaction PIN (TPIN) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| meroshare_get_dp_listA | List all Depository Participants with their numeric client IDs (call this first to find your client_id) |
| meroshare_loginA | Log in to MeroShare. Password is read from MERO_SHARE_PASSWORD in .env |
| meroshare_logoutA | Log out of MeroShare and clear the session |
| meroshare_get_current_issuesA | List all currently open IPO, FPO, and Rights share issues available for application |
| meroshare_apply_ipoA | Apply for an IPO/FPO/Rights issue. Use dry_run=true to preview without submitting. |
| meroshare_get_application_reportsA | Get all submitted IPO/FPO/Rights application reports |
| meroshare_get_bank_detailsB | Get linked bank account details using your demat number (16-digit) |
| meroshare_get_own_detailA | Get your own account/profile details (name, BOID, demat, email) |
| meroshare_get_transactionsC | Get share transaction history |
| meroshare_check_ipo_resultB | Check IPO/FPO allotment result for a specific issue |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tekchapagain1/meroshare_mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server