What it does
Given an Indian phone number in +91 format or a custom UPI VPA, the tool checks more than 30 UPI handles, including PhonePe, Paytm, BHIM, Google Pay and Amazon Pay, and returns the active UPI IDs found for that phone. For each VPA it also returns the bank-registered name from NPCI, with Razorpay and PayU used for lookups. Bulk arrays of phones and VPAs are supported.
The documentation names fraud investigation, KYC enrichment, law-enforcement OSINT, compliance screening for fintechs and due diligence before a UPI payment as the typical uses. It can be added to Claude, Claude Code, Codex or any MCP client, and it runs as an Apify Actor on pay-per-event pricing. Each lookup needs a Razorpay key_id and a PayU merchant key and salt supplied by the user, so upstream API usage counts against the user's own quotas. Charges apply only to targets that a lookup answered.
Limitations and requirements
Requires an Apify account and sign-in for MCP use. Razorpay key_id is mandatory for every run; PayU merchant key and salt are also required. Input phones must be in +91XXXXXXXXXX format. Razorpay and PayU rate-limit per merchant. Upstream API costs are billed to the user's own Razorpay and PayU quotas, and the Actor is pay-per-event with a start fee. The publisher states that compliance with applicable laws is the user's responsibility; the DPDP Act 2023 law-enforcement exemption is cited for legitimate investigation use only.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 18 Nov 2026 · its page on the source
UPI ID OSINT & Verification - Phone to VPAs, Bank Name (India)
UPI ID OSINT - Phone to VPAs + Bank Names India | Bulk
v0.3.12As shown on registry.modelcontextprotocol.io when we last read it