Skills/PyPI/robotics-control-mcp

robotics-control-mcp@1.0.8

VERIFIED· not started

Publisher claims: "Robotics Control MCP server. Tools: list devices, send command, read sensor. Built by MEOK AI Labs." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher csoai-org · publishing for 216 daysInstalls 186Last detonated 1 h ago
$claude mcp add robotics-control-mcp -- uvx robotics-control-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
MEOK_API_KEYConfiguration, not credentials: MEOK_ATTEST_KEY, MEOK_PAYG_KEY, MEOK_VERIFY_TIMEOUT, MEOK_VERIFY_URL
Where it talks to
no vendor host named in the codeAlso proofof.ai, stripe.com, meok.ai, smithery.ai, mcpize.com, councilof.ai — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names proofof.ai, stripe.com, meok.ai, smithery.ai, mcpize.com, councilof.ai as well as its own vendor. The guard injects MEOK_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx robotics-control-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-16 and scored it 91/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 1 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.9sprocessdependency install exit 1 · npm error notarget In most cases you or one of your dependencies are requesting npm error notarget a package version that doesn't exist. npm error A complete log of this run can be found in: /tmp/ks-detonate-wlgHuq/task/home/.npm/_logs/2026-11-16T02_38_08_605Z-debug-0.log
0.9sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.9sprocessscript backend runs setup only
0.9sprocessno install scripts to re-run

Static findings

LOW
URL to a private-network addressserver.py:72 · URL to a private-network address — a LAN or development target"connection": connection, # /dev/ttyUSB0 or http://192.168.1.100Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.
AST07
LOW
URL to a private-network addressserver.py:486 · URL to a private-network address — a LAN or development target- An HTTP URL: http://192.168.1.100/api/commandFix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.
AST07
MEDIUM
npx invocation of non-well-known package.github/workflows/mcp-smithery-publish.yml:33 · npx invocation of non-well-known package — may execute untrusted codenpx @smithery/cli mcp publish "https://github.com/${{ github.repository }}" -n nicholastempleman/${{ github.event.repository.name }} --jsonFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
MCP server using network transport (SSE/HTTP)mcp-wrapper.py:85 · MCP server using network transport (SSE/HTTP) — data sent over networkmcp_server.run(transport="streamable-http")Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04

Cost to the agent

Instructions loaded
≈65 tok
1 file · 32 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

Not checked against OSV yet; the weekly check has not reached this version.