Check an x402 seller before paying: verdict, failure rate and evidence from paid calls on Base.
Nothing to run from here
Instamojo MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
9
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read Instamojo payment requests, payments and refunds; create payment links and refund payments.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http instamojo-mcp-by-usefulapi https://instamojo.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# instamojo_list_payment_requests, instamojo_get_payment_request, instamojo_create_payment_request and 6 more
Instamojo MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 421 servers
usefulapi421 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http instamojo-mcp-by-usefulapi https://instamojo.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
| limit | integer | no | Rows per page, 1-500 (default 50). |
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}/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| payment_request_id | string | yes | Payment request id (a 32-character hex id from instamojo_list_payment_requests). |
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/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| amount | number | yes | Amount in INR (Instamojo documents a minimum of 9 and a maximum of 200000 per request). |
| purpose | string | yes | What the payment is for (shown to the buyer). Often used as your own order reference. |
| buyer_name | string | no | Name of the payer. |
| string | no | Email of the payer (required when send_email is true). | |
| phone | string | no | Phone number of the payer (required when send_sms is true). |
| redirect_url | string | no | URL the buyer is redirected to after paying (Instamojo appends payment_request_id, payment_status and payment_id). |
| webhook | string | no | URL Instamojo POSTs the payment details to after a payment. |
| allow_repeated_payments | boolean | no | true = the link accepts several payments (Instamojo's default); false = one payment only. |
| send_email | boolean | no | true = Instamojo emails the link to the payer (needs email). Default false: nothing is sent. |
| send_sms | boolean | no | true = Instamojo texts the link to the payer (needs phone). Default false: nothing is sent. |
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/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| payment_request_id | string | yes | Payment request id. |
WRITE: enable a previously disabled payment request so its link accepts payments again. POST /payment-requests/{id}/enable/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| payment_request_id | string | yes | Payment request id. |
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}/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| payment_id | string | yes | Payment id, e.g. MOJO5a06005J21512197 (from instamojo_get_payment_request). |
List refunds with id (case id), payment id, status, reason type, refund and total amount (INR) and date. Paged: use next_page. GET /refunds/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
| limit | integer | no | Rows per page, 1-500 (default 50). |
One refund by its id (the case id from instamojo_list_refunds, e.g. C5c0751272). GET /refunds/{id}/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| refund_id | string | yes | Refund id (case id). |
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 = custome
| Parameter | Type | Required | Notes |
|---|---|---|---|
| payment_id | string | yes | Payment id (MOJO...) of the payment to refund. |
| 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 cancele |
| body | string | yes | Text explaining the refund. |
| refund_amount | number | no | Amount to refund in INR; default the full paid amount. |
| transaction_id | string | no | Your own unique id for this refund case; Instamojo uses it to refuse a replayed call (mandatory from the second refund case onwards). |
| confirm | boolean | no | Must be true to actually create the refund; otherwise only a preview is returned. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Instamojo MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.8.2 · scanned 31 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 2 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest3d0d591c90a19b4739f50ac0bdf9bb981ab78b46d72613b0613840c12dc6ca2f
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| instamojo_list_payment_requests | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| instamojo_get_payment_request | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| instamojo_create_payment_request | external-sink | external-sink: keyword "send_email", parameter "webhook", declares readOnlyHint: false, openWorldHint: true |
| instamojo_disable_payment_request | external-sink | external-sink: declares destructiveHint: true, openWorldHint: true |
| instamojo_enable_payment_request | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| instamojo_get_payment | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| instamojo_list_refunds | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| instamojo_get_refund | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| instamojo_create_refund | untrusted-inputexternal-sink | untrusted-input: keyword "download"; external-sink: declares destructiveHint: true, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest3d0d591c90a19b47
Scanned2026-10-31
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.8.2.
1.8.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Instamojo MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.