BharatPay MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_ifscA | Look up bank, branch, address, and supported payment rails (NEFT/RTGS/IMPS/UPI) for an Indian IFSC code. Uses Razorpay's free public IFSC API. |
| validate_panA | Validate Indian PAN format and identify the entity type (Individual / Company / HUF / Trust / Partnership Firm / etc.) from the 4th character. |
| validate_gstinA | Validate Indian GSTIN: format, mod-36 checksum, and extract embedded state and PAN. Returns the registration state name from the leading state code. |
| lookup_pincodeA | Look up state, district, and post offices for an Indian PIN code using the free India Post API. |
| get_mutual_fund_navA | Get the latest daily NAV for an Indian mutual fund scheme. Accepts either an AMFI scheme code (digits only) or a name fragment for fuzzy search. Data sourced from AMFI India's public daily file. |
| validate_upi_vpaA | Validate a UPI VPA's format and identify the issuing PSP and underlying bank from the handle suffix (e.g., 'oksbi' → Google Pay on State Bank of India). |
| format_inrA | Format an INR amount in Indian numbering conventions (lakh/crore
grouping with comma every two digits after the first three) and return
word form. Set |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool addresses a unique Indian financial or address validation task, with no overlap. IFSC, PAN, GSTIN, pincode, mutual fund NAV, UPI VPA, and INR formatting are all distinct and clearly separated.
All tool names follow a consistent verb_noun pattern (e.g., lookup_ifsc, validate_gstin, format_inr). Verbs like 'lookup', 'validate', 'get', and 'format' are used appropriately, with no mixing of conventions.
Seven tools is an appropriate number for a focused domain of Indian financial utilities. Each tool covers a key operation, and the count is neither too sparse nor excessive.
The tool set covers common Indian financial identifiers (IFSC, PAN, GSTIN, UPI), address lookup (pincode), mutual fund data, and currency formatting. This appears comprehensive for the intended use case, with no obvious missing operations.