mcpbeat Sign in

StudioSphere Pulse — Audio Intelligence MCP Server

by studiosphere Your server? Claim it
answering

StudioSphere Pulse — Audio Intelligence is answering right now. Last checked 8 min ago. It exposes 10 tools. Last commit 30 Oct 2026.

Free licensed loops and authorized audio analysis: BPM, key, waveform. Estimate before paid use.

Uptime history 91 days of history · worst day 98%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
10
Tools
read from the server
668 ms
Response time
average over 24h
0
Stars
last commit 30 Oct 2026

What changed 29

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 7 October 2026. No other catalogue keeps this.

30 Oct a tool description was rewritten search_open_loops
30 Oct a tool changed the parameters it asks for search_open_loops
29 Oct 3 tool descriptions were rewritten get_job_status, request_payment_link, search_open_loops
29 Oct a tool changed the parameters it asks for get_job_status
29 Oct a tool changed version
13 Oct a tool description was rewritten get_job_status
13 Oct a tool changed version
12 Oct 3 tool descriptions were rewritten8 times that day estimate_cost, get_job_status, request_payment_link
12 Oct a tool changed the parameters it asks for request_payment_link
9 Oct a tool description was rewritten estimate_cost
and 15 more, back to 7 October 2026

What the code does

We read the source, 1 d ago · tools taken from the live server · rules 995398eba69f

Evidence

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

Claims local-only, but ships network tools request_payment_link
заявлено «локально, без передачи данных», но есть request_payment_link

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch StudioSphere Pulse — Audio Intelligence and you get told the day something new turns up.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add pulse --transport http https://mcp.studiosphere.space/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.studiosphere.space/mcp
~/.codex/config.toml
[mcp_servers.pulse]
url = "https://mcp.studiosphere.space/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "pulse": {
      "url": "https://mcp.studiosphere.space/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "pulse": {
      "type": "http",
      "url": "https://mcp.studiosphere.space/mcp"
    }
  }
}

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

open
get_open_loop
Get a released sample’s metadata, exact licence, attribution, preview and WAV download URLs. Free; no account or tokens required. Keep attribution when using the sample in a song.
search_open_loops
Find original synthesis kits and individually auditioned source samples by keyword, pack, BPM, key, role, review_basis and licence. project_bpm with bpm_tolerance (default 5) returns closest-tempo candidates and project_match reasons; do not combine it with bpm_min/max. Project keys need explicit mode. Optional include_unkeyed_percussion includes percussion hints with unspecified key, requiring audition; this is not proof of harmonic fit. Automated checks are not listening review. Free; no account or tokens required. Keywords match any term; read search_match.missing_terms before claiming a full match or genre. Key abbreviations such as Am are accepted; hard filters stay exact. Source tags are creator hints. Preserve attribution when required and follow each sample’s licence.
token
get_token_balance
Check the banked token balance for the authenticated Pulse account. Requires PULSE_API_KEY.
list_token_packs
List the available Pulse token packs (tier label, token count, price). Use before purchase_token_pack to show options to the user.
analyze
analyze_track
Run audio analysis on a public audio URL. Requires estimate_cost to be called first (job_estimate_id). Requires PULSE_API_KEY. Before calling, you MUST confirm with the user that they have a lawful basis to submit this audio for analysis. For a user-requested folder, project, playlist, or batch, one confirmation can cover every track in that scope. Returns job_id — poll get_job_status for results. If processing or payment returns estimate_pricing_changed, get a fresh free estimate with estimate_cost, present the new price, and wait for explicit user approval before processing or payment. Never silently retry analysis or purchase.
estimate
estimate_cost
Estimate audio analysis cost anonymously and free before committing. Read analysis_options for eligible anonymous one-off Checkout, trial duration fit and key-based banked-token use; these do not verify balance or trial entitlement. Eligible quotes can include checkout.upfront_payment_estimate from the current charge builder; this is not a reserved price or a saved-link charge. Review the hosted amount before payment. Returns estimated dollars, job_estimate_id and expires_at. Review the estimate before spending; final cost depends on measured duration and completed analysis, and Checkout can collect a buffered amount with refund thresholds. If processing or payment returns estimate_pricing_changed, get a fresh free estimate, present the new price, and wait for explicit user approval before processing or payment. Never silently retry analysis or purchase.
job
get_job_status
Resume the original saved job anonymously after interruption. Follow continuation for human payment, bounded polling, result review or support; never create a replacement purchase. Completed/partial results may include studio_notes: preserve provenance, warnings and failed tools; BPM/key are estimates requiring review. Keep job references private. Results, costs and notes are not payment/refund confirmation. refund_status_source=local_ledger is reconciliation at refund_checked_at, not a fresh provider query; unconfirmed/needs_review is not a completed refund. Review terminal Checkout billing separately on the result page or the on-demand REST receipt_api_url; that URL is not another MCP tool.
purchase
purchase_token_pack
Create a Stripe Checkout session for a Pulse token pack. Returns payment_url — DO NOT submit it programmatically; surface it to the user so they can complete payment in their browser. Once paid, banked tokens are credited automatically. Requires PULSE_API_KEY.
request
request_payment_link
Create anonymous one-off Checkout after an estimate, explicit human link-creation approval and lawful-basis confirmation. Read analysis_options.checkout. The human reviews the hosted upfront amount and pays; it can exceed analysis cost. Save job_id, payment_url and continuation.review_url privately; lost links require support, not a replacement purchase. For minimum_charge_offer, show minimum final cost and upfront estimate, obtain explicit acceptance, then send accept_minimum_charge:true and max_upfront_amount_cents at the approved ceiling. Rights alone do not approve spending. On estimate_pricing_changed, get a fresh free estimate and explicit approval. An exceeded cap needs new review; never raise it or retry automatically. Poll the original job with get_job_status after payment or interruption. Host setup/recovery: https://pulse.studiosphere.space/connect
start
start_trial
Start a temporary, email-free Pulse trial for one URL analysis. Read trial_policy and trial_allowance for the actual duration cap and remaining attempts; an existing trial key may have a lower cap. One completed/partial analysis consumes the allowance regardless of remaining tokens. A failed analysis may retry only when attempts remain. No Stripe Checkout session is created. Store the returned private API key in the client or a trusted local environment; never repost it in logs, screenshots, shared chats or issues. Confirm rights, permission, lawful access, or another legal basis before analysis. The original CC0 demo is https://pulse.studiosphere.space/assets/pulse-demo.mp3 (180 seconds); use it only if it fits the returned cap.

