Overview
JMP.chat is a privacy-centric telecommunications bridge that assigns real US or Canadian phone numbers and delivers them over the open XMPP (Jabber) network. Rather than forcing users into conventional carrier ecosystems, the service lets you send and receive text messages, picture messages, and voice calls, including voicemails transcribed to text, through any compatible XMPP client. The model is deliberately unconventional: no mobile app lock-in, no SIM card, and no binding contract. Users can run multiple numbers through a single client, making it straightforward to compartmentalize personal, professional, and temporary contacts. The service has been operational since 2017 and is built entirely on free-software infrastructure, with source code available for inspection and modification.
Pricing is straightforward at $4.99 per month. New accounts can receive texts and calls immediately, but must first receive at least one message from another person before they can initiate outbound SMS or place calls, a friction point designed to mitigate abuse. Number porting is supported for existing US and Canadian lines, and the service explicitly disclaims 911, 112, or other emergency routing, noting that even SIM-less handsets can typically reach emergency services directly.
Privacy & KYC
JMP.chat sits at KYC Tier L1: fully anonymous and pseudonymous. No email address, legal name, or government ID is required to establish service. You select a number and pay, ideally with Monero or Bitcoin via Lightning, leaving minimal financial fingerprint. This makes it one of the rare telecom providers that genuinely caters to users seeking no-KYC communication infrastructure.
However, the privacy picture contains meaningful caveats. Because JMP.chat bridges to the legacy phone network, all SMS and voice content traverses unencrypted carrier infrastructure beyond the service's control. Metadata and message content are exposed to upstream telcos, regulatory capture, and potential interception. JMP.chat is transparent about this limitation, noting that TLS encryption protects traffic between your device and their servers (and between XMPP hops), but cannot extend into the PSTN. For users whose threat model includes state-level actors or sophisticated supply-chain attacks, the service recommends migrating sensitive conversations to pure XMPP with OMEMO encryption, bypassing the phone network entirely.
- No personal data collected at signup
- IP logging policy not explicitly detailed; Tor access available for connection-layer anonymity
- Content unencrypted on PSTN leg; encrypted in transit to JMP servers
- Open-source stack permits independent audit
Supported assets & payments
JMP.chat accepts a deliberately privacy-friendly mix of payment rails. Cryptocurrency users can settle with Monero, Bitcoin, or Lightning Network transactions, aligning with the service's no-KYC ethos. Traditional fiat and cash payments are also accommodated, broadening accessibility for users who prefer or require non-digital settlement. The inclusion of Monero is particularly notable, few telecom services support the privacy coin natively, and its ring-signature architecture provides stronger transactional anonymity than transparent ledger alternatives.
Security & custody
JMP.chat operates as a non-custodial communications gateway in the sense that you control your XMPP identity and client choice, but the phone numbers themselves are provisioned through JMP.chat's carrier relationships. There is no "wallet" or stored balance to secure; it is a subscription service rather than a financial custodian. The security model therefore hinges on XMPP client hygiene and payment op-sec rather than key management. Users select their own Jabber server or rely on a trusted provider, meaning compromise of JMP.chat's infrastructure does not automatically expose message history if end-to-end encryption is employed for pure XMPP conversations. For the telephony bridge specifically, the service's transparency about its threat model and data-retention practices allows informed risk assessment.
Community sentiment emphasizes responsive human support and reliable XMR payment processing. Users report successful number recovery and prompt assistance, though some note geographic restrictions, Canadian number availability appears more limited than US options in practice.
Who it's for, verdict
JMP.chat is purpose-built for privacy-conscious individuals, activists, journalists, and crypto-native users who need functional phone numbers without surrendering identity. Developers and system administrators appreciate the protocol-level flexibility: any XMPP client becomes a full-featured SMS and voice terminal. The service also suits temporary or project-based use cases, disposable numbers for registrations, short-term campaigns, or compartmentalized identities.
It is not a drop-in replacement for mainstream mobile service. The lack of emergency calling, the inbound-message prerequisite for outbound functionality, and the technical overhead of XMPP configuration create friction for casual users. Those demanding seamless, app-based convenience will find traditional VoIP apps more approachable. But for the audience that values pseudonymity over polish, JMP.chat delivers a rare combination of real PSTN interoperability and genuine anonymity. We score it 8/10 overall, with the gap reflecting inherent limitations of bridging to an unencrypted phone network rather than service failures.
