remote-mcp
Skill0 starsChanged 54 days agoApache-2.0View on GitHub
MCP and device-relay compatibility rules for Open Remote Commander.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- garrytan/gbraintheir own version, first seen Oct 17, 2026
- mediar-ai/terminatortheir own version, first seen Oct 8, 2026
- marioluciofjr/skillstheir own version, first seen Mar 27, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- garrytan/gbrain★ 32ksame name
- mediar-ai/terminator★ 1.7ksame name
- marioluciofjr/skills★ 18same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- go-engineeringSkill
- security-reviewSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Prefer the official modelcontextprotocol/go-sdk for the public MCP endpoint.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Remote MCP rules
- MCP terminates at
orc-server; the agent protocol is a smaller independent wire protocol. - Prefer the official
modelcontextprotocol/go-sdkfor the public MCP endpoint. - Support Streamable HTTP and Protected Resource Metadata required by current MCP authorization guidance.
- MCP access tokens identify users; device tokens identify machines. Never reuse one token class for the other.
- Device WebSockets are outbound from the controlled machine, one current owner connection per device ID.
- Calls use random IDs and bounded pending maps. Closing a socket must immediately fail all pending calls.
- Breaking device-protocol changes get a new
/agent/vN/endpoint; do not silently reinterpret old frames. - New tools require: public JSON type, MCP schema/handler, executor implementation, hard resource bounds, tests, security review and compatibility docs. Search/edit/process tools must fail closed on ambiguous or policy-disallowed operations.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.