_ registry / mcp streamable-http · checked 15h ago

redqueen-tts

https://ttskits.online

Registry code: 8a41960044f4fef8

api record

Text-to-speech with multiple engines and built-in voices. Use list_models to discover voices/languages and text_to_speech to synthesize with a built-in voice.

endpoint
https://ttskits.online/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is redqueen-tts live?
Yes — it answered the hub's last check (checked 15h ago). It answered 99% of checks over the last 30 days.
Is redqueen-tts free to use?
Yes — the hub reached it with no key and no payment.
What tools does redqueen-tts have?
3 tools: text_to_speech, list_voices, list_models.
Is redqueen-tts safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.7%

90 days 99%· all time 99%

latency
603ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 509 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • convert text to speech
  • list text-to-speech models
  • list available voices
takes → gives
text → audio
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
2 open 1 never probed 2 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_voices reads open 8d ago

    List the available voices per model (best-effort). Args: model: optional model id to filter to a single model.

    mcp-tool

    {
      "type": "object",
      "title": "list_voicesArguments",
      "properties": {
        "model": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Model",
          "default": null
        }
      }
    }
    arguments 18 lines
  • list_models reads open 8d ago

    List available TTS models with their languages and default voice. Returns a human-readable catalogue. Use the model ``id`` values with ``text_to_speech``.

    mcp-tool

    {
      "type": "object",
      "title": "list_modelsArguments",
      "properties": {}
    }
    arguments 5 lines
  • text_to_speech reads unknown never probed

    Synthesize speech from text using a built-in voice. Args: text: the text to speak. model: TTS model id (see list_models), e.g. kokoro, melotts, qwen3-tts-1.7b, cosyvoice3, indextts2, chatterbox. voice: voice id; omit to use the model's default. response_format: mp3 (default), wav, opus, aac, flac, or pcm. speed: speaking rate multiplier (1.0 = normal). language: optional language hint (e.g. en, zh, ja). Returns the synthesized audio.

    mcp-tool

    {
      "type": "object",
      "title": "text_to_speechArguments",
      "required": [
        "text"
      ],
      "properties": {
        "text": {
          "type": "string",
          "title": "Text"
        },
        "model": {
          "type": "string",
          "title": "Model",
          "default": "kokoro"
        },
        "speed": {
          "type": "number",
          "title": "Speed",
          "default": 1
        },
        "voice": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Voice",
          "default": null
        },
        "language": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Language",
          "default": null
        },
        "response_format": {
          "type": "string",
          "title": "Response Format",
          "default": "mp3"
        }
      }
    }
    arguments 52 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 8a41960044f4fef8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8a41960044f4fef8/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/8a41960044f4fef8/badge.svg)](https://brick.blue/agent/8a41960044f4fef8?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.