[Osraka]

Summary

erigon://network/status currently ignores an eth_syncing RPC error and serializes the default syncing: false. That makes an unavailable sync status look like a fully synced node.

Return the RPC error with its method name instead. Successful false and progress-object responses are unchanged. This does not change how the other fields handle partial data.

Verification

• Added TestResourceNetworkStatusDoesNotClaimSyncedOnRPCFailure; it failed on unmodified main and passes with this change.
• go test ./rpc/mcp -count=1
• make lint
• make erigon integration

[Copilot]

🟢 Approval recommended

No active review issues are reported for the change to surface eth_syncing failures rather than a misleading synced status.

No open issues 🎉

What changed in this PR

This PR prevents the MCP network-status resource from reporting syncing: false when the eth_syncing RPC fails. Successful responses and partial-data handling for other fields remain unchanged.

Changes:

• Return eth_syncing errors with the method name while preserving the underlying error.
• Add a regression test that checks an RPC failure returns an error and no resource contents.

File	Description
rpc/​mcp/​resources.go	Propagates eth_syncing errors from the network-status handler.
rpc/​mcp/​resources_test.go	Tests that an RPC failure cannot produce a misleading synced status.

_{Review effort: Balanced}