Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Doppelreim Rhymes

REMOTE · API.DOUBLE-RHYME.COM

Multisyllabic, vowel and classic rhymes plus rhyming lines in 56 languages for lyrics and poems.

+3 this week 84 Trust /100

Last scanned (16 hours ago)

Scores higher than 89% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 717 tokens (~358/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://api.double-rhyme.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=double-rhyme.com CN=WR3,O=Google Trust Services,C=US 12 Oct 2026 10 Jan 2027 RSA 2048 SHA256-RSA c5f09464fa27919212dc2482f2ae1c2f
SANs: double-rhyme.com, api.double-rhyme.com, www.double-rhyme.com, florianhoenicke.com, www.florianhoenicke.com, doppel-reim.de
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d
CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 1 Sept 1998 28 Jan 2028 RSA 2048 SHA1-RSA 40000000001154b5ac394

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.double-rhyme.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
double-rhyme.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31556926

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.double-rhyme.com/mcp Verified 200
http (plaintext) http://api.double-rhyme.com/mcp HTTPS enforced 301 https://api.double-rhyme.com/mcp
MCP tools · 2 exposed · ~520 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
find_rhymes ~286

Find rhymes for a word or short phrase. type "double" = multisyllabic rhymes (best for rap and poetry), "classic" = perfect end rhymes grouped by matching syllables, "vowel" = assonance (same vowel sounds). 50+ languages; strongest results come first.

NameTypeReqDescription
languagestring–Language code. Supported: af, ar, az, bg, bs, ca, cs, cy, da, de, el, en-us, eo, es, es_lat, et, eu, fa, fi, fr, fr_be, fr_ch, hi, hr, hu, hy, hy_arevmda, id, it, ka, kn, ko, la, lt, lv, mk, ml, ms,…
limitinteger–Maximum results per group.
typestring–Kind of rhyme.
vocabularystring–"rap" draws from rap lyrics (de and en only), "general" from general language.
wordstringyesWord or short phrase to rhyme on, e.g. "verloren" or "heart".
NameTypeReqDescription
groupsarrayyes–
languagestringyes–
typestringyes–
vocabularystringyes–
wordstringyes–

No examples provided.

find_rhyming_lines ~234

Find real lines (lyrics, proverbs, sayings) that end with a rhyme on the given word. Useful as inspiration for the next line of a verse.

NameTypeReqDescription
languagestring–Language code. Supported: af, ar, az, bg, bs, ca, cs, cy, da, de, el, en-us, eo, es, es_lat, et, eu, fa, fi, fr, fr_be, fr_ch, hi, hr, hu, hy, hy_arevmda, id, it, ka, kn, ko, la, lt, lv, mk, ml, ms,…
limitinteger–Maximum number of lines.
vocabularystring–"rap" uses rap lyrics (de and en only), "general" uses proverbs and general texts.
wordstringyesWord the lines should rhyme with.
NameTypeReqDescription
groupsarrayyes–
languagestringyes–
typestringyes–
vocabularystringyes–
wordstringyes–

No examples provided.

Install

How do I install the Doppelreim Rhymes MCP server?

Doppelreim Rhymes is a hosted endpoint at https://api.double-rhyme.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.double-rhyme.com

# add to Claude Code
claude mcp add --transport http com-double-rhyme-rhymes 'https://api.double-rhyme.com/mcp'
Common questions

What is the Doppelreim Rhymes MCP server?

Doppelreim Rhymes is an MCP server listed in the public MCP registry as com.double-rhyme/rhymes. Multisyllabic, vowel and classic rhymes plus rhyming lines in 56 languages for lyrics and poems. This page covers its hosted endpoint (https://api.double-rhyme.com/mcp).

Is the Doppelreim Rhymes MCP server safe to use?

Doppelreim Rhymes scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Doppelreim Rhymes MCP server expose?

Doppelreim Rhymes exposes 2 tools: find_rhymes, find_rhyming_lines. Their descriptions and schemas cost roughly 520 tokens of context every time the server is loaded.

Does the Doppelreim Rhymes MCP server require authentication?

No. We connected to Doppelreim Rhymes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Doppelreim Rhymes MCP server still maintained?

Doppelreim Rhymes is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Doppelreim Rhymes MCP server?

VerifyMCP ran 13 checks on Doppelreim Rhymes, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.