io.github.epsilon-records/audiokit
AudioKit
Is the AudioKit MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.
Audio analysis and production jobs: BPM, key, fingerprint, tags, stems, cleanup, mastering.
needs auth probed 2026-11-15 · unchanged since 2026-11-14 · HTTP 401
Streamable HTTP error: Error POSTing to endpoint: {"error":{"code":"unauthorized","message":"send your API key as Authorization: Bearer <key>"}}- Endpoint
- https://api.audiokit.ai/mcp (streamable-http)
- Host
- api.audiokit.ai
- Getting access
- The server answers HTTP 401 with no WWW-Authenticate header and no OAuth metadata, so the publisher's documentation is the only guide.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://audiokit.ai/docs/mcp/
- Registry
- active, updated 2026-11-13 · registry entry
Compare this server with others.
More servers
Servers that mention fingerprint or production.
- ai.aient/mcp · needs auth
- Auralogs ai.auralogs/auralogs · not MCP
- Arclan MCP Registry ai.arclan/registry · alive
- ai.firmbrain/x402-services · not found
- objekts Production Desk ai.objekts.mcp/production-desk · alive
- HostProfit ai.hostprofit/mcp · timeout
- Revelara ai.revelara/mcp · needs auth
- SignalHarness.ai ai.signalharness/mcp · server error
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.