StudioSphere Pulse — Audio Intelligence MCP Server

space.studiosphere/pulse

answering

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

Privacy-first audio intelligence: BPM, key, waveform. Audio never stored. Pay per second.

Uptime history 42 hours of history

42 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

647 ms

Response time

average over 24h

Stars

last commit 8 Jun 2026

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add pulse --transport http https://mcp.studiosphere.space/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "pulse": {
      "url": "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

{
  "mcpServers": {
    "pulse": {
      "url": "https://mcp.studiosphere.space/mcp"
    }
  }
}

Available tools 8

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

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.

estimate

estimate_cost

Get the exact price to analyze an audio file before committing. Always call this first. Returns cost in dollars and a job_estimate_id valid for 30 minutes. Free — never charged.

job

get_job_status

Check the status and results of an analysis job. Poll after analyze_track returns job_id, or after the user pays via request_payment_link. Returns full results when status=completed.

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

Generate a one-time Stripe payment page for users without a Pulse account. Before calling, you MUST confirm with the user that they have a lawful basis to submit this audio for analysis; for a user-requested batch/folder/project, one confirmation can cover that scope. Present the payment_url to the user as a link. Analysis begins automatically after payment. Poll get_job_status with the returned job_id.

start

start_trial

Start a temporary, email-free Pulse trial. Returns a short-lived private API key with enough banked tokens for one short URL-based v1 analysis. No Stripe Checkout session is created. Store the key in the client or a trusted local environment; do not repost it in public logs, screenshots, GitHub issues, shared chats, or directory examples.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.studiosphere.space/mcp	streamable-http	answering	659 ms	15 min ago

StudioSphere Pulse — Audio Intelligence — questions

Answers built from our own checks of this server.

What can StudioSphere Pulse — Audio Intelligence do?

It exposes 8 tools, read directly from the server on our last check. Among them: analyze_track, estimate_cost, get_job_status, get_token_balance, list_token_packs, purchase_token_pack and 2 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 →

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 647 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 with the file path 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 8 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 647 ms on average, which is faster than 14% 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?

Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.