Skip to content

robot-md README: name the MCP tool that sends data to RRF #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
craigm26 merged 1 commit into from
Nov 12, 2026
Merged

robot-md README: name the MCP tool that sends data to RRF #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion plugins/robot-md/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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/<rrn>` 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/<rrn>` under CC0. See the [privacy policy](https://robotmd.dev/privacy/).

## Keeping copies in sync

Expand Down
Loading