MCP servers › com.doseedo › daw-sessions
MCP server · registry snapshot 2026-11-18 · last tested 2026-11-18
daw-sessions MCP server
Registry name com.doseedo/daw-sessions
Doseedo DAW Sessions: read, edit and convert Logic, Ableton, FL Studio and Pro Tools projects — the publisher's title
by doseedo.com · domain (the registry's namespace rule)Website ↗
Read and edit DAW projects as an agent, save native Logic projects, convert projects between DAWs — the publisher's description
Summary
com.doseedo/daw-sessions is a remote MCP server listed in the official MCP registry at version 0.22.1, under the namespace of the domain doseedo.com. On 2026-11-18 ProtocolProbe connected to it in read-only mode and read its inventory: 20 tools, 0 resources and 0 prompts.
Record checks
1 of 2 record checks met · 7 do not apply
- met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Tools
- 20
- Last tested
- 2026-11-18
Tool list size
12,249 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (20 tools). Counted with Anthropic's token counter on 2026-11-18, from the tool list we read on 2026-11-18. Median across 28,560 counted servers: 2,657 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-11-18 (api.doseedo.com), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (0.22.1).
Observed fact
This server accepted a session without any credential and lists 7 tools whose name or declaration suggests they change data (doseedo_get_project_upload_url, doseedo_complete_project_upload, doseedo_cancel_job, doseedo_delete_sessions, doseedo_edit_session and 2 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-18.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-18
- Mode
- read-only (no tool calls)
- Latest version
- 0.22.1, published 2026-11-17 (registry, as of the 2026-11-18 snapshot)
- First listed version
- 2026-11-09 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 2 versions listed, 2026-11-09 to 2026-11-17; 2 in the 90 days before the 2026-11-18 snapshot.(versions still listed in the registry only)
Most recent 2 versions
0.22.1· 2026-11-170.22.0· 2026-11-09
- Registry data
- snapshot 2026-11-18
- Package and repository
- checked 2026-11-18
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 0.22.0 (published 2026-11-09) → 0.22.1 (published 2026-11-17), between the registry lists of 2026-11-17 and 2026-11-18.
No release note: the registry entry links no GitHub repository.
Source: the official MCP Registry list on 2026-11-17 and on 2026-11-18; release notes from the GitHub Releases API, checked 2026-11-18.
What it is
What does this server offer?
Observed inventoryNone of its 20 tools are described as changing anything. For 20 the reading was uncertain, so no mark is shown.
- doseedo_convert_projecton 1 other server
“DAW CONVERTER: a project rebuilt natively in the target: tracks, MIDI, audio clips, tempo and markers arrive editable (Logic/Ableton/Pro Tools/REAPER pairs also automation, buses/sends, plugin state;…”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
4 inputs, 2 required
project_keystringrequired“R2 key of the uploaded project (from doseedo_get_project_upload_url / POST /api/upload/r2/signed-url; starts with "uploads/").”directionstringrequired“Source and target as "<source>2<target>" (logic | ableton | fl | protools | reaper | cubase | dorico | studioone | bitwig | garageband | aaf), "auto2<target>" …”optionsobject“Conversion options (all optional).”idempotency_keystring“Optional.”
- doseedo_get_project_upload_urlon 1 other server
“Get a presigned upload for a DAW PROJECT file (for doseedo_convert_project / doseedo_import_project).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
7 inputs
filenamestring“File name including extension, e.g.”content_typestring“MIME type: application/zip for zips (default), application/octet-stream for bare project files.”size_bytesnumber“The file's size in bytes (stat it).”multipartboolean“Force a multipart upload regardless of size (resumable per part).”project_keystring“CONTINUATION of a multipart upload: the key the first call returned.”upload_idstring“CONTINUATION: the upload_id the first call returned.”part_numbersarray“CONTINUATION: which part numbers (1-based) to sign now, ≤ 24 per call.”
- doseedo_complete_project_uploadon 1 other server
“Finish a MULTIPART project upload started by doseedo_get_project_upload_url: pass every uploaded part's number and ETag (from the PUT response header; quotes optional).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
4 inputs, 2 required
project_keystringrequiredupload_idstringrequiredpartsarray“[{part_number, etag}] for EVERY part, in order.”abortboolean“true = abandon the upload and free its parts (no project_key results).”
- doseedo_import_projecton 1 other server
“Open an uploaded DAW project (Logic .logicx.zip, Ableton .als or project zip, FL .flp, REAPER .rpp, Pro Tools .ptx — zip the folder) as an EDITABLE doseedo session: returns a session_id the session t…”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
4 inputs
project_keystring“R2 key of the uploaded project (from doseedo_get_project_upload_url; starts with "uploads/").”dawstring“The source DAW, when the filename does not say (optional; detected otherwise).”namestring“Session name (default: the project's own name).”task_idstring“CONTINUATION: the task_id a previous call returned while the parse was still running.”
- doseedo_check_taskon 2 other servers
“Check an async doseedo job once — a DAW conversion (doseedo_convert_project) or a bounce (doseedo_bounce_session).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
5 inputs
task_idstring“The task_id returned by a submit tool.”kindstring“Which job kind created the task — convert_project or bounce_session, the name the submit reply carried (convert / bounce are accepted aliases).”job_idstring“Alternatively the job_id (job_…) from doseedo_convert_project, doseedo_bounce_session or doseedo_list_jobs — replaces task_id + kind.”partsarray“Optional, on a finished job: the result rows to return in full, by name (as the result names them) or index.”frominteger“Optional, with parts naming one list: the first row to return (0-based) — a long list comes in pages.”
- doseedo_wait_taskon 2 other servers
“Wait for an async doseedo job — a DAW conversion or a bounce — to finish: polls server-side for up to timeout_seconds (5–50; one call can never hold longer than 50 s), then returns the result or the …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs
task_idstring“The task_id returned by a submit tool.”kindstring“Which job kind created the task — convert_project or bounce_session, the name the submit reply carried (convert / bounce are accepted aliases).”job_idstring“Alternatively the job_id (job_…) from doseedo_convert_project, doseedo_bounce_session or doseedo_list_jobs — replaces task_id + kind.”timeout_secondsnumber“Max seconds to wait in this call (5–50, default 45).”
- doseedo_list_jobson 2 other servers
“List the jobs this account submitted, newest first — DAW conversions (convert_project) and bounces (bounce_session) — to find an earlier result, check what is still running, or resume after a lost co…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
5 inputs
limitnumber“How many (1–100, default 20).”kindstring“Only this job kind: convert_project or bounce_session (convert / bounce are accepted aliases).”statusstringsession_idstring“Only jobs whose input names this session (its bounces), filtered within the fetched page.”beforestring“Page cursor: the next_cursor of a previous call.”
- doseedo_cancel_jobon 2 other servers
“Cancel a queued or running job.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
1 input, 1 required
job_idstringrequired“The job_id from doseedo_convert_project, doseedo_bounce_session or doseedo_list_jobs.”
- doseedo_accounton 2 other servers
“Check the connected doseedo account: plan tier, the monthly credit pool (DAW conversions draw it), purchased extra-usage credits, and storage.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
Takes no inputs.
- doseedo_list_sessionson 1 other server
“List the connected account's DAW sessions (most recently updated first) — their ids, names, DAW, and update time.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs
limitnumber“How many to return (default 25, max 200).”offsetnumber“How many to skip (default 0) — pass the previous response's next_offset to get the next page.”name_containsstring“Only sessions whose name contains this text (case-insensitive).”
- doseedo_delete_sessionson 1 other server
“Delete DAW sessions in bulk — a SOFT delete (the sessions disappear from the account and every listing; nothing on the user's disk is touched).”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
7 inputs
idsarray“Session ids to delete (up to 500), from doseedo_list_sessions.”daw_kindstring“Only sessions bound to this DAW, e.g.”created_beforestring“ISO-8601 date/time: only sessions created before this.”created_afterstring“ISO-8601 date/time: only sessions created after this.”name_containsstring“Only sessions whose name contains this text (case-insensitive).”limitnumber“Cap on how many sessions one call may match (default and max 1000).”confirmboolean“false/omitted = dry run (nothing deleted).”
- doseedo_get_sessionon 1 other server
“Read a DAW session as the arrangement an agent edits against: every track with its wire ids (track_id t_…, mixer strip channel_id ch_…), regions in BOTH beats and seconds with their MIDI notes (i, pi…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
5 inputs, 1 required
session_idstringrequired“From doseedo_list_sessions.”tracksarray“Only these tracks (track_id t_… or channel_id ch_…; a track name matches too).”include_notesboolean“Include MIDI notes.”include_paramsboolean“Include plugin params (default true).”include_automationboolean“Include automation lanes with points (default true).”
Show 8 more tools
- doseedo_edit_sessionon 1 other server
“Edit a DAW session with a list of ops (regions, MIDI notes, sampler samples, tracks, mixer faders/pans/mutes, plugins, tempo, markers, key, …): ids and current values from doseedo_get_session, op arg…”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
4 inputs, 2 required
session_idstringrequiredbatch_keystring“A stable id for THIS batch (e.g.”atomicboolean“Default true: any rejected op means nothing is stored.”opsarrayrequired“The edits, e.g.”
- doseedo_edit_ops_referenceon 1 other server
“The catalog of session edit ops doseedo_edit_session accepts, served in views that each fit one answer (never cut mid-JSON).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs
sectionstring“Which part of the catalog.”opstring“One op name, e.g.”opsarray“Several op names — returns each in full.”
- doseedo_desktop_statuson 1 other server
“Is Dø Desktop running on the user's Mac, and can it put edits into their Logic project?”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
Takes no inputs.
- doseedo_add_audio_to_sessionon 1 other server
“Add an audio file to a session from a public https URL (any audio file online; a bounce's pre-signed stem link works as is).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
4 inputs, 1 required
session_idstringrequiredaudio_urlstring“https URL of the audio — any public URL, or a doseedo result URL from a job (pre-signed links work as-is; no key needed).”audio_keystring“Instead of audio_url: the key of audio already uploaded to this doseedo account (starts with "ingest/").”filenamestring“Optional name for the asset.”
- doseedo_bounce_sessionon 1 other server
“Bounce a session (or specific tracks) to audio on the user's Mac — Dø Desktop renders them in the background WITHOUT the user opening the DAW (engine "headless"): each AUDIO track's regions as the ar…”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
6 inputs, 1 required
session_idstringrequiredtrack_idsarray“Tracks to bounce (t_… ids from doseedo_get_session).”stemsboolean“true (default) = one file per track; false = a single mixdown.”tail_secondsnumber“Extra seconds for reverb/delay to ring out (default 2).”formatstring“Output format (default wav).”idempotency_keystring“Optional.”
- doseedo_download_sessionon 1 other server
“Save a session as a native Logic project (.logicx.zip), rebuilt server-side from the session state — no desktop needed.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
session_idstringrequireddawstring“Target DAW (default logic; only logic is a one-shot native download — for others use doseedo_convert_project).”
- doseedo_list_pluginson 1 other server
“List the plugins you can insert on a strip with doseedo_edit_session's add_device op.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
Takes no inputs.
- doseedo_create_sessionon 1 other server
“Create a new, empty DAW session in the account (a blank project you can then populate with doseedo_edit_session).”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 1 required
namestringrequired“Session name.”dawstring“Bound DAW (default logic).”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-18.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 90% of 70
- Tools with a description
- 100% of 20
- Typical description length
- 715 characters
The tool set
Counted from the listing
- Tools
- 20
- Size of the list
- about 8,224 tokens for an agent to load (characters ÷ 4)
- Naming
- 20 of 20 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 20 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-11-18 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://api.doseedo.com/mcp/daw
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"daw-sessions": {
"url": "https://api.doseedo.com/mcp/daw"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"daw-sessions": {
"type": "http",
"url": "https://api.doseedo.com/mcp/daw"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"daw-sessions","type":"http","url":"https://api.doseedo.com/mcp/daw"}'Claude Code
claude mcp add --transport http daw-sessions https://api.doseedo.com/mcp/daw
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"daw-sessions": {
"type": "streamableHttp",
"url": "https://api.doseedo.com/mcp/daw",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"daw-sessions": {
"httpUrl": "https://api.doseedo.com/mcp/daw"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.daw-sessions] url = "https://api.doseedo.com/mcp/daw"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"daw-sessions": {
"url": "https://api.doseedo.com/mcp/daw"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://api.doseedo.com/mcp/daw --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- MCP SDK in the package files. Not read yet: added with the next daily run.
- Build workflow. Not read yet: added with the next daily run.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-18. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-18. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-18. Source: read 2026-11-18.
- Cline marketplace. Not in the Cline marketplace on 2026-11-18. Source: read 2026-11-18.
Own host
- security.txt. Not read (our limit: timeout 8 s, 2026-11-18). Source: api.doseedo.com/.well-known/security.txt · read 2026-11-18.
- A2A agent card. Not read (our limit: timeout 8 s, 2026-11-18). Source: api.doseedo.com/.well-known/agent-card.json · read 2026-11-18.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint api.doseedo.com/mcp/daw | Session opened | matches | our test · 2026-11-18 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-11-18 |
Tool list changes
Our reads compared · no tool calledHosted endpoint api.doseedo.com/mcp/daw
1 of 1 comparison between consecutive reads showed a change (2 reads, 2026-11-12 to 2026-11-18; versions 0.22.0 to 0.22.1).
Last change seen between our reads on 2026-11-12 (version 0.22.0) and 2026-11-18 (version 0.22.1).
Changed (1):
doseedo_download_session: descriptionCompared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-18 is not known yet. No tool was called. How it is compared
Choosing
Record checks
Public records · not a safety rating1 of 2 record checks met · 7 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-18. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about com.doseedo/daw-sessions
Answered from the data aboveWho publishes com.doseedo/daw-sessions?
The registry ties the namespace com.doseedo to the domain doseedo.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.
Does com.doseedo/daw-sessions need an API key or sign-in?
It opened a session without any credential on 2026-11-18. The registry entry declares no required credential; no declaration is not a guarantee.
Has com.doseedo/daw-sessions been security tested?
Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Open without sign-in
It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: exercised
3 exercised12 not run (reason given)3 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
Source: our own test, 2026-11-18, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 446 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 20 tools, 0 resources, 0 prompts.
- 1,718 msFinished: 3 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “com.doseedo/daw-sessions: MCP server record.” Data checked 2026-11-18. https://protocolprobe.com/mcp/servers/com.doseedo/daw-sessions
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/com.doseedo/daw-sessions)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology