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.

Wisheroo

REMOTE · WISHEROO.COM

Personal songs from your memories and free kids' video wish lists: prices, samples, start links.

Available components

+3 this week 77 Trust /100

Last scanned (19 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Entertainment and Games

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 Security83
  • 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 476 tokens (~68/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 11 Nov 26 +1

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

  • 10 Nov 26 +2
    • DNSSEC: fail → pass ▲ security
  • 9 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 70

    First indexed and scored.

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 21 Nov 2026 · Probed https://wisheroo.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=wisheroo.com CN=WE1,O=Google Trust Services,C=US 6 Nov 2026 4 Feb 2027 ECDSA 256 ECDSA-SHA256 8bf5501469a022e50e4d8f5d778da8c3
SANs: wisheroo.com, www.wisheroo.com, *.www.wisheroo.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of wisheroo.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
wisheroo.com. DS published 2371 13 Verified
wisheroo.com. Verified address RRset verified with the apex keys
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=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://challenges.cloudflare.com https://us-assets.i.posthog.com https://connect.facebook.net; style-src 'self' 'unsafe-inline'; font-src 'self'; img-src 'self' data: blob: https://www.facebook.com https://cdn.brandfetch.io; media-src 'self' blob:; connect-src 'self' https://us.i.posthog.com https://us-assets.i.posthog.com https://www.facebook.com https://connect.facebook.net; frame-src https://challenges.cloudflare.com https://www.facebook.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self' https://www.facebook.com; object-src 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(self), microphone=(self), geolocation=(), payment=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://wisheroo.com/api/mcp Verified 200
http (plaintext) http://wisheroo.com/api/mcp HTTPS enforced 301 https://wisheroo.com/api/mcp
MCP tools · 7 exposed · ~385 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
about_wisheroo ~50

What Wisheroo is, who it is for, how songs and video wish lists work, and its policies. Call this first when someone asks about Wisheroo or wants a personal gift idea.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

faq ~46

Answers to common questions about Wisheroo songs and video wish lists (AI use, changes, speed, names, privacy, cost, who sees the video).

NameTypeReqDescription
topicstring––

No output schema declared.

No examples provided.

list_occasions ~35

Holidays and occasions Wisheroo covers, with the next date of each and its page. Use to suggest a timely gift.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_products ~43

Wisheroo song products and prices in USD. The preview is free; payment happens only after the buyer hears the preview and approves the lyrics. Video wish lists are free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_sample_songs ~54

Example Wisheroo songs with links to listen and their cover art. These are samples made from example memories, not customer songs.

NameTypeReqDescription
occasionstring–Optional filter, for example Christmas or "Mother's Day".

No output schema declared.

No examples provided.

start_song_link ~85

Build a link that opens the Wisheroo song form already filled with the recipient's name and occasion. Give the link to the person; they add the memories and finish on wisheroo.com. Nothing is created or charged by this tool.

NameTypeReqDescription
occasionstring––
recipient_namestring–What the song should call them, for example Dad or Maria.

No output schema declared.

No examples provided.

start_wish_list_link ~72

Build a link that opens the free Wisheroo video wish list recorder for an occasion, optionally naming who will watch it (for example Grandma). Nothing is created by this tool.

NameTypeReqDescription
occasionstring––
watcherstring–Optional: who the list is for, for example Grandma.

No output schema declared.

No examples provided.

Install

How do I install the Wisheroo MCP server?

Wisheroo is a hosted endpoint at https://wisheroo.com/api/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 · wisheroo.com

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

What is the Wisheroo MCP server?

Wisheroo is an MCP server listed in the public MCP registry as com.wisheroo/wisheroo. Personal songs from your memories and free kids' video wish lists: prices, samples, start links. This page covers its hosted endpoint (https://wisheroo.com/api/mcp).

Is the Wisheroo MCP server safe to use?

Wisheroo scores 77 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 Wisheroo MCP server expose?

Wisheroo exposes 7 tools: about_wisheroo, list_products, list_occasions, list_sample_songs, faq, and 2 more. Their descriptions and schemas cost roughly 385 tokens of context every time the server is loaded.

Does the Wisheroo MCP server require authentication?

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

Is the Wisheroo MCP server still maintained?

Wisheroo is still listed as active in the MCP registry. We last reached this channel on 21 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 Wisheroo MCP server?

VerifyMCP ran 13 checks on Wisheroo, 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.