MusicCheck: copyright screening MCP server
ai.smilestory/musicchecksmilestory.aistreamable-httpv1.0.0Scanned
Screen audio or video URLs for commercial recordings before publishing; verify any report.
4 tools: 2 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the MusicCheck: copyright screening MCP server can do
The MusicCheck: copyright screening MCP server is published by smilestory.ai, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: screen_audio and verify_report), but cannot delete data. 2 tools only read.
1 tool brings in text other people can write (screen_audio); 1 tool can send data out of your system (screen_audio).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 2Claude Code: ask
screen_audioSubmit a publicly reachable audio or video URL for copyright screening.Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "submit": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Submit a publicly reachable audio or video URL for copyright screening. Returns immediately with a report_id and QUEUED status; the finished result is available from get_screening. Starting a screening is a paid call on the signed-in WIA account (WIA MCP Pro plan or credits).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- title: Screen audio or video for copyright matches
verify_reportCheck that a MusicCheck report id refers to a real screening, and see what it concluded.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Check that a MusicCheck report id refers to a real screening, and see what it concluded. Needs no sign-in, so anyone can verify a report someone else shows them, for example a claim of "already cleared".
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Verify a screening report is genuine
Only reads 2Show 2 read-only tools
get_screeningFetch the status and result of one screening.No findings
Why it is in this group
- The name "get_screening" says "get": a word for reading.
Description, as the server wrote it Fetch the status and result of one screening. When status is COMPLETED, returns every window where a commercial recording was detected, with timestamps and the matched title/artist, plus a plain-language verdict on whether the file is safe to publish.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Get a screening result
list_screeningsList recent screenings with their results.No findings
Why it is in this group
- The name "list_screenings" says "list": a word for reading.
Description, as the server wrote it List recent screenings with their results. Currently available only to the MusicCheck service API key; accounts signed in through Claude receive an error and look up screenings by report id.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: List recent screenings
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:27 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://musiccheck.smilestory.ai/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://login.smilestory.ai
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://musiccheck.smilestory.ai/mcp: tools/list returned 4 tools to an anonymous client, including screen_audio (write), verify_report (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http musiccheck https://musiccheck.smilestory.ai/mcpclaude mcp add --transport http musiccheck https://musiccheck.smilestory.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__musiccheck__get_screening",
"mcp__musiccheck__list_screenings"
],
"ask": [
"mcp__musiccheck__screen_audio",
"mcp__musiccheck__verify_report"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as musiccheck. Review it before you use it.
Capability tags behind 1 rule
- mcp__musiccheck__screen_audio untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.smilestory/musiccheck/verify?hash=59cd4f0c9a718a2324af69d4acd03e57e689a57179086a8f265d6dbd8008e169" | jq -e '.changed == false'Pinned hash 59cd4f0c9a71, from Nov 11, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.smilestory/musiccheck/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.smilestory/musiccheck)Source: MCP Registry. Synced Oct 21, 2026, 17:43 UTC.
MusicCheck: copyright screening MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the MusicCheck: copyright screening MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the MusicCheck: copyright screening MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the MusicCheck: copyright screening MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the MusicCheck: copyright screening MCP server have?
- 4 tools: 2 write, 2 read. screen_audio, verify_report, get_screening and list_screenings.
Does the MusicCheck: copyright screening MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the MusicCheck: copyright screening MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): screen_audio.
Has the MusicCheck: copyright screening MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.