StudioSphere Pulse
https://server.smithery.ai/studiosphere/pulse/mcpDiscover free, licensed loops and analyze authorized audio for BPM, musical key and waveform data. Start with free discovery and see estimated costs before paid analysis. Connect anonymously to https://mcp.studiosphere.space/mcp using Streamable HTTP. Begin with search_open_loops, then get_open_loop. Preserve each sample's exact licence, required attribution and source credit. Free discovery needs no account or tokens. Connection guide: https://pulse.studiosphere.space/connect. For authorized audio, call estimate_cost first and review analysis_options, estimated duration, analysis cost, estimated upfront payment and any minimum final charge. With explicit rights and spending approval, request_payment_link creates one-off Checkout without a Pulse account or key; the human reviews and completes payment. Save the job and payment link privately. After payment or interruption, resume the same job with get_job_status; never create a replacement purchase. Usable results can include Studio notes for DAW/project notes. Notes and completed analysis do not prove payment or refund settlement; review receipts separately. BPM and key are estimates requiring review. Optional trial: one short URL analysis with a private temporary key, subject to the returned allowance. Trial issuance requires human approval. Keys bind at initialization: end the anonymous connection and reconnect after obtaining a trial/account key. Ongoing account analysis uses banked tokens; call list_token_packs for current tiers, including Starter, and get_token_balance through a trusted key-aware connection. MCP OAuth and bearer/header authentication are unsupported. Two controlled one-off Checkout workflows through an existing configured Claude connector were validated October 12, 2026, including buffered payment/refund and an explicitly approved short-track minimum charge. This does not certify fresh anonymous Claude initialization, trial/banked-token authentication or other hosts. Actual Smithery and ChatGPT host workflows remain untested; HTTP/SDK checks are separate evidence. Submit audio only with rights, permission, lawful access or another legal basis. Audio is processed for analysis and not stored as user audio. Available analysis: BPM, key and waveform; transcription, stems, mastering, chords and structure are unavailable. Docs: https://pulse.studiosphere.space/docs Privacy: https://pulse.studiosphere.space/privacy Pricing and refunds: https://pulse.studiosphere.space/terms#pricing Support: [email protected]
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 23/25 | Endpoint answers the MCP initialize handshake (5536 ms); very slow response -2. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 10 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 80% of peers
- This listing 86 · peer median 81
- Latency
- Faster than 20% of peers
- This listing 636 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
- Live MCP endpoint −2
— Answer initialize and tools/list at the declared endpoint.
Now: Endpoint answers the MCP initialize handshake (5536 ms); very slow response -2.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/studiosphere/pulse/mcp
curl -X POST https://server.smithery.ai/studiosphere/pulse/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'