Home / MCP registry index / io.github.jamie7893/keelen

Keelen

io.github.jamie7893/keelen in the official MCP registry. Endpoint https://keelen.ai/mcp. Source: github.com/jamie7893/keelen-mcp.

The registry describes it as: Autonomous dev team steered from chat: plain-English requests in, tested merged PRs out.

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

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http keelen https://keelen.ai/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "keelen": {
      "url": "https://keelen.ai/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"keelen","type":"http","url":"https://keelen.ai/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

list_projects create_project submit_request get_request_status set_product_vision set_product_goal list_roadmap reorder_roadmap cancel_roadmap_item clear_horizon_pin rollback_roblox_place project_status close_task get_product_goal get_product_vision list_escalations resolve_escalation answer_planning_question retry_blocked_task requeue_for_review rearm_roadmap_item resolve_platform_regression list_steering_rules approve_steering_rule retire_steering_rule replan_task remove_cancelled_dependency control_scheduler archive_project delete_project run_security_review run_legal_exposure_review get_legal_exposure_findings run_control_gap_review get_control_gap_findings answer_request refine_request signup verify_email get_onboarding_status open_dashboard connect_github list_github_repos import_project get_provisioning_status get_billing project_digest stop_iteration

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-jamie7893-keelen/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-jamie7893-keelen)

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.