Instamojo MCP by usefulapi
REMOTE · INSTAMOJO.USEFULAPI.IO
Read Instamojo payment requests, payments and refunds; create payment links and refund payments.
Available components
Last scanned (2 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1460 tokens (~162/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "instamojo_get_refund" implies "refund" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.2 → 1.0.3 functional
- Server version: 1.0.0 → 1.0.2 functional
- 24 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Probed https://instamojo.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of instamojo.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://instamojo.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://instamojo.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://instamojo.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://instamojo.usefulapi.io/mcp |
| Authorisation server | https://instamojo.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://instamojo.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/instamojo/ |
| http (plaintext) | http://instamojo.usefulapi.io/mcp | Inconclusive | 302 | http://instamojo.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
instamojo_create_payment_request Create payment request ~330
WRITE: create a payment request (a payment link) and return its id and URLs (longurl, shorturl) to share with the buyer. Amount is in INR. The buyer is NOT emailed or texted unless send_email / send_sms is true (they then need email / phone). Nothing is charged; the buyer pays on the link. POST /payment-requests/.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_repeated_payments | boolean | – | true = the link accepts several payments (Instamojo's default); false = one payment only. |
| amount | number | yes | Amount in INR (Instamojo documents a minimum of 9 and a maximum of 200000 per request). |
| buyer_name | string | – | Name of the payer. |
| string | – | Email of the payer (required when send_email is true). | |
| phone | string | – | Phone number of the payer (required when send_sms is true). |
| purpose | string | yes | What the payment is for (shown to the buyer). Often used as your own order reference. |
| redirect_url | string | – | URL the buyer is redirected to after paying (Instamojo appends payment_request_id, payment_status and payment_id). |
| send_email | boolean | – | true = Instamojo emails the link to the payer (needs email). Default false: nothing is sent. |
| send_sms | boolean | – | true = Instamojo texts the link to the payer (needs phone). Default false: nothing is sent. |
| webhook | string | – | URL Instamojo POSTs the payment details to after a payment. |
No output schema declared.
No examples provided.
instamojo_create_refund Create refund ~314
WRITE (moves money): refund a payment, in full or in part. Instamojo allows only ONE refund per payment, so a partial refund cannot be topped up later. Without confirm: true nothing is sent and the call returns a preview of the refund; ask the user to confirm, then call again with confirm: true. Reason types: RFD = duplicate/delayed payment, TNR = product/service no longer available, QFL = customer not satisfied, QNR = product lost/damaged, EWN = digital download issue, TAN = event was canceled/changed, PTH = problem not described above. POST /refunds/.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Text explaining the refund. |
| confirm | boolean | – | Must be true to actually create the refund; otherwise only a preview is returned. |
| payment_id | string | yes | Payment id (MOJO...) of the payment to refund. |
| refund_amount | number | – | Amount to refund in INR; default the full paid amount. |
| transaction_id | string | – | Your own unique id for this refund case; Instamojo uses it to refuse a replayed call (mandatory from the second refund case onwards). |
| type | string | yes | Reason code. RFD = duplicate/delayed payment, TNR = product/service no longer available, QFL = customer not satisfied, QNR = product lost/damaged, EWN = digital download issue, TAN = event was cancel… |
No output schema declared.
No examples provided.
instamojo_disable_payment_request Disable payment request ~64
WRITE: disable a payment request so its link no longer accepts payments (instamojo_enable_payment_request undoes it). Existing payments are not touched. POST /payment-requests/{id}/disable/.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_request_id | string | yes | Payment request id. |
No output schema declared.
No examples provided.
instamojo_enable_payment_request Enable payment request ~49
WRITE: enable a previously disabled payment request so its link accepts payments again. POST /payment-requests/{id}/enable/.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_request_id | string | yes | Payment request id. |
No output schema declared.
No examples provided.
instamojo_get_payment Get payment ~99
One payment by its id (MOJO...): status (Credit = paid, Failed), amount, fees, buyer, instrument (card, UPI, netbanking, wallet), failure reason, payout and the payment request it belongs to. GET /payments/{id}/.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_id | string | yes | Payment id, e.g. MOJO5a06005J21512197 (from instamojo_get_payment_request). |
No output schema declared.
No examples provided.
instamojo_get_payment_request Get payment request ~74
One payment request by id, with its status and the payments made against it (the payment ids go to instamojo_get_payment). GET /payment-requests/{id}/.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_request_id | string | yes | Payment request id (a 32-character hex id from instamojo_list_payment_requests). |
No output schema declared.
No examples provided.
instamojo_get_refund Get refund ~60
One refund by its id (the case id from instamojo_list_refunds, e.g. C5c0751272). GET /refunds/{id}/.
| Name | Type | Req | Description |
|---|---|---|---|
| refund_id | string | yes | Refund id (case id). |
No output schema declared.
No examples provided.
instamojo_list_payment_requests List payment requests ~109
List the payment requests (payment links) of the account with id, purpose, amount (INR), buyer, status (Pending, Sent, Failed, Completed), short and long URL and timestamps. Paged: use next_page. GET /payment-requests/.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows per page, 1-500 (default 50). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
No output schema declared.
No examples provided.
instamojo_list_refunds List refunds ~95
List refunds with id (case id), payment id, status, reason type, refund and total amount (INR) and date. Paged: use next_page. GET /refunds/.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows per page, 1-500 (default 50). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
No output schema declared.
No examples provided.
How do I install the Instamojo MCP by usefulapi server?
Instamojo MCP by usefulapi is a hosted endpoint at https://instamojo.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · instamojo.usefulapi.io
claude mcp add --transport http io-usefulapi-instamojo 'https://instamojo.usefulapi.io/mcp'
What is the Instamojo MCP by usefulapi server?
Instamojo MCP by usefulapi is listed in the public MCP registry as io.usefulapi/instamojo. Read Instamojo payment requests, payments and refunds; create payment links and refund payments. This page covers its hosted endpoint (https://instamojo.usefulapi.io/mcp).
Is the Instamojo MCP by usefulapi server safe to use?
Instamojo MCP by usefulapi scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Instamojo MCP by usefulapi server expose?
Instamojo MCP by usefulapi exposes 9 tools: instamojo_list_payment_requests, instamojo_get_payment_request, instamojo_create_payment_request, instamojo_disable_payment_request, instamojo_enable_payment_request, and 4 more. Their descriptions and schemas cost roughly 1,194 tokens of context every time the server is loaded.
Does the Instamojo MCP by usefulapi server require authentication?
Yes. Instamojo MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Instamojo MCP by usefulapi server still maintained?
Instamojo MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.