Home / MCP registry index / com.gluecron/gluecron
Gluecron
com.gluecron/gluecron in the official MCP registry.
Endpoint https://gluecron.com/mcp.
The registry describes it as: AI-native git hosting — repos, PRs, issues, CI gates, and AI code review over MCP (60 tools).
We read its 111 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
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
gluecron_repo_search gluecron_repo_read_file gluecron_repo_list_issues gluecron_repo_explain_codebase gluecron_repo_health gluecron_create_issue gluecron_comment_issue gluecron_close_issue gluecron_reopen_issue gluecron_create_pr gluecron_get_pr gluecron_list_prs gluecron_comment_pr gluecron_merge_pr gluecron_close_pr gluecron_fork_repo gluecron_delete_repo gluecron_update_repo gluecron_search_repos gluecron_whoami gluecron_clone_url gluecron_create_deploy_token gluecron_create_repo_token gluecron_list_repo_tokens gluecron_revoke_repo_token gluecron_list_tokens gluecron_get_token gluecron_rotate_token gluecron_revoke_token gluecron_list_repo_secrets gluecron_set_repo_secret gluecron_delete_repo_secret gluecron_list_deleted_repos gluecron_restore_repo gluecron_purge_repo gluecron_list_variables gluecron_get_variable gluecron_set_variable gluecron_delete_variable gluecron_delete_branch gluecron_edit_comment gluecron_delete_comment gluecron_import_action gluecron_backup_status gluecron_learning_status gluecron_label_issue gluecron_unlabel_issue gluecron_assign_issue gluecron_search_issues gluecron_request_changes gluecron_dismiss_review gluecron_search_prs gluecron_list_pr_comments gluecron_open_draft_pr gluecron_set_pr_draft gluecron_generate_pr_description gluecron_update_pr_branch gluecron_update_pr gluecron_set_auto_merge gluecron_get_pr_checks and 51 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-gluecron-gluecron)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.