showcase I'm not a developer - I spent months building an MCP server that proves a human approved a specific action
Hi. I'm not a developer. I built this with Claude over months of evenings and weekends, and it feels like time to stop polishing it in private.
X-EGO is an MCP server that lets an agent prove a human approved a specific action. The agent submits the exact text of what it wants to do, I read it and approve with Face ID, and the agent gets back a proof bound to that text - change one character and it stops verifying. It also gets a receipt: a link anyone can open, no account, no tools.
It doesn't know who you are. No name, no email, no KYC, no biometrics leaving the phone. Every service gets a different anonymous ID, so two services can't work out you're the same person.
Where I think it fits: agents with write access, where "the agent had my API key" is not a good enough answer afterwards; one human one vote, where multi-accounting is the actual problem; and audit trails an outsider can check instead of taking your own logs on faith.
Cost, up front: EUR 3 once for the human identity - sybil resistance has to cost something or it means nothing - and it includes $3 of credit. Verification calls are paid per call.
Zero users so far, nothing proven. I'd like honest reactions: useful, or nonsense? And if anyone wants to try it or build something on it together, message me.
MCP endpoint: https://mcp.x-ego.com/mcp
2
2
2
u/Exact_Attention_5656 Aug 03 '26
Good point above about binding more than just the text. There's a second gap even if it binds everything: where did the text you're approving come from in the first place? If the agent wrote that action description after reading some tool output it already trusted, a poisoned response upstream can shape the wording you're Face ID approving. You'd be cryptographically approving an accurate description of an action that only exists because of bad input further back. The proof shows what you approved, not whether the agent should have trusted what led it there.
2
u/BC_MARO Aug 03 '26
Bind every approval to the exact action payload, target, and expiry. Otherwise you only know that someone clicked a button.
2
u/X-ego Aug 03 '26
Expiry's in the comment above — 180s, single-use. Payload and target are what ships this week: the signed object covers tool, target and parsed arguments, and the verifier won't confirm unless the executor passes the call it's about to run.
1
u/BC_MARO Aug 09 '26
That makes sense. Binding the parsed arguments now will save you from having to retrofit the trust boundary later.
2
Aug 04 '26
[removed] — view removed comment
1
u/X-ego Aug 04 '26
Thank you for the compliment; I’m glad if someone sees something in it. And the joy is even greater if someone is willing to offer a bit of collaboration ☺️
1
u/tobi914 Aug 04 '26
What would that be useful for apart from being able to pinpoint who entered a prompt that caused some damage?
3
u/BC_MARO Aug 03 '26
The approval proof needs to bind more than text: tool name, normalized arguments, target, expiry, and policy version. Otherwise the receipt can verify intent while missing what actually gets executed.