Home / MCP registry index / com.gemmein/mcp

Gemmein

com.gemmein/mcp in the official MCP registry. Endpoint https://api.gemmein.com/mcp. Source: github.com/gemmeinhq/gemmein-release.

The registry describes it as: Gemmein docs, API reference, error explainers and a live integration check for coding agents.

We read its 138 tools on 2026-10-26. 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

guide changes reference search_docs explain_rule explain_error validate_collection_name reaffirm_template explain_relay check_integration app_status tools_map pull keys_list waiting_review sync declare_collection put_record update_record dev_delete_record publish_record set_payments put_relay put_ai_tool put_ai_alias put_email_template put_view rename_app test_member_add test_mail prove_app test_run_ai_tool test_pay test_outcome test_member_credits test_member_suspend test_member_unsuspend test_member_cancel_subscription request_go_live request_promote request_rename_app create_app request_add_domain request_delete_domain request_accept_terms request_revoke_server_key request_replace_every_key request_unpublish_site request_delete_collection request_delete_relay request_delete_ai_tool request_grant_credits request_suspend_person request_unsuspend_person request_delete_person request_cancel_subscription request_create_record request_update_record request_delete_record request_publish_record and 78 more

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-gemmein-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/com-gemmein-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.