io.github.mdvohra/agent-godmode

MCPcommunity
v0.1.9io.github.mdvohraUnknownUpdated 5mo agoGitHub

Sandboxed workspace MCP: file ops, argv-only run_command, list_files; BYO LLM prompts.

Workspace-scoped MCP tools for building Cursor-style agents: readfile, writefile, editfile, runcommand, listfiles. Includes strict, versioned system prompts () and OpenAI-style tool definitions so your app can wire any LLM with one import. The LLM and API keys stay in your app. This package provides tool execution, sandboxing, and prompts—not a hosted model. OpenAI + in-process tools: the Tier B…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5mo agoLast update
Package
Authorio.github.mdvohra
LicenseUnknown
Version0.1.9
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ Cleanv0.1.9 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Workspace-scoped MCP tools for building Cursor-style agents: readfile, writefile, editfile, runcommand, listfiles. Includes strict, versioned system prompts () and OpenAI-style tool definitions so your app can wire any LLM with one import. The LLM and API keys stay in your app. This package provides tool execution, sandboxing, and prompts—not a hosted model. OpenAI + in-process tools: the Tier B section below is self-contained—copy the Python into a script, module, or REPL; no separate artifact…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.