Merchant Check MCP server
{
"mcpServers": {
"gradientdecisions-merchant-check": {
"type": "http",
"url": "https://mcp.gradientdecisions.com/mcp"
}
}
}{
"mcpServers": {
"gradientdecisions-merchant-check": {
"type": "http",
"url": "https://mcp.gradientdecisions.com/mcp"
}
}
}{
"mcpServers": {
"gradientdecisions-merchant-check": {
"type": "http",
"url": "https://mcp.gradientdecisions.com/mcp"
}
}
}{
"servers": {
"gradientdecisions-merchant-check": {
"type": "http",
"url": "https://mcp.gradientdecisions.com/mcp"
}
}
}{
"mcpServers": {
"gradientdecisions-merchant-check": {
"type": "http",
"url": "https://mcp.gradientdecisions.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
An MCP server that evaluates merchant trust on-chain before x402 payments are made. Agents call the check_merchant tool (charged $0.01 per query via x402) to assess unfamiliar merchants on Base and Solana before deciding whether to pay them.
- Check the on-chain payment history and signals of a merchant address before sending an x402 payment to it.
- Integrate merchant evaluation into an autonomous agent's payment decision flow as a pre-payment step.
- Access merchant recommendation scores and risk signals for both Base and Solana-based merchants.
Tools this server exposes
| Tool | Does |
|---|---|
| check_merchant | Evaluates observable on-chain payment behavior for a merchant address, returning recommendation score and risk signals; charged $0.01 per call via x402. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.