Cline 402MCP.org — HTTP 402 & Agent Payment Registry decode_402_challenge
How to: Cline 402MCP.org — HTTP 402 & Agent Payment Registry decode_402_challenge
Add 402MCP.org — HTTP 402 & Agent Payment Registry to Cline
-
01
Open ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"registry": {
"url": "https://402mcp.org/api/v1/mcp"
}
}
}-
02
Save the file and restart Cline.
-
03
Ask for something decode_402_challenge does. Cline lists the server's tools on connect and calls decode_402_challenge itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that 402MCP.org — HTTP 402 & Agent Payment Registry's identifier in your config matches the one above exactly.
Cline's MCP Servers pane edits this file for you if you would rather not find it. Cline docs
Set these first
402MCP.org — HTTP 402 & Agent Payment Registry will not start until these are set, so decode_402_challenge never becomes available.
-
MCP_402_OFFLINE
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 16 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.