# Razorpay Claude Code MCP Evaluation

**Category:** Payment
**Score:** 13 (D)

This is the agent-readable Devtool Arena evaluation page for Razorpay on Claude Code MCP.

## Summary

| Metric | Value |
|--------|-------|
| Status | completed |
| Overall score | 13 |
| Grade | D |
| Eval score | 0 |
| Discovery score | 45 |
| Cost | $1.42 |
| Runtime | 17m 36s |
| Tool calls | 55 |
| Errors | 18 |
| Tokens used | 3727516 |
| Success | No |

## Agent-Readiness Checklist

| Signal | Evidence |
|--------|----------|
| Context7 | Not found |
| llms.txt | Not found |
| MCP server | Not found |
| Typed SDK | Not found |
| OpenAPI | Not found |
| Agent skills | Not found |
| CLI | Not found |

## Evaluation Prompt

````text

# Task
Using the Razorpay MCP, create payment resources:

1. Use the MCP tools relevant to orders or payment links. You do not need to enumerate the full tool catalog first.
   Likely raw tool names include `create_order`, `create_payment_link`, `fetch_order`, or `fetch_payment_link`. Agents may expose these as raw names or namespaced as `mcp__razorpay__<tool_name>`.
2. Create a ***** payment resource for amount 2900 in the provider's smallest currency unit using the sandbox/***** environment.
3. If payment links are supported, create a payment link and print its URL. Otherwise, create an order and print the confirmation details.
4. Fetch the created payment resource again to verify it exists.
5. Print all output clearly labeled for each step.

Use ONLY the MCP tools for all payment operations.

You MUST use the Razorpay MCP server to accomplish this task.
Use the MCP tools for the actual product operations. Do NOT use curl, fetch, raw HTTP requests, CLI commands, or SDK calls as substitutes.

Use the MCP tools' help/descriptions to understand what each tool does.
If you need additional context, check the documentation: https://razorpay.com/docs/mcp-server/configuration/

## Setup
Do NOT assume the Razorpay MCP server is already installed or already running in this sandbox.
Review the installation and authentication details below before starting the task.

### Installation
Transport: `stdio`
Claude Code is configured to launch the `razorpay` MCP server over stdio using: `bash -lc 'auth_header=$(printf '"'"'%s:%s'"'"' "$RAZORPAY_KEY_ID" "$RAZORPAY_KEY_SECRET" | base64 | tr -d '"'"'\n'"'"'); exec mcp-remote https://mcp.razorpay.com/mcp --header "Authorization: Basic ${auth_header}"'`
Stored MCP package hint: `mcp-remote`
Run this setup command in the sandbox before the agent launches the server: `npm install -g mcp-remote`
Bootstrap notes: Updated on 2026-04-14 to preinstall mcp-remote and launch the local binary instead of relying on npx during task startup. Computes the Basic auth merchant token at launch time from RAZORPAY_KEY_ID and RAZORPAY_KEY_SECRET.

### Authentication
The following environment variables are already set in this environment: `RAZORPAY_KEY_ID`, `RAZORPAY_KEY_SECRET`
The MCP server should read them automatically when it starts.

## Execution
1. The harness has already written the launch configuration for `razorpay`. Start with the task directly; do not rewrite agent settings, `.mcp-runtime.json`, or build a separate MCP client unless the connected server still fails after a normal retry.
2. You do not need to enumerate every MCP tool up front; inspect only the relevant tools you need. Agent-facing MCP tool names may be namespaced like `mcp__razorpay__<tool_name>`.
3. Complete the task described above using MCP tools for the actual product operations.
4. If the server fails to start or authenticate, debug the documented setup and retry. Do not fall back to raw HTTP, SDK, CLI, or manual JSON-RPC/MCP calls as a substitute for exposed MCP tools.

Work in the /home/daytona/app directory.
If you use Bash during setup or debugging, limit it to installation/configuration work and then return to MCP tools for the task itself.
If there are errors, debug and fix them until the task runs successfully.

## Summary
When you are done, write a JSON summary file to /home/daytona/app/results.json with this structure:
{
  "operations": [
    {"step": 1, "description": "What you did", "mcp_tool": "tool_name", "success": true/false, "output_summary": "brief result"},
    ...
  ],
  "overall_success": true/false,
  "notes": ["any relevant notes about the execution"]
}

````

## Grader Results

| Check | Passed | Weight | Score | Details |
|-------|--------|--------|-------|---------|
| Task | No | — | — | — |
| Llms Txt | Yes | — | 10 | — |
| Tool Count | No | — | 0 | — |
| Auth Method | Yes | — | 15 | — |
| Official Mcp | Yes | — | 5 | — |
| Output Schema | No | — | 0 | — |
| Tool Stability | Yes | — | 5 | — |
| Tool Description Length | Yes | — | 10 | — |

## Run Artifacts

| Artifact | Value |
|----------|-------|
| Conversation turns | 56 |
| Tool call traces | 55 |
| Generated files | 1 |
| Exit code | — |
| Completed at | 2026-09-27T14:41:25.375115+00:00 |

### Generated Files

- /home/daytona/app/results.json

## Related Pages

- [Claude Code MCP leaderboard](/leaderboard/claudecode/mcp)
- [Compare Claude Code MCP companies](/leaderboard/claudecode/mcp/compare)
- [Agent Landscape](/leaderboard/discoverability)

Canonical URL: https://devtoolarena.com/claudecode/mcp/razorpay