Endpoints

URLTransportStateLatencyChecked
https://mcp.studiosphere.space/mcp streamable-http answering 661 ms 8 min ago

Alternatives to StudioSphere Pulse — Audio Intelligence

same job, measured the same way
Echosaw
by matthew-b-simpson

Media intelligence analysis for audio, video, and images via the Echosaw MCP server.

328 installs/wk local only
Echosaw
by echosaw

Media intelligence analysis for audio, video, and images via the Echosaw MCP server.

answering
FastestRank SEO Intelligence
by fastestrank

Live SEO intelligence, rank tracking, site audits, and backlink analysis for AI agents.

answering
GoVeda Patent Search
by goveda

AI-powered patent intelligence for search & analysis

answering
Japan Website Intelligence
by adson-japan-data

Website company, contact, hiring and social links. 20 free daily lookups; prepaid keys for AI.

answering
X402watch
by printmoneylab

Wash-filtered intelligence for x402: categories, services, wash analysis, trends.

5 tools answering
Cartelera
by cartelera

AI video and music studio: music videos, ads, voiceovers and audio analysis (genre, BPM, key).

answering
Mind Map
by nerfels

Experimental code intelligence platform for Claude Code with AST parsing and context analysis

63 installs/wk local only

StudioSphere Pulse — Audio Intelligence — questions

Answers built from our own checks of this server.

What can StudioSphere Pulse — Audio Intelligence do?
It exposes 10 tools, read directly from the server on our last check. Among them: analyze_track, estimate_cost, get_job_status, get_open_loop, get_token_balance, list_token_packs and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is StudioSphere Pulse — Audio Intelligence mostly used for?
Its tools cluster around open and token. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is StudioSphere Pulse — Audio Intelligence working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 668 ms. The bar chart above shows every period we have measured.
How do I connect StudioSphere Pulse — Audio Intelligence?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does StudioSphere Pulse — Audio Intelligence need an API key?
No. StudioSphere Pulse — Audio Intelligence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is StudioSphere Pulse — Audio Intelligence?
It answers our handshake in 668 ms on average, which is faster than 15% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is StudioSphere Pulse — Audio Intelligence open source?
The code is open source: it is published under the MIT licence and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.studiosphere.space, which runs on its operator's own terms.