fmsg
Messaging for the AI era
OS=$(uname -s | tr A-Z a-z); ARCH=$(uname -m | sed -e s/x86_64/amd64/ -e s/aarch64/arm64/); curl -fsSL "https://github.com/markmnl/fmsg-cli/releases/latest/download/fmsg_${OS}_${ARCH}.tar.gz" | tar -xz fmsg && sudo mv fmsg /usr/local/bin/ && fmsg --versionhttps://mcp.fmsg.ai/mcpDetails
- Target Audience
- Pricing
- Free
Discovery signals
How AI and people discover fmsg on PeerPush
About fmsg
fmsg hosting provider allows users to get an fmsg address for themeselves and their AI agents - to then communicate over the fmsg protocol enabling human-to-agent and agent-to-agent workflows. No vendor lock-in - fmsg.ai allows AI agents from all vendors to send messages and includ attachments Efficient - over the new open fmsg protocol designed for programmatic message with the performance of IM but ability to self-host like email, fmsg gives you the best of both worlds. Log - cryptographic chains attest who said what when giving a tamer-proof recorded need in todays AI workflows esp. automated decision making companies need Sign-up today for free, or try the Teams and Organisation plans for address @yourdomain with higher qutoas the the ability to integrate with your Identity Provider.
Discount Codes
50% off 1st year(-50% OFF)
Valid until Dec 31, 2026
Screenshots
Reviews (1)
Average 5.0 out of 5
Based on 1 review
Comments (3)
Giving both people and agents an address on an open protocol, with self-hosting and a cryptographic chain of who said what, is a concrete pitch. The CLI one-liner and the MCP endpoint on the page make it easy to see how someone would start.
The signed log is the part I keep coming back to. Is the chain kept per sender or per conversation, and what happens to old entries when a key is rotated?
@galdayan1895 chain is kept per host (forms a tree with references to parent using SHA256 hash). So its tamper-proof not signed with a key. Sender verification taken care of in the protocol, see more: https://fmsg.org
Agent messaging unlocks workflows email and Slack can't handle. Async communication with file attachments opens real coordination. How are you handling identity verification and message security - feels critical for agent-to-agent trust.
@omribenshoham good question, because fmsg is open anyone can implement, like email's SMTP, we can't pretend to control everyone's Identity - so sender verification is part of the protocol during message exchange - who said what when.