Mcp Miro — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Mcp Miro (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
A bulleted imperative like {match} tells the agent to never reveal, disclose, or mention something to the user. Used adversarially it can instruct the agent to hide its tool calls or lie about what it did — stripping the transparency a user relies on to trust the agent.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
A Model Context Protocol server to connect to the MIRO Whiteboard Application.
<a href="https://glama.ai/mcp/servers/gr5t7vthv3"><img width="380" height="200" src="https://glama.ai/mcp/servers/gr5t7vthv3/badge" alt="mcp-miro MCP server" /></a>
To install MIRO Whiteboard Connector for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @llmindset/mcp-miro --client claudeYou can install this package using mcp-get:
npx @michaellatman/mcp-get@latest install @llmindset/mcp-miro_Note - if you are using an old version of Windows PowerShell, you may need to run_ Set-ExecutionPolicy Bypass -Scope Process _before this command._
MIRO/Claude Desktop Screenshot
Install dependencies:
npm installBuild the server:
npm run buildFor development with auto-rebuild:
npm run watchTo use with Claude Desktop, add the server config:
On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"mcp-miro": {
"command": "/path/to/node-or-npx",
"arguments": [
"/path/to/mcp-miro/build/index.js",
"--token","MIRO-OAUTH-KEY"
]
}
}
}Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:
npm run inspectorThe Inspector will provide a URL to access debugging tools in your browser.
In Dev environment recommend adding https://github.com/miroapp/api-clients/blob/041de24ebf7955432b447d887ede066ad4c7e2c7/packages/generator/spec.json for reference.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.