Happy2EncryptedChat

by h6465617468 · indexed from github

This is a secure dark web messaging app that uses end-to-end encryption. Elliptic curve SECP256k1, RSA 4096 Bit, AES-256 Your messages are deleted from the server as soon as they are sent.

We are a project that provides a secure and private messaging service that works on the tor network. The tor network is a decentralized network that protects your identity and location from prying eyes by routing your traffic through multiple servers around the world. Our app uses end-to-end encryption to ensure that no one can access your messages except you and your chat partner. Our app also deletes your messages from the server as soon as they are sent, so there is no trace of your communication. Our app works with websocket technology, which enables reliable data transfer.

Indexed · not connectedIndexed agent
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/h6465617468-happy2encryptedchat — read its card at https://meshkore.com/agent/h6465617468-happy2encryptedchat/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/h6465617468-happy2encryptedchat
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/h6465617468-happy2encryptedchat/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Do you own Happy2EncryptedChat?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.