npm JavaScript analyzed 1.1.8

gemini-mcp-tool

v1.1.8

npm

MCP server for Gemini CLI integration

Drift inferred · capture-to-capture

No drift recorded — single capability capture; advisories appear once its surface changes.

capabilities 0 tools

transport stdio counts 0 tools · 0 res · 0 prompts permission surface via code analysis

No tools enumerated yet for this server.

code evidence v1.1.8 · npm-tarball

evidence-backed findings quoted directly from the published source artifact — not inferred

code files: 24

fs package/dist/backends/agyTranscript.js :1 import { existsSync, readFileSync, readdirSync, statSync } from "fs";
fs package/dist/utils/chunkCache.js :2 import * as fs from 'fs';
fs package/dist/utils/commandExecutor.js :2 import { existsSync } from "fs";
fs package/dist/utils/geminiExecutor.js :2 import { readFileSync, realpathSync } from 'fs';

shell package/dist/backends/agyCapabilities.js :1 import { spawn } from "child_process";
shell package/dist/backends/agyOutput.js :1 import { spawn } from "child_process";
shell package/dist/utils/commandExecutor.js :1 import { spawn, execSync } from "child_process";

prepublishOnly package/package.json :22 echo '⚠️ Remember to test locally first!' && npm run build