Echo

com.thetempleofdoom.echo-mcpPublished by echo-mcp.thetempleofdoom.comOfficial publisherv1.0.0Updated Oct 24, 2026

Text-to-speech API: neural voices, pay-per-credit in Bitcoin sats via BTCPay.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote text-to-speech service that turns text into speech with neural voices, paid per credit in Bitcoin sats via BTCPay.

What you can do
  • Convert text into spoken audio using neural voices.
  • Spend credits for each synthesis, with credits purchased in Bitcoin sats through BTCPay.
  • No tool list is published, so the exact operations and voice options are not documented in the supplied material.
When to use it
When an assistant needs to produce spoken audio from text and the user is willing to pay per credit in Bitcoin sats rather than use a subscription-based TTS provider.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. No authentication, environment variables or headers are declared, though credits must be obtained through BTCPay to use the service.
Before you install
Usage is billed per credit and credits are bought with Bitcoin sats, so calls can cost real money; confirm pricing and credit handling before use. The endpoint declares no authentication, so consider what text you send to a third-party service.

Installation

In SourceWeft

  1. Open Echo in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.thetempleofdoom.echo-mcp%2Fecho/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "echo": {
      "type": "http",
      "url": "https://echo-mcp.thetempleofdoom.com/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 23, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.