# Instamojo MCP by usefulapi (remote · instamojo.usefulapi.io)

Read Instamojo payment requests, payments and refunds; create payment links and refund payments.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `instamojo.usefulapi.io`: 62/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-instamojo/instamojo.md), [page](https://verifymcp.io/servers/io-usefulapi-instamojo/instamojo)

## Channel facts

- Endpoint: `https://instamojo.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 88/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-instamojo 'https://instamojo.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-instamojo": {
      "url": "https://instamojo.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-instamojo": {
      "type": "http",
      "url": "https://instamojo.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-instamojo]
url = "https://instamojo.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-instamojo": {
      "type": "remote",
      "url": "https://instamojo.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-instamojo --url 'https://instamojo.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-instamojo:
    url: "https://instamojo.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-instamojo": {
      "Transport": "http",
      "Url": "https://instamojo.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-instamojo -t streamable-http -u 'https://instamojo.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-instamojo": {
      "type": "http",
      "url": "https://instamojo.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-25 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.2 → 1.0.3
- [functional] Server version: 1.0.0 → 1.0.2

### 2026-10-24 (score 61)

First indexed and scored.

## MCP tools (9)

### `instamojo_list_payment_requests` (~109 tokens)

List payment requests

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/.

Input parameters:

- `limit` (integer): Rows per page, 1-500 (default 50).
- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.

### `instamojo_get_payment_request` (~74 tokens)

Get payment request

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}/.

Input parameters:

- `payment_request_id` (string, required): Payment request id (a 32-character hex id from instamojo_list_payment_requests).

### `instamojo_create_payment_request` (~330 tokens)

Create payment request

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/.

Input parameters:

- `allow_repeated_payments` (boolean): true = the link accepts several payments (Instamojo's default); false = one payment only.
- `amount` (number, required): Amount in INR (Instamojo documents a minimum of 9 and a maximum of 200000 per request).
- `buyer_name` (string): Name of the payer.
- `email` (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, required): 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.

### `instamojo_disable_payment_request` (~64 tokens)

Disable payment request

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/.

Input parameters:

- `payment_request_id` (string, required): Payment request id.

### `instamojo_enable_payment_request` (~49 tokens)

Enable payment request

WRITE: enable a previously disabled payment request so its link accepts payments again. POST /payment-requests/{id}/enable/.

Input parameters:

- `payment_request_id` (string, required): Payment request id.

### `instamojo_get_payment` (~99 tokens)

Get payment

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}/.

Input parameters:

- `payment_id` (string, required): Payment id, e.g. MOJO5a06005J21512197 (from instamojo_get_payment_request).

### `instamojo_list_refunds` (~95 tokens)

List refunds

List refunds with id (case id), payment id, status, reason type, refund and total amount (INR) and date. Paged: use next_page. GET /refunds/.

Input parameters:

- `limit` (integer): Rows per page, 1-500 (default 50).
- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.

### `instamojo_get_refund` (~60 tokens)

Get refund

One refund by its id (the case id from instamojo_list_refunds, e.g. C5c0751272). GET /refunds/{id}/.

Input parameters:

- `refund_id` (string, required): Refund id (case id).

### `instamojo_create_refund` (~314 tokens)

Create refund

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/.

Input parameters:

- `body` (string, required): Text explaining the refund.
- `confirm` (boolean): Must be true to actually create the refund; otherwise only a preview is returned.
- `payment_id` (string, required): 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, required): 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…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-instamojo/instamojo#diagnostics

## Score history

- 2026-10-25: 62
- 2026-10-24: 61

## Common questions

### 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.

## Links

- Remote endpoint: https://instamojo.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/instamojo/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-instamojo/instamojo.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-instamojo/instamojo.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-instamojo/instamojo