ruflo-chatgpt-federation

Reviewed at commit ab18c33

Dedicated ChatGPT Federation MCP publisher with isolated Nostr signing-key custody, OAuth-scoped publishing, and signed public-channel coordination over the…

Made by
ruvnet
What we checked

Checks calls to the ChatGPT federation connector's channel_publish tool and blocks messages to non-public channels, messages with secret-looking text or credential-named fields, and payloads over a size cap (8 KB by default). It can only deny. It adds a /chatgpt-mod command and writes counters to a status file in your project. The plugin itself makes no network calls; the publisher service in its folder is not started by it.

Review details

Static review of the source at the pinned commit; not run. Delta review of the changes since bd77bce; the rest carries over from the review at that commit. Registers session.start (registers /chatgpt-mod, reads the project root, writes counters), tool.call (guard on channel_publish for MCP servers whose name contains chatgpt or federation; other tools pass) and command.run for /chatgpt-mod (status, scan, channel; answered locally). The guard denies channels not matching pub:<name>, secret shapes or credential-named fields in msgType and payload, and payloads above maxPayloadBytes (256 to 65536, default 8192). $.fs.write is used only for .claude-flow/chatgpt-mod/status.json (rule names and counts). No network, process or env use in the hooks. The folder also holds src/*.mjs, a separate Node MCP publisher service (Nostr signing, OAuth against auth.cognitum.one, WebSocket to wss://relay.ruv.io by default, signing key read from a mounted secret path, open CORS, rate limit keyed on x-forwarded-for) that a README describes deploying to the author's Cloud Run. Nothing in the plugin launches it: there is no .mcp.json, hook or skill that starts it, so installing the plugin does not run it. Changes in this version: version 0.2.6 with a repository field in plugin.json, a zod 3 to 4 dependency bump in package.json, and in src/server.mjs the channel_publish payload schema changed from z.record(z.any()) to z.record(z.string(), z.any()) (the zod 4 form of the same schema); smoke.sh only updates the expected version. The hooks, manifest permissions and hook files are unchanged. The Dockerfile, e2e script, smoke script and npm dependencies (@modelcontextprotocol/sdk, zod, nostr-tools, ws, jose) were not reviewed.

What it uses
  • Reads your prompts: no
  • Sees tool calls: yes
  • Blocks or changes tool calls: yes
  • Reads or writes files: yes
  • Runs programs on your machine: no
  • Calls the model (uses tokens): no
  • Sends data over the network: no
  • Stores data: yes
  • Shows something on screen: yes
Hooked events

Dedicated ChatGPT Federation MCP publisher with isolated Nostr signing-key custody, OAuth-scoped publishing, and signed public-channel coordination over the Ruflo relay. As a mod (ADR-445 pattern): a tighten-only tool guard, a local slash command, and a status file the console shows.

Made this mod? Add a badge to your README

modsforClaude badge for ruflo-chatgpt-federation

Paste this into your README. The badge says reviewed once the current version has been reviewed, and links readers to this page.

[![Listed on modsforClaude](https://modsforclaude.com/badge/ruflo-chatgpt-federation.svg)](https://modsforclaude.com/mods/ruflo-chatgpt-federation/)

← All mods