SongUp AI
REMOTE · WWW.SONGUPAI.COM
Find AI songs in 24 languages, start a custom song on SongUp AI, and find browser audio tools.
Available components
Last scanned (11 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Design and Media
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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 587 tokens (~195/item across 3 items; 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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 →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 2 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.
- 31 Oct 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.
- 29 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.
- 27 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.
- 25 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 +3
- HSTS header: fail → pass ▲ security
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 7 Nov 2026 · Probed https://www.songupai.com/mcp/agents
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.songupai.com | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 64a87aa3e457b6cd0e454bc13b358263 |
| SANs: www.songupai.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 insecure
Validation of www.songupai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| songupai.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=15552000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.songupai.com/mcp/agents | Verified | 200 | |
| http (plaintext) | http://www.songupai.com/mcp/agents | HTTPS enforced | 301 | https://www.songupai.com/mcp/agents |
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 →
find_audio_tool Find a SongUp AI audio tool ~145
Finds the SongUp AI browser audio tool for a task the user describes, such as splitting a song into vocals and music, removing vocals for karaoke, making a mashup of two songs, removing background noise, mastering a track, finding chords, converting audio to MIDI, auto-tune or editing audio. Returns the matching tools with what each one does and a link to open it on songupai.com, where the user uploads their audio. This tool does not process audio itself.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | What the user wants to do with their audio, in a few words (e.g. "separate vocals", "mashup maker", "audio editor"). |
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| matched | boolean | yes | – |
| task | string | yes | – |
| tools | array | yes | – |
No examples provided.
find_songs Find songs in the SongUp AI library ~186
Finds ready-made AI songs from the SongUp AI library and returns each one with a direct link to its audio (MP3). Use it when the user wants to hear AI songs or example songs in a language, genre, mood or for an occasion (for example "an Arabic love song", "Hindi lo-fi", "upbeat birthday pop"). Songs are pre-made library tracks, not made from the user's own words; for a song from their own idea use start_custom_song.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language the songs are sung in, or "Instrumental" for songs without vocals. Defaults to English. |
| limit | integer | – | How many songs to show (default 5). |
| query | string | – | Optional genre, mood or occasion to match, in a few words (e.g. "romantic", "lo-fi", "birthday", "rap"). |
| Name | Type | Req | Description |
|---|---|---|---|
| createUrl | string | yes | – |
| kind | string | yes | – |
| language | string | yes | – |
| query | string | yes | – |
| songs | array | yes | – |
No examples provided.
start_custom_song Start a custom song on SongUp AI ~152
Prepares a link that opens the SongUp AI song maker on songupai.com with the user's song idea already filled in, so they can turn it into a full song with vocals there. Use it when the user wants a song made from their own idea, story, names or lyrics (birthday, anniversary, love song, etc.). Nothing is created or charged by this tool; the song is made on songupai.com, which needs a free account.
| Name | Type | Req | Description |
|---|---|---|---|
| idea | string | yes | What the song is about, in the user's words: occasion, names, story, mood and style. Up to 500 characters. |
| language | string | – | Language to sing in, if the user said one. |
| Name | Type | Req | Description |
|---|---|---|---|
| createUrl | string | yes | – |
| idea | string | yes | – |
| kind | string | yes | – |
| language | string|null | yes | – |
No examples provided.
How do I install the SongUp AI MCP server?
SongUp AI is a hosted endpoint at https://www.songupai.com/mcp/agents, 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 · www.songupai.com
claude mcp add --transport http com-songupai-songup-ai 'https://www.songupai.com/mcp/agents'
What is the SongUp AI MCP server?
SongUp AI is an MCP server listed in the public MCP registry as com.songupai/songup-ai. Find AI songs in 24 languages, start a custom song on SongUp AI, and find browser audio tools. This page covers its hosted endpoint (https://www.songupai.com/mcp/agents).
Is the SongUp AI MCP server safe to use?
SongUp AI scores 87 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 SongUp AI MCP server expose?
SongUp AI exposes 3 tools: find_songs, start_custom_song, find_audio_tool. Their descriptions and schemas cost roughly 483 tokens of context every time the server is loaded.
Does the SongUp AI MCP server require authentication?
No. We connected to SongUp AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SongUp AI MCP server still maintained?
SongUp AI is still listed as active in the MCP registry. We last reached this channel on 7 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 SongUp AI MCP server?
VerifyMCP ran 13 checks on SongUp AI, 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.