Repository navigation
Remote paid MCP server compatible with withX402Client: NOVA (x402, USDC on Base mainnet) #2686
jessicaespinal777-cloud
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi all, I'm Jessica. I built NOVA, a remote MCP server whose paid tools follow the same x402 MCP transport spec as the
examples/x402-mcpdemo. That means an agent wrapped withwithX402Clientshould be able to pay for them without custom code.Endpoint: https://nova-agent-output-recovery.onrender.com/mcp (stateless Streamable HTTP)
nova_catalog: free, lists each tool with its price and an example inputrecover_agent_output, $0.01: repairs malformed LLM/tool-call JSON and validates it against an optional JSON Schemacompany_intelligence_report, $0.25: source-linked company profile from a public websitecited_research_brief, $0.99: research memo with 5–8 cited public sourcesAn unpaid
tools/callreturns the PaymentRequired object. Retrying with_meta["x402/payment"]settles the payment before the tool runs. One difference from the demo: NOVA settles real USDC on Base mainnet (eip155:8453), not Base Sepolia, so the client's network config needs to allow that.It's listed on Glama: https://glama.ai/mcp/connectors/io.github.jessicaespinal777-cloud/nova
If anyone tries it with
withX402Client, I'd really like to hear whether the flow works end to end, or what breaks.All reactions