Yieldagentx402 runs on your own machine — the client starts it, so there is no endpoint to ping. 67 installs a week from npm. Last commit 19 May 2026.
Policy-gated x402 MCP for agent workflows with TEE receipts, 18 tools, and no custody.
What the code does
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
proc = subprocess.run(
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add yieldagentx402 -e 'YAX_API_KEY=<YAX_API_KEY>' -e 'YAX_AGENT_ID=<YAX_AGENT_ID>' -- npx -y agentx402-mcp-server{
"mcpServers": {
"yieldagentx402": {
"command": "npx",
"args": [
"-y",
"agentx402-mcp-server"
],
"env": {
"YAX_AGENT_ID": "<YAX_AGENT_ID>",
"YAX_API_KEY": "<YAX_API_KEY>"
}
}
}
}[mcp_servers.yieldagentx402]
command = "npx"
args = ["-y", "agentx402-mcp-server"]
env = { YAX_API_KEY = "<YAX_API_KEY>", YAX_AGENT_ID = "<YAX_AGENT_ID>" }{
"mcpServers": {
"yieldagentx402": {
"command": "npx",
"args": [
"-y",
"agentx402-mcp-server"
],
"env": {
"YAX_AGENT_ID": "<YAX_AGENT_ID>",
"YAX_API_KEY": "<YAX_API_KEY>"
}
}
}
}{
"servers": {
"yieldagentx402": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"agentx402-mcp-server"
],
"env": {
"YAX_AGENT_ID": "<YAX_AGENT_ID>",
"YAX_API_KEY": "<YAX_API_KEY>"
}
}
}
}Put your own values in place of
<YAX_API_KEY> (YieldAgentX402 API key from https://yieldagentx402.app/apply), <YAX_AGENT_ID> (Your agent ID from the dashboard).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
YAX_MCP_ENDPOINT (Optional full MCP endpoint override (default: https://api.yieldagentx402.app/mcp)).
Alternatives to Yieldagentx402
same job, measured the same wayAgentic rails for complex workflows with receipts, fees, and MCP tool access.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Free public MCP for AI agents — 193 tools, 44 workflows. No API key.
MCP server for agent task workflows with phases, prompts, gates, and multi-agent coordination
Store, retrieve, and pin encrypted files on IPFS via MCP tools for AI agents and workflows
MCP server for the @agentutility browser-workflow cluster — pay-per-call x402 tools, no API keys…
Authenticated MCP server for ClearPolicy policy and compliance workflows.
Fail-closed quality gate and hash-chained receipt ledger for AI agent workflows.
Yieldagentx402 — questions
Answers built from our own checks of this server.