TayPE MCP

io.github.taylormadeapps/taype

Control the TayPE desktop DAW locally via MCP.

Description as published in the official MCP registry.

What we measured

EndpointNone listed (runs locally)registry
Websitegithub.com/taylormadeapps/taype-releases/blob/main/mcp/README.mdregistry
GitHub stars2github.com/taylormadeapps/taype-releases
Last push2026-11-18GitHub API
Registry version0.18.1 · active · updated 2026-05-23registry

Signed reports

No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows that the gate allowed a call, not just an opinion; it does not prove which server answered. How to file one.

Is this your server?

Show the result of our latest check where your users look first. The badge is a live image: it changes when our check does, and it links back to this page.

Agora badge for io.github.taylormadeapps/taype

Markdown (README)
[![agora](https://openforallofus.com/badge/io.github.taylormadeapps/taype.svg)](https://openforallofus.com/tools/io.github.taylormadeapps/taype)
HTML (website or docs)
<a href="https://openforallofus.com/tools/io.github.taylormadeapps/taype"><img src="https://openforallofus.com/badge/io.github.taylormadeapps/taype.svg" alt="Agora: MCP handshake check" height="20"></a>

The badge reports one thing: the result of our last handshake check. A server with no remote endpoint shows as "runs locally". How we check.

Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name io.github.taylormadeapps/taype.