From 918901de4a6dc4d65bb39e5aedbff994c42f9742 Mon Sep 17 00:00:00 2001 From: Craig M Date: Thu, 12 Nov 2026 12:34:33 -0800 Subject: [PATCH] robot-md README: name the MCP tool that sends data to RRF The Data section said the MCP server sends nothing. Its spatial_eval_submit_to_rrf tool uploads a signed score, and the directory submission says this README lists what the plugin sends. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01LkzLwZG62ywkcaNNrw7DxP --- plugins/robot-md/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/robot-md/README.md b/plugins/robot-md/README.md index 29f2948..10a2a5d 100644 --- a/plugins/robot-md/README.md +++ b/plugins/robot-md/README.md @@ -30,7 +30,7 @@ Declaration doesn't enforce anything. Physical limits are meant to be enforced a ## Data -The MCP server runs locally and sends nothing to the Robot Registry Foundation. Registry commands, which the `rrf-registry` skill runs only after you agree, publish a robot record at `rcan.dev/r/` under CC0. See the [privacy policy](https://robotmd.dev/privacy/). +The MCP server runs locally. It sends data to the Robot Registry Foundation only through its `spatial_eval_submit_to_rrf` tool, which uploads a signed spatial-eval score when you approve the call. Registry commands, which the `rrf-registry` skill runs only after you agree, publish a robot record at `rcan.dev/r/` under CC0. See the [privacy policy](https://robotmd.dev/privacy/). ## Keeping copies in sync