@alr51307/noimg 0.3.0 → 0.3.1

package/README.md

@@ -16,6 +16,8 @@
 
 <p align="center"><code>@noimg</code> means explicit <strong>NON-IMAGE OUTPUT</strong>.</p>
 
+> **Experimental / made for fun.** NoIMG is a tiny hobby project, not a platform-level kill switch. It can improve the odds that `@noimg` stays non-image, but it is **not 100% reliable** because the host still decides tool routing. Sometimes the agent may still reach for the crayons. `¯\_(ツ)_/¯`
+
 ---
 
 You:
@@ -62,7 +64,7 @@ One process talks to one local MCP client over stdin/stdout. That is it. We brav
 Official npm package:
 
 ```bash
-npx -y @alr51307/noimg@0.3.0
+npx -y @alr51307/noimg@0.3.1
 ```
 
 For MCP clients, use the same pinned package command. The executable is still `noimg`; the scope just makes package ownership explicit.

package/SECURITY.md

@@ -17,11 +17,13 @@ At runtime it does not:
 
 The MCP process communicates with its local client through stdin/stdout only.
 
+NoIMG's policy behavior is **best effort and not a security control**. The project is experimental, was created mostly for fun, and cannot guarantee that every host will honor `@noimg` before its own built-in image routing.
+
 ## Package identity
 
 The official npm package is `@alr51307/noimg`.
 
-Prefer a pinned version such as `@alr51307/noimg@0.3.0` in MCP configuration so upgrades are deliberate. A bare npm package named `noimg` is not this project.
+Prefer a pinned version such as `@alr51307/noimg@0.3.1` in MCP configuration so upgrades are deliberate. A bare npm package named `noimg` is not this project.
 
 ## Reporting a vulnerability
 

package/dist/cli.js

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 import { runStdio } from './stdio.js';
-const VERSION = '0.3.0';
+const VERSION = '0.3.1';
 function usage() {
     return `NoIMG ${VERSION}\n\nUsage:\n  noimg            Start the stdio MCP server\n  noimg stdio      Start the stdio MCP server\n\nNo network listener. No remote mode. No tunnel.\n`;
 }

package/dist/server.js

@@ -12,7 +12,7 @@ export const NOIMG_DIRECTIVE = [
     'If no compatible tool or format was explicitly requested, fulfill the request with a text-native alternative such as ASCII/Unicode art, Mermaid, SVG source, HTML/CSS, code, or structured text. Do not ask the user to restate the request.',
 ].join('\n');
 export function createServer() {
-    const server = new McpServer({ name: 'noimg', version: '0.3.0' });
+    const server = new McpServer({ name: 'noimg', version: '0.3.1' });
     server.registerTool('noimg', {
         title: 'NoIMG Non-Image Preflight Hard Block',
         description: '@noimg PRE-FLIGHT — ALWAYS invoke this tool before tool routing whenever the current user request contains the literal token @noimg. That token means the user explicitly requests NON-IMAGE OUTPUT for this request. Do not classify draw, create, generate, render, visualize, illustrate, picture, image, or similar wording as image-generation intent when @noimg is present. Hard-block image-generation, image-editing, and image-rendering operations before selecting tools, then continue all compatible non-image tools, formats, and workflows normally. NoIMG is not task completion.',

package/docs/usage.md

@@ -17,12 +17,18 @@ When a request contains the literal token `@noimg`, treat the request as explici
 
 Words such as `draw`, `render`, `visualize`, `create`, or `illustrate` do not override `@noimg`.
 
+## Limitations
+
+NoIMG is experimental and was created mostly for fun. It is **not a 100% reliable platform-level blocker**. MCP tool selection and built-in image routing are controlled by the host/client. If a host bypasses NoIMG and starts an image operation before invoking the tool, the NoIMG server cannot intercept a request it never received.
+
+Treat NoIMG as a best-effort routing hint with a very opinionated name, not as a guarantee.
+
 ## Install from npm
 
 The official package is scoped:
 
 ```bash
-npx -y @alr51307/noimg@0.3.0
+npx -y @alr51307/noimg@0.3.1
 ```
 
 Pin the version in MCP configuration so upgrades are deliberate:
@@ -32,7 +38,7 @@ Pin the version in MCP configuration so upgrades are deliberate:
   "mcpServers": {
     "noimg": {
       "command": "npx",
-      "args": ["-y", "@alr51307/noimg@0.3.0"]
+      "args": ["-y", "@alr51307/noimg@0.3.1"]
     }
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@alr51307/noimg",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "A tiny stdio-only MCP that makes @noimg mean no image generation for the current request.",
   "type": "module",
   "bin": {