emailmd
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Ask Telegraph's ranked miners from any MCP client, no wallet. Morse pays; each answer has a receipt.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 8/8 | The cloud endpoint answered at the last check |
| Usage score | 20/100 |
Quality: Passed 5/5 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Morse — Telegraph in Telegram. Follow https://mcp.popnx.com/i/harshyadav442277-telegraph-morse.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 5/5 checks · What you ask goes through the maker’s server (telegraph-morse.vercel.app) · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 5 min
You need a Morse — Telegraph in Telegram key (create it on the maker’s site) · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
Morse — Telegraph in Telegramhttps://telegraph-morse.vercel.app/mcpUnder Request headers, add this name and value
AuthorizationBearer <paste your key here>Paste the key only into the app’s field, never into a chat or to anyone
Click Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsMorse — Telegraph in Telegram
Use Morse — Telegraph in Telegram and tell me what you can do for me, then show me one thing✓ If Claude says it is using Morse — Telegraph in Telegram or shows a Morse — Telegraph in Telegram tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Morse — Telegraph in Telegram yet
Morse — Telegraph in Telegram needs your own key to connect, but OpenAI’s help page only describes OAuth sign-in; there is no key option we could verify
A · Use an app that can connect Morse — Telegraph in Telegram
B · Others in Chat & email that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code · about 5 min
You need a Morse — Telegraph in Telegram key (create it on the maker’s site)
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user telegraph-morse https://telegraph-morse.vercel.app/mcp --header 'Authorization: Bearer your-value'Replace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Morse — Telegraph in Telegram listed as connected
Use Morse — Telegraph in Telegram and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Morse — Telegraph in Telegram or shows a Morse — Telegraph in Telegram tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 5 min
You need a Morse — Telegraph in Telegram key (create it on the maker’s site)
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
In the Morse — Telegraph in Telegram settings, Authorization is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Morse — Telegraph in Telegram and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Morse — Telegraph in Telegram or shows a Morse — Telegraph in Telegram tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 5 min
You need a Morse — Telegraph in Telegram key (create it on the maker’s site)
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
In the Morse — Telegraph in Telegram settings, Authorization is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Morse — Telegraph in Telegram and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Morse — Telegraph in Telegram or shows a Morse — Telegraph in Telegram tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://telegraph-morse.vercel.app/mcpJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user telegraph-morse https://telegraph-morse.vercel.app/mcp --header 'Authorization: Bearer your-value'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"telegraph-morse": {
"url": "https://telegraph-morse.vercel.app/mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"telegraph-morse": {
"type": "http",
"url": "https://telegraph-morse.vercel.app/mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}Descriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account Harshyadav442277, which owns the repo
Code last changed 19 days ago
Uses MIT
Responded in 2072 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/harshyadav442277-telegraph-morse)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed 19 days ago, and the latest version (0.1.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Build and fix Discord bots from a chat. Kite hosts them 24/7, with no code to deploy.
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.
CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.
| This one Morse — Telegraph in Telegram | emailmd | Kite Discord Bot Builder | e2a — email for AI agents | Infobip MCP | kernelCAD | |
|---|---|---|---|---|---|---|
| Runs where | Runs in the cloud, nothing to install | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | Yes | No |
| Basic checks | 5/5 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | MIT | AGPL-3.0 | Apache-2.0 | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A Telegraph Hackathon Season I, Track 3 application. Live: [https://telegraph-morse.vercel.app](https://telegraph-morse.vercel.app) · public ledger · API & MCP
Telegraph in Telegram. Ask, get an answer from a ranked miner, with a receipt. Send a question to the bot — no wallet, no key, no sign-up — and Telegraph's own router classifies it and picks a ranked miner (Morse falls back to its own routing only when the router does not answer), Morse pays the x402 fee from one app-owned wallet, and the answer comes back with a receipt: the miner that served it, the intent and why it was chosen, that miner's rank, its confidence, the cost, the latency, the on-chain settlement transaction, and a signal_hash you can verify on the node. The same thing is on the web and behind one hosted MCP/REST endpoint for agents.
Live example, 2026-09-02: LiveCert #1 for SSL_VERIFICATION, $0.01, signal 0x0691ca3f…0821a1, settled on-chain as 0x31b9b480…2af007.
Every call Morse makes is in a public ledger, so "people used it" is checkable rather than claimed.
What Morse deliberately does not do. It does not re-rank miners. Telegraph's leaderboard is the consensus and the router's pick is the answer, so there is no podium, no automatic second opinion and no consensus report. Those were built, measured and retired on 2026-09-04 after an organizer pointed out that paying several miners per question to re-derive the ranking is what the protocol already does once for everyone, does not work economically for a user, and looks like spam. The ledger keeps their rows, labelled; the code leaves before the freeze (GAPS G32).
One check that does not rely on Morse's word. /proof reads the payer wallet's USDC transfers on Base Sepolia from a public indexer and matches them, hash for hash, against the ledger's settlement transactions — the "actual volume of Telegraph calls" counted from the chain, with any settlement the ledger lacks shown rather than hidden. It is computed from data that already exists and spends nothing.
Not an aggregator. Morse does not pick providers or blend answers. Telegraph's ranked router picks the miner; Morse pays and keeps the receipt. When you *do* want a specific miner — the dispatch the organizers' own reference apps use — name it: telegraph_ask_miner over MCP, {"miner": "livecert", "question": "…"} on REST, /miner livecert in Telegram. The receipt says routing was bypassed at your request.
Consuming Telegraph today needs a wallet, testnet USDC from a faucet, and an x402 client. That keeps out everyone who is not already a developer with a burner key, and it means the network's "real usage" is mostly machines calling one miner. Morse is the missing front door, and because every answer carries a verifiable receipt, its usage is evidence rather than a claim.
Get a free key at /keys, then:
claude mcp add --transport http morse https://telegraph-morse.vercel.app/mcp --header "Authorization: Bearer morse_YOURKEY"
Then ask Claude anything the network can answer — *"use telegraph_ask: is the TLS certificate for github.com valid, and who issued it?"*, then *"use telegraph_verify_signal on that signal_hash"*. Tools: telegraph_ask, telegraph_ask_miner, telegraph_recipe, telegraph_verify_signal. Intents and leaderboards are free over REST at /v1/intents and /v1/leaderboard/{INTENT}; the three MCP discovery tools that duplicated Telegraph's explorer were removed on 2026-09-05.
{
"mcpServers": { "morse": { "url": "https://telegraph-morse.vercel.app/mcp", "headers": { "Authorization": "Bearer morse_YOURKEY" } } } }
curl -X POST https://telegraph-morse.vercel.app/api/keys -H "content-type: application/json" -d '{"label":"my-laptop"}'
curl -X POST https://telegraph-morse.vercel.app/v1/ask -H "Authorization: Bearer morse_YOURKEY" -H "content-type: application/json" -d '{"question":"What is the current weather in Chennai?"}'
Ask one named miner directly (miner authors: your own slug goes here):
curl -X POST https://telegraph-morse.vercel.app/v1/ask -H "Authorization: Bearer morse_YOURKEY" -H "content-type: application/json" -d '{"miner":"livecert","question":"Is the SSL certificate for github.com valid?"}'
Free, no key needed — the discovery endpoints and the ledger:
curl -s https://telegraph-morse.vercel.app/v1/intents
curl -s https://telegraph-morse.vercel.app/v1/leaderboard/SSL_VERIFICATION
curl -s https://telegraph-morse.vercel.app/api/stats
[https://t.me/MyMorse_Bot](https://t.me/MyMorse_Bot) — /start shows tappable example questions; answers free text. Commands: /miner , /safe, /wallet, /weather, /fact, /verify, /stats. Every answer carries the same receipt the web and API surfaces return, and lands in the same public ledger. In a group, Morse answers only when it is @mentioned or replied to, so a busy chat never pays for answers nobody asked for.
| field | meaning |
|---|---|
minerSlug, minerId | which miner the Engine routed to |
intent | the canonical intent the router classified the question as |
minerRank | that miner's current leaderboard rank for the intent |
routedBy | engine when Telegraph's router chose the miner, morse when the fallback did |
routerReasoning | the router's stated reason, or which fallback rule fired |
settlementTx | the USDC transfer on Base Sepolia, from the node's payment-response header |
confidence | the miner's own confidence, read from its declared signal_mapping — or "not reported" |
costUsd, durationMs | what the call cost and how long it took |
signalHash | verify at /verify/{hash}, or on the node at GET /engine/v1/signal/{hash} |
/verify/{hash} shows the node's record, the payer wallet and whether it is Morse's, the node's own keccak256-over-payload attestation, and the payload the hash covers. The node does not publish a per-call settlement transaction (0 of 8 user-paid signals sampled on 2026-09-02 carried one), so the on-chain trail is the payer wallet's USDC history on BaseScan, which Morse links.
git clone https://github.com/Harshyadav442277/telegraph-morse && cd telegraph-morse && npm ci
npm run typecheck && npm test
cp .env.example .env && npm run dev
Without EVM_PRIVATE_KEY and a non-zero DAILY_BUDGET_CALLS, asking is refused with an honest message; the site, the ledger and the free discovery endpoints all still work. The end-to-end judge journey runs against any deployment:
npm run e2e
That suite is free to run. The single paid step is gated behind MORSE_E2E_PAID=1 so no schedule can manufacture traffic.
keccak256 over the payload and reports verified: true; eleven serialisations of the payload as served failed to reproduce it, so Morse displays that attestation rather than claiming to have recomputed it (GAPS G3). What Morse establishes independently is the payer: the wallet on the record, checked against its own.MIT