[@phantom/mcp-server] Agent wallet sim OK, signAndSend HTTP 403 submission-failed -32009 (funds stuck)

[ZombieKiller6969420]

Summary

Device-code agent wallet on @phantom/mcp-server 1.2.7: simulation OK, solana message sign OK, KMS signAndSendTransaction HTTP 403 type=submission-failed code=-32009 upstreamStatus=403. No outbound on-chain signature ever created.

Solana: 8SVW2VwuVWEXQP9fdnrRKP3gNAKpcbtxsJNxBpHgRnBu
Still holds 9.2 USDC + 0.046 SOL (checked 2026-08-27). Only two inbound funding txs.
walletId 7b92e618-5e47-589a-9681-93308d0d5c3c
org 13a5befe-882e-50d0-af4d-52eb8e75f993

Zendesk already escalated by Yaovi (DevRel) as request 329281 / 7VRMJ4-60MM5 on Aug 24. Still blocked. Need outbound unblocked or a signed raw tx for public RPC.

RequestIds: 0c8d83a2-094c-414f-bb87-154b0683de77, c2fea642-eb94-4c9c-9759-7dbad18fdaf0, eb7216af-5f5d-4c8d-a5be-b8ec6164c0c0

Example

No response

Steps to Reproduce

1. Create a device-code agent wallet via @phantom/mcp-server 1.2.7 (walletId 7b92e618-5e47-589a-9681-93308d0d5c3c, org 13a5befe-882e-50d0-af4d-52eb8e75f993).
2. Fund the Solana address 8SVW2VwuVWEXQP9fdnrRKP3gNAKpcbtxsJNxBpHgRnBu (two inbound txs; balance 9.2 USDC + 0.046 SOL).
3. Run a transaction simulation -> OK. Sign a Solana message -> OK.
4. Call KMS signAndSendTransaction -> HTTP 403, type=submission-failed, code=-32009, upstreamStatus=403. No outbound on-chain signature is ever created, so the funds are stuck.

RequestIds: 0c8d83a2-094c-414f-bb87-154b0683de77, c2fea642-eb94-4c9c-9759-7dbad18fdaf0, eb7216af-5f5d-4c8d-a5be-b8ec6164c0c0

Phantom Version

@phantom/mcp-server 1.2.7

Is there an existing discussion for this?

• I have searched the existing discussions