Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/razorpay/razorpay-mcp-server/agents-mdgit clone --depth 1 https://github.com/razorpay/razorpay-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/razorpay/razorpay-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/razorpay/razorpay-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/razorpay/razorpay-mcp-server/agents-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.03435 | $0.03435 |
| Opus 5 | $0.01717 | $0.01717 |
| Sonnet 5 | $0.00687 | $0.00687 |
| Haiku 4.5 | $0.00344 | $0.00344 |
Grade A, and why
razorpay-mcp-server AGENTS.md scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Generate complete MCP tool implementations from Razorpay API docs, curl commands, or request/response examples. How it starts
The opening of the file, as written. The whole thing — 432 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
This file provides instructions for AI coding agents working on this repository.
Project Overview
This is a Go MCP (Model Context Protocol) server that wraps Razorpay APIs. Tools live in pkg/razorpay/, are registered in pkg/razorpay/tools.go, and tested alongside in *_test.go files.
Key Commands
make test # Run all tests
make fmt # Format code
make lint # Run golangci-lint
make build # Build the binary
Contributing
See CONTRIBUTING.md for branch naming (username/feature), commit format ([type]: description), and PR process.
Code Style
- 80-char line length max (lll linter)
goimportswith local prefixgithub.com/razorpay/razorpay-mcp-server- Full linter config in
.golangci.yaml
Razorpay MCP Tool Generator
Generate complete MCP tool implementations from Razorpay API docs, curl commands, or request/response examples.
Input Formats
The user may provide any of:
- Razorpay docs URL —
https://razorpay.com/docs/api/... - curl command — extract method, path, headers, body, and response
- Request/response JSON — raw payload and expected response
- SDK function signature — Go SDK function to call
If the tool name is not provided or cannot be inferred, ask the user before proceeding.
Workflow
Task Progress:
- [ ] Step 1: Parse input and extract API contract
- [ ] Step 2: Determine tool name and resource file
- [ ] Step 3: Implement tool function
- [ ] Step 4: Register tool in tools.go
- [ ] Step 5: Write unit tests
- [ ] Step 6: Update README.md Available Tools table
- [ ] Step 7: Run linter — fix errors
- [ ] Step 8: Run tests — fix errors
- [ ] Step 9: Create branch, commit, and open PR (if gh available)
Step 1: Parse Input
From docs URL: Fetch the page and extract endpoint path, HTTP method, required/optional params with types and descriptions, and example response.
From curl: Parse the method (-X), URL path, headers (-H), request body (-d), and note the response if provided.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 432 lines · 3,435 tokens per session scan A 733e2e03823c
razorpay-mcp-server AGENTS.md is an instructions file published in the GitHub repository razorpay/razorpay-mcp-server (230 stars, last pushed 8d ago), licensed MIT. It adds 3,435 tokens to every session, about $0.0172 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
robinhood-mcp AGENTS.md
Instructions for verygoodplugins/robinhood-mcp, covering agents.md, project overview, read-only is a hard invariant, build & development and install with dev dependencies (editable).
counterpoise-ledger CLAUDE.md
Instructions for jeffjjohnston/counterpoise-ledger, covering claude.md, project overview, development commands, essential commands and testing.
swiss-statistics-mcp CLAUDE.md
Claude Code instructions for malkreide/swiss-statistics-mcp, covering claude.md, teil 1 — portfolio-konventionen, vor der arbeit, tests and wenn etwas rot ist.
apra-mcp CLAUDE.md
Claude Code instructions for Bigred97/apra-mcp, covering apra-mcp, source, curated datasets (13), repo-specific module set and repo-specific gotchas.
agentservices-api AGENTS.md
AGENTS.md instructions for vbkotecha/agentservices-api, covering agent instructions — agentservices api, war time trade api, hyperliquid (first venue), trade invariants (all venues) and dual trade door — execution vs monetization.
ynab-budget-mcp AGENTS.md
AGENTS.md instructions for Orlando-Villanueva/ynab-budget-mcp, covering agents.md, purpose, project shape, core files and commands.