Home / MCP registry index / io.github.AKzar1el/god-prompt-mcp
GodPrompt MCP Server
io.github.AKzar1el/god-prompt-mcp in the official MCP registry.
Endpoint https://god-prompt-mcp.tomi-seregi99.workers.dev/mcp. Source: github.com/AKzar1el/god-prompt-mcp.
The registry describes it as: GodPrompt MCP + Agent Skill for coding agents with TDD, debugging, verification, and task routing.
We read its 7 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_god_prompt get_core_skill get_protocols get_gates get_anti_patterns classify_task get_version
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-akzar1el-god-prompt-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.