Your dApp isn't broken. It's lying.
The page loads and the node answers, but the balance says zero. DApp Doctor finds out why: the wrong network, a lagging node, or a contract that isn't there. Get a verdict in seconds.
Misconfigured dApps don't crash. They show the wrong numbers.
The wrong network.
Your app was built for Base Sepolia. Your RPC answers Base Mainnet. Every read succeeds, and every read is wrong.
A lagging node.
It answers every call on time, with state that stopped being true a minute ago.
A contract that isn't there.
The address has no code on this network, so reads come back empty, and your interface shows zeros as if they were data.
Six checks. Read-only. Seconds.
RPC access
Does the URL answer as a node? If not, is it DNS, a timeout, a rate limit, or a JSON-RPC error? Each one needs a different fix.
Network identity
Is the node on the network your app expects?
Node freshness
Is its latest block recent, or is it serving stale state?
Contract bytecode
Is there actually a contract at that address, on this network?
Critical read
Does the contract answer the call your app makes, in the shape your app expects?
Fallback RPC
Does your backup answer, and is it on the same network? A backup on the wrong chain fails silently the day you need it.
A verdict you can act on.
- READY
All six checks passed.
- AT RISK
Nothing critical failed, but something needs attention or could not be checked.
- BLOCKED
A critical check failed. The verdict names the root cause, not a list of symptoms.
Not tested never counts as passing.
Every failure comes with what to do about it.
One report proves nothing. Two do.
Run the broken setup and the fixed one side by side. DApp Doctor shows which checks your fix resolved, and names any it broke.
Before
BLOCKEDAfter
READY| Check | Before | After | Change |
|---|---|---|---|
| Network identity | FAIL | PASS | fixed |
| Fallback RPC | NOT TESTED | PASS | fixed |
Bring your config the way you have it.
Fill in the details
Enter the RPC URL, the network your app expects, and optionally a contract and a fallback.
Ask your agent
Connect DApp Doctor to Claude Code or Cursor as an MCP server. Your agent reads the project and runs the diagnosis.
claude mcp add --transport http dapp-doctor https://dapp-doctor.vercel.app/api/mcp
Pro keeps the chart.
Every diagnosis is saved, so you can see when a configuration broke and prove when it was fixed.
- Saved diagnosis history.
- Launch Check: a stricter bar before you go to mainnet.
- Monthly
- USD9.99per month
- Yearly
- USD79.99per year
- Lifetime
- USD99.99one-time
During the hackathon, purchases are RevenueCat Test Store transactions. No card is charged.
Read-only by design.
No private keys, no seed phrases, no transactions. The only calls DApp Doctor makes are reads: eth_call, eth_getCode, eth_chainId, eth_blockNumber and eth_getBlockByNumber.
It refuses private and internal network addresses before opening a connection, so it cannot be turned against the infrastructure it runs on.
The code is open source.