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.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 20/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Morse — Telegraph in Telegram。按照 https://mcp.popnx.com/i/harshyadav442277-telegraph-morse.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(telegraph-morse.vercel.app) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 5 分钟
需要 Morse — Telegraph in Telegram 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Morse — Telegraph in Telegramhttps://telegraph-morse.vercel.app/mcp在 Request headers 下添加这个名称和值
AuthorizationBearer <在这里粘贴你的密钥>只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsMorse — Telegraph in Telegram
用 Morse — Telegraph in Telegram 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Morse — Telegraph in Telegram,或回答中出现 Morse — Telegraph in Telegram 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Morse — Telegraph in Telegram
Morse — Telegraph in Telegram 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式
A · 使用能连接 Morse — Telegraph in Telegram 的应用
B · 聊天与邮件 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code · 约 5 分钟
需要 Morse — Telegraph in Telegram 的密钥(在开发者网站创建)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user telegraph-morse https://telegraph-morse.vercel.app/mcp --header 'Authorization: Bearer your-value'按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 Morse — Telegraph in Telegram 在列表中并显示已连接
用 Morse — Telegraph in Telegram 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Morse — Telegraph in Telegram,或回答中出现 Morse — Telegraph in Telegram 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 5 分钟
需要 Morse — Telegraph in Telegram 的密钥(在开发者网站创建)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
在 Morse — Telegraph in Telegram 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Morse — Telegraph in Telegram 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Morse — Telegraph in Telegram,或回答中出现 Morse — Telegraph in Telegram 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 5 分钟
需要 Morse — Telegraph in Telegram 的密钥(在开发者网站创建)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
在 Morse — Telegraph in Telegram 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Morse — Telegraph in Telegram 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Morse — Telegraph in Telegram,或回答中出现 Morse — Telegraph in Telegram 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://telegraph-morse.vercel.app/mcpJSON 设置在下方“开发者专用”中
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"
}
}
}
}说明仍为英文原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 Harshyadav442277 验证,该账户拥有此仓库
代码最后更新于19天前
使用 MIT
在 2072 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/harshyadav442277-telegraph-morse)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于19天前,最新版本(0.1.0)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
| 本项 Morse — Telegraph in Telegram | emailmd | Kite Discord Bot Builder | e2a — email for AI agents | Infobip MCP | kernelCAD | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 5/5 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | AGPL-3.0 | Apache-2.0 | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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