Skip to content

Gluecron MCP server

com.gluecron/gluecrongluecron.comstreamable-httpv1.0.0Scanned

AI-native git hosting — repos, PRs, issues, CI gates, and AI code review over MCP (60 tools).

131 tools: 24 can delete or cancel things, 1 do something that can't be undone, 60 change things and 46 only read.

Tools: 24 delete, 1 irreversible, 60 write, 46 read.
  • Reads private data · 38
  • Reads text others write · 15
  • Can send data out · 9
  • 20 findings

Sign-in required, OAuth metadata published. Remote posture

With Anlyon

24 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Gluecron MCP server can do

The Gluecron MCP server is published by gluecron.com, a domain the MCP Registry verified. It has 131 tools. It can delete or cancel things (24 tools: merjax_close_issue, merjax_merge_pr, merjax_close_pr, merjax_delete_repo and 20 more), do things that cannot be undone, such as sending, paying or publishing (merjax_chat_continue) and create or change data (60 tools: merjax_repo_health, merjax_create_issue, merjax_comment_issue, merjax_reopen_issue and 56 more). 46 tools only read.

38 tools read private data (merjax_repo_search, merjax_repo_read_file, merjax_repo_list_issues and 35 more); 15 tools bring in text other people can write (merjax_repo_list_issues, merjax_get_pr, merjax_list_prs and 12 more); 9 tools can send data out of your system (merjax_create_issue, merjax_comment_issue, merjax_close_issue and 6 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 20 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint asks for sign-in and publishes OAuth metadata, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 13, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

131 tools

Deletes or cancels 24Claude Code: deny
  • merjax_cancel_workflow_runCancel a queued/running workflow run.No findings

    Why it is in this group

    • The name "merjax_cancel_workflow_run" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Cancel a queued/running workflow run. Requires 'repo' scope.

    Annotations the server declares

    • title: Cancel workflow run
    • readOnlyHint: false
    • destructiveHint: true
  • merjax_close_issueClose an open issue.Can send data outNo findings

    Why it is in this group

    • The name "merjax_close_issue" says "close": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "merjax_close_issue" says "close" and "issue": it writes something other people read.
    Description, as the server wrote it
    Close an open issue. Requires authenticated caller with write access. Idempotent — closing an already-closed issue is a no-op. Returns {state}.

    Annotations the server declares

    • title: Close issue
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
  • merjax_close_prClose an open pull request without merging.No findings

    Why it is in this group

    • The name "merjax_close_pr" says "close": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Close an open pull request without merging. Requires authenticated caller with write access. Idempotent. Returns {state}.

    Annotations the server declares

    • title: Close pull request
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
  • merjax_delete_branchDelete a branch the way `git push --delete` would: write access, then branch protection (allow_deletion), rulesets and the push inspection apply; webhooks and CI fire.No findings

    Why it is in this group

    • The name "merjax_delete_branch" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a branch the way `git push --delete` would: write access, then branch protection (allow_deletion), rulesets and the push inspection apply; webhooks and CI fire. The default branch is never deleted. Pass expected_sha to delete only if the branch still points there. A missing branch is a not-found error. Mirrors DELETE /api/v3/repos/:o/:r/git/refs/heads/:branch. Audit-logged. Returns {branch, sha, deleted: true}.

    Annotations the server declares

    • title: Delete a branch
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • merjax_delete_commentDelete a comment on an issue or pull request (by comment id), with its edit history.No findings

    Why it is in this group

    • The name "merjax_delete_comment" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a comment on an issue or pull request (by comment id), with its edit history. Its author or a repository writer only. A missing comment is a not-found error, never reported as deleted. Mirrors DELETE /api/v3/repos/:o/:r/issues/comments/:id. Audit-logged (who wrote it, never what it said). Returns {id, kind, number, deleted: true}.

    Annotations the server declares

    • title: Delete a comment
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • merjax_delete_fileDelete a file from a branch via git plumbing.No findings

    Why it is in this group

    • The name "merjax_delete_file" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a file from a branch via git plumbing. Requires the existing blob sha (optimistic concurrency) and 'repo' scope. Meets the same branch protection, rulesets and secret scan as a git push, and fires CI/webhooks like one. Mirrors DELETE /api/v2/contents.

    Annotations the server declares

    • title: Delete file
    • readOnlyHint: false
    • destructiveHint: true
  • merjax_delete_loop_secretDelete a hosted-loop (or organisation-level) secret by name.No findings

    Why it is in this group

    • The name "merjax_delete_loop_secret" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a hosted-loop (or organisation-level) secret by name. Pass loop (the hosted Claude loop's id, from /connect/claude/deploy) for the loop's own secret — its owner only — or org (organisation slug, admin-scoped token) for an organisation-level secret every loop of the organisation inherits; a loop-level name overrides the organisation's. ANTHROPIC_API_KEY is the loop's model key (CAP-S.8: the platform never lends its own); at organisation level it is the BYOK override. A secret that does not exist is a not-found error, never reported as deleted. Audit-logged. Returns {name, deleted: true}.

    Annotations the server declares

    • title: Delete a hosted-loop secret
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • merjax_delete_repoDelete a repository — a SOFT delete (2026-10-19): it disappears at once from git, web, REST, MCP, CI, webhooks, search and pages, its name stays reserved, and it can be restored wi…No findings

    Why it is in this group

    • The name "merjax_delete_repo" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a repository — a SOFT delete (2026-10-19): it disappears at once from git, web, REST, MCP, CI, webhooks, search and pages, its name stays reserved, and it can be restored with merjax_restore_repo until restorable_until (90 days by default). Queued/running CI is cancelled and pending webhook deliveries are stopped. Only the repository OWNER (the personal owner, or an org owner for an org repository) or a site admin may — admin collaborators and org admins are refused, as in the web UI. Requires 'admin' token scope. Audited as repo.delete; the owner is notified. To remove it for good before then, use merjax_purge_repo. Returns {deleted: true, soft: true, id, restorable_until}.

    Annotations the server declares

    • title: Delete repository (restorable)
    • readOnlyHint: false
    • destructiveHint: true
  • merjax_delete_repo_secretDelete one workflow secret from a repository by name (cron_secret is read as CRON_SECRET).No findings

    Why it is in this group

    • The name "merjax_delete_repo_secret" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete one workflow secret from a repository by name (cron_secret is read as CRON_SECRET). Idempotent: deleting a secret that is already gone succeeds with deleted:false, already_deleted:true, so a retry is safe. Workflows that reference it stop receiving it. Needs admin access to the repository and 'repo' scope. Audit-logged (name only). Returns {repository, name, deleted, already_deleted, at}.

    Annotations the server declares

    • title: Delete repository secret
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
  • merjax_delete_variableDelete an Actions variable by name.No findings

    Why it is in this group

    • The name "merjax_delete_variable" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete an Actions variable by name. Pass owner + repo for a repository variable, owner + repo + environment for an environment variable, or org for an organisation variable (organisation variables need an admin-scoped token). A variable that does not exist is a not-found error, never reported as deleted. Audit-logged. Returns {name, deleted: true}.

    Annotations the server declares

    • title: Delete an Actions variable
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • merjax_edit_commentReplace the text of a comment on an issue or pull request (by comment id).Can send data outNo findings

    Why it is in this group

    • The name "merjax_edit_comment" says "edit": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "merjax_edit_comment" says "edit" and "comment": it writes something other people read.
    Description, as the server wrote it
    Replace the text of a comment on an issue or pull request (by comment id). Its author or a repository writer only; the previous text is kept in the edit history; the same text again is `unchanged`; a concurrent edit is a conflict, never overwritten. Mentions the edit adds are notified. Mirrors PATCH /api/v3/repos/:o/:r/issues/comments/:id. Returns {id, kind, number, effect}.

    Annotations the server declares

    • title: Edit a comment
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • merjax_merge_prMerge an open PR.No findings

    Why it is in this group

    • The name "merjax_merge_pr" says "merge": a word for a change that another call does not undo.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Merge an open PR. Enforces the same checks as the HTTP merge flow: not a draft, head SHA resolves, GateTest+AI-review hard gates pass, branch-protection rules satisfied. M3: soft-blocks when the pre-merge risk score is `critical` unless `confirm_high_risk: true` is passed. Returns {merged, sha?, reason?, riskScore?}.

    Annotations the server declares

    • title: Merge pull request
    • readOnlyHint: false
    • destructiveHint: true
  • merjax_press_kill_switchPress the platform kill switch: pause every model call and suspend every personal access token minted or used in the last N hours (KILL_SWITCH_WINDOW_HOURS, default 24), platform-w…No findings

    Why it is in this group

    • The name "merjax_press_kill_switch" says "press": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Press the platform kill switch: pause every model call and suspend every personal access token minted or used in the last N hours (KILL_SWITCH_WINDOW_HOURS, default 24), platform-wide. Git, CI, merges and deploys are unaffected. One forensic audit row (security.kill_switch) names every suspended token and its previous expiry; every site admin is alerted. Site admins with an admin-scoped token only. Not idempotent: a second press suspends whatever the window holds then. Mirrors POST /api/v2/admin/security/kill-switch. Returns {at, windowHours, suspended, aiWasPaused, auditId, effect}.

    Annotations the server declares

    • title: Press the kill switch
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • merjax_purge_repoPERMANENTLY delete an already-deleted repository now, instead of waiting for its restore window to end.No findings

    Why it is in this group

    • The name "merjax_purge_repo" says "purge": a word for removing or ending something.
    • The description says "PERMANENTLY delete".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    PERMANENTLY delete an already-deleted repository now, instead of waiting for its restore window to end. IRREVERSIBLE: the git data, LFS objects, issues, PRs, releases, packages, CI history and settings are removed and cannot be restored (data already in the instance's backups ages out on the backup schedule). Only works on a repository already deleted with merjax_delete_repo; `confirm` must be its full name (owner/name). Owner (personal owner, or an org owner) or a site admin; needs 'admin' scope. Audited as repo.purge. Returns {purged: true, id, full_name}.

    Annotations the server declares

    • title: Purge deleted repository (irreversible)
    • readOnlyHint: false
    • destructiveHint: true
  • merjax_revoke_all_credentialsSite admins only (needs an 'admin'-scoped token).3 findings

    Why it is in this group

    • The name "merjax_revoke_all_credentials" says "revoke": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The annotations title mentions "credentials".

      Matched text

      annotations.title: "Revoke all credentials (admin)"

      What this check looks for
    • Info

      The description mentions "CREDENTIALS".

      Matched text

      description: "...sending `confirm` exactly: 'REVOKE ALL CREDENTIALS' for platform, 'REVOKE <username>' for..."

      What this check looks for
    • Info

      The input schema at properties.confirm.description mentions "CREDENTIALS".

      Matched text

      inputSchema.properties.confirm.description: "Exactly 'REVOKE ALL CREDENTIALS' (platform) or 'REVOKE <username>' (use..."

      What this check looks for
    Description, as the server wrote it
    Site admins only (needs an 'admin'-scoped token). Revoke every browser session, personal access token (repository tokens included) and OAuth grant — for every user (scope 'platform') or for one (scope 'user' + username). Optionally force a password reset (old password stops working, reset email sent) and 2FA re-enrolment (seeds and recovery codes deleted). Confirm by sending `confirm` exactly: 'REVOKE ALL CREDENTIALS' for platform, 'REVOKE <username>' for one user; anything else changes nothing. Platform scope revokes YOUR OWN sessions and tokens too, including the token making this call. Audit-logged. Not covered: SSH keys, passkeys, deploy keys/tokens, CI runners, app installation tokens. Returns counts, actorSignedOut and notCovered.

    Annotations the server declares

    • title: Revoke all credentials (admin)
    • readOnlyHint: false
    • destructiveHint: true
  • merjax_revoke_repo_tokenRevoke one of your fine-grained repository tokens by id (from merjax_list_repo_tokens).No findings

    Why it is in this group

    • The name "merjax_revoke_repo_token" says "revoke": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Revoke one of your fine-grained repository tokens by id (from merjax_list_repo_tokens). It stops working on its next use. Needs 'repo' scope. Audit-logged.

    Annotations the server declares

    • title: Revoke repository token
    • readOnlyHint: false
    • destructiveHint: true
  • merjax_revoke_runnerRevoke a CI runner by id: nothing is dispatched to it from now on, its next heartbeat is refused and it stops accepting jobs.No findings

    Why it is in this group

    • The name "merjax_revoke_runner" says "revoke": a word for removing or ending something.
    • The description says "Cannot be undone".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Revoke a CI runner by id: nothing is dispatched to it from now on, its next heartbeat is refused and it stops accepting jobs. Cannot be undone — register a new runner instead. Returns {id, revoked}.

    Annotations the server declares

    • title: Revoke CI runner
    • readOnlyHint: false
    • destructiveHint: true
  • merjax_revoke_tokenRevoke one of your tokens by type and id.No findings

    Why it is in this group

    • The name "merjax_revoke_token" says "revoke": a word for removing or ending something.
    • The description says "cannot be undone".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Revoke one of your tokens by type and id. It stops working on its next use; this cannot be undone. `type` is pat (personal access token, glc_), repo (repository token, gcft_) or deploy (deploy token, gcdt_). PATs need 'admin' scope; repository and deploy tokens need 'repo'. Audit-logged.

    Annotations the server declares

    • title: Revoke token
    • readOnlyHint: false
    • destructiveHint: true
  • merjax_rotate_tokenRotate one of your tokens: mint a new secret with the same name, scopes / permissions, repository and expiry, returned ONCE as `token`.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Rotate one of your tokens: mint a new secret with the same name, scopes / permissions, repository and expiry, returned ONCE as `token`. `grace_seconds` (default 0, max 604800 = 7 days) keeps the old secret working that long; 0 kills it now. Rotating again ends an earlier grace period. `expected_rotation_count` (from merjax_get_token's rotationCount) makes it compare-and-swap; two concurrent rotations never both win. `type` is pat (personal access token, glc_), repo (repository token, gcft_) or deploy (deploy token, gcdt_). PATs need 'admin' scope; repository and deploy tokens need 'repo'. Audit-logged.

    Annotations the server declares

    • title: Rotate token
    • readOnlyHint: false
    • destructiveHint: true
  • merjax_set_loop_secretCreate or replace a secret a hosted Claude loop runs with (reaches it as process.env.NAME at invoke time only; sealed at rest, scrubbed from its logs).No findings

    Why it is in this group

    • The name "merjax_set_loop_secret" says "set": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create or replace a secret a hosted Claude loop runs with (reaches it as process.env.NAME at invoke time only; sealed at rest, scrubbed from its logs). Pass loop (the hosted Claude loop's id, from /connect/claude/deploy) for the loop's own secret — its owner only — or org (organisation slug, admin-scoped token) for an organisation-level secret every loop of the organisation inherits; a loop-level name overrides the organisation's. ANTHROPIC_API_KEY is the loop's model key (CAP-S.8: the platform never lends its own); at organisation level it is the BYOK override. Safe to retry: the same value again changes nothing. Audit-logged by name, never value. Returns {name, effect: created|updated|unchanged, updatedAt}.

    Annotations the server declares

    • title: Set a hosted-loop secret
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • merjax_set_variableCreate or replace an Actions variable (plain text, not for secrets — use merjax_set_repo_secret).No findings

    Why it is in this group

    • The name "merjax_set_variable" says "set": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create or replace an Actions variable (plain text, not for secrets — use merjax_set_repo_secret). Pass owner + repo for a repository variable, owner + repo + environment for an environment variable, or org for an organisation variable (organisation variables need an admin-scoped token). Safe to retry: the same value again changes nothing. Audit-logged. Returns {name, effect: created|updated|unchanged, updatedAt}.

    Annotations the server declares

    • title: Set an Actions variable
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • merjax_ship_specDrop a spec file in .gluecron/specs/ with status: ready so the autopilot picks it up.1 finding

    Why it is in this group

    • The description's first verb is "drop": a word for removing or ending something.
    • The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "merjax_ship_spec" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false}; The description's first verb is "drop": a word for removing or ending something.

      What this check looks for
    Description, as the server wrote it
    Drop a spec file in .gluecron/specs/ with status: ready so the autopilot picks it up. Wraps voice-to-pr.shipAsSpec — handle both voice + manual specs. Requires 'repo' scope.

    Annotations the server declares

    • title: Ship spec
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_undo_kill_switchUndo the last kill switch press: give every token it suspended its previous expiry back and unpause AI (unless AI was already paused before the press, which stays as it was).1 finding

    Why it is in this group

    • The name "merjax_undo_kill_switch" says "kill": a word for removing or ending something.
    • The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "merjax_undo_kill_switch" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "merjax_undo_kill_switch" says "kill": a word for removing or ending something.

      What this check looks for
    Description, as the server wrote it
    Undo the last kill switch press: give every token it suspended its previous expiry back and unpause AI (unless AI was already paused before the press, which stays as it was). A press already undone, or none at all, is a precondition failure. Site admins with an admin-scoped token only. Audit-logged (security.kill_switch.undo); every site admin is alerted. Mirrors POST /api/v2/admin/security/kill-switch/undo. Returns {pressedAt, undoneAt, ofSuspended, restored, aiUnpaused, aiWasPaused, effect}.

    Annotations the server declares

    • title: Undo the kill switch
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • merjax_update_repoUpdate repository description / visibility / default_branch / automation dials / merge-conflict AI mode / GateTest switch.No findings

    Why it is in this group

    • The name "merjax_update_repo" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Update repository description / visibility / default_branch / automation dials / merge-conflict AI mode / GateTest switch. Requires 'admin' access on the repo (owner, org owners/admins, admin collaborators) and 'repo' scope. Returns {ok: true}; with gate_test_enabled, also gate_test {enabled, server_configured, state: on | disabled_in_settings | not_configured_on_server, details}. merjax_get_branch_protection reads gate_test without changing it.

    Annotations the server declares

    • title: Update repository settings
    • readOnlyHint: false
    • destructiveHint: true
Can't be undone 1Claude Code: ask
  • merjax_chat_continueSend another message to an existing repo chat.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe description's first verb is "send": it sends or publishes something to other people.
    • outboundThe input takes a destination (input.chat_id): what the tool writes goes there.
    Description, as the server wrote it
    Send another message to an existing repo chat. Returns the assistant's reply. If the AI service does not answer this fails with a JSON-RPC error carrying {chat_id, ai_error} rather than returning apology copy as a reply.

    Annotations the server declares

    • title: Continue repository chat
    • readOnlyHint: false
    • destructiveHint: false
Changes things 60Claude Code: ask
  • merjax_acquire_leaseGrab an exclusive lease on a PR, issue, branch or file path in a repository you can write, for one of your agent sessions.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Grab an exclusive lease on a PR, issue, branch or file path in a repository you can write, for one of your agent sessions. Pass owner+repo with a bare key (PR/issue number, branch name, path), or target_id '<repository id>:<key>'. Returns lease null when another agent holds an active lease.

    Annotations the server declares

    • title: Acquire lease
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_apply_patchCommit a patch to a branch without sending whole files — the way to change a few lines of a large file.No findings

    Why it is in this group

    • The name "merjax_apply_patch" says "apply": a word for a change.
    Description, as the server wrote it
    Commit a patch to a branch without sending whole files — the way to change a few lines of a large file. `patch` is a unified diff as `git diff` prints it (one commit, `message` required) OR `git format-patch` mbox output (each patch becomes its own commit with the patch's own message and author, like `git am`; `message` is ignored). Applied server-side with `git apply --cached` against the branch head (created from `base_branch` if missing); blank context lines a transport stripped to empty lines, or trimmed off the end of the patch, are restored first (git still checks them against the file). `expected_head_sha` makes it compare-and-swap (all zeros = branch must not exist yet). Meets the same branch protection, rulesets and secret scan as a git push, and fires CI/webhooks like one. Patch limit 2 MiB. Requires 'repo' scope. Returns {branch, commit_sha, parent_sha, files_changed, files, commits, created} (+ blank_context_lines_restored / trimmed_blank_context_lines_restored when a repair was needed).

    Annotations the server declares

    • title: Apply patch
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_approve_prApprove a pull request: records an 'approved' review by the caller — the same review the web form and POST /api/v2/repos/:owner/:repo/pulls/:number/reviews write, so it counts towa…No findings

    Why it is in this group

    • The name "merjax_approve_pr" says "approve": a word for a change.
    Description, as the server wrote it
    Approve a pull request: records an 'approved' review by the caller — the same review the web form and POST /api/v2/repos/:owner/:repo/pulls/:number/reviews write, so it counts toward branch protection's required approvals and clears the caller's own earlier request for changes. The PR must be open; its author cannot approve it. Requires write access and 'repo' scope. To request changes use merjax_request_changes. Returns {reviewId, number, state, url}.

    Annotations the server declares

    • title: Approve pull request
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_assign_issueAssign (or, with remove: true, unassign) users on an issue or pull request.Can send data outNo findings

    Why it is in this group

    • The name "merjax_assign_issue" says "assign": a word for a change.

    What it can reach

    • outboundThe name "merjax_assign_issue" says "assign" and "issue": it writes something other people read.
    Description, as the server wrote it
    Assign (or, with remove: true, unassign) users on an issue or pull request. Real assignees since 2026-10-12 — up to 10 per thread, only users who can read the repository; the old `assignee:<username>` labels were migrated. Pass `assignee` (one username) or `assignees` (array). `type` is 'issue' (default) or 'pull_request'. Requires 'repo' scope and write access. Returns {assigned, skipped:[{username, reason}], removed, assignees}.

    Annotations the server declares

    • title: Assign issue
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
  • merjax_atomic_multi_file_commitApply a set of file writes + deletes as a single atomic commit on a branch (creates the branch if it doesn't exist).No findings

    Why it is in this group

    • The name "merjax_atomic_multi_file_commit" says "commit": a word for a change.
    Description, as the server wrote it
    Apply a set of file writes + deletes as a single atomic commit on a branch (creates the branch if it doesn't exist). The killer agent tool: blob/tree/commit/ref-update sequence. Each change is `{path, content?, content_base64?, deleted?}`. Meets the same branch protection, rulesets and secret scan as a git push, and fires CI/webhooks like one. Requires 'repo' scope.

    Annotations the server declares

    • title: Atomic multi-file commit
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_backup_statusSite admins only (needs an 'admin'-scoped token).1 finding

    Why it is in this group

    • The name "merjax_backup_status" says "status": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "merjax_backup_status" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false}; The name "merjax_backup_status" says "status": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Site admins only (needs an 'admin'-scoped token). Backup and restore-drill health: whether the newest backup set is verified on an offsite target and how old it is, whether offsite copies are immutable (Object Lock), when a restore drill last passed, whether the backup worker is running, plus targets (host/bucket, never keys), schedule and recent runs. A stale, failed, local-only or never-drilled backup reads RED. Pass start: 'backup' or 'drill' to queue one for the worker (picked up within 15 minutes; audit-logged). Returns {health, reasons, targets, problems, schedule, runs, started?}.

    Annotations the server declares

    • title: Backup status (admin)
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_chat_with_repoStart a new chat with a repo: creates a chat row, sends the first user message, streams + persists the assistant reply.No findings

    Why it is in this group

    • The description's first verb is "start": a word for a change.
    Description, as the server wrote it
    Start a new chat with a repo: creates a chat row, sends the first user message, streams + persists the assistant reply. Returns {chat_id, reply}. If the AI service does not answer this fails with a JSON-RPC error carrying {chat_id, ai_error} — it never returns apology copy as a reply. Requires authentication.

    Annotations the server declares

    • title: Chat with repository
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_ci_executorWhere CI runs and why: mode (external | in-process), declaration (external | in-process | auto) and its source (CI_EXECUTOR on the box, the estate-wide setting, or auto), runners c…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Where CI runs and why: mode (external | in-process), declaration (external | in-process | auto) and its source (CI_EXECUTOR on the box, the estate-wide setting, or auto), runners configured / reachable / busy / slots, lastSeenAt, state (ok | degraded | unconfigured | in-process) and holdReason — the sentence every queued run shows when no runner can take it. In-process never runs while external runners are configured. Site admins (admin scope) also get per-runner rows and may pass `declare` (external | in-process | auto) to set the estate-wide setting, audited (the answer then carries `saved`). Same as GET/PUT /api/v2/ci/executor and /admin/runners.

    Annotations the server declares

    • title: CI executor status
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_ci_healthCI health, the same as GET /api/v2/ci/health and /admin/ci: status, the paging rules (queue p95, runner silent, timeout rate, heavy on the app box, runner_slow: a runner over 2x sl…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    CI health, the same as GET /api/v2/ci/health and /admin/ci: status, the paging rules (queue p95, runner silent, timeout rate, heavy on the app box, runner_slow: a runner over 2x slower than its pool's fastest on the same heavy jobs), queue wait p50/p95 by work class, outcome rates, capacity, runnerSpeed24h (each runner's slowdown against its pool), and `measures`: capacity:compute_trigger (Tallrig ESTATE_PLAN §5's compute row: p95 push-to-start over 5 min for 7 days, or busy slots over 70% for 7 days) with firing, value, window, source and each day. Site admins (admin scope) also get `dashboard` (CAP-0.4) for 24 h and 7 d: startTimes (queue → start p50/p95 by class and pool), duplicateMinutes (lease time on a tree, workflow and job that already had a green job), poolCost (minutes per pool; a cost only where CI_POOL_COST_PER_MINUTE sets one, else 'cost not configured'), notMerged (merge-train dequeue and auto-merge reasons, counted), nonBillable (platform repositories on our machines vs customers'), testSelection (CAP-1.4: minutes saved by test selection and reuse, against full-run medians). Every number carries `source`: the table or setting it was read from. Read-only.

    Annotations the server declares

    • title: CI health
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_comment_issueAdd a comment to an existing issue.Can send data outNo findings

    Why it is in this group

    • The name "merjax_comment_issue" says "comment": a word for a change.

    What it can reach

    • outboundThe name "merjax_comment_issue" says "comment" and "issue": it writes something other people read.
    Description, as the server wrote it
    Add a comment to an existing issue. Requires authenticated caller with write access. Returns {commentId}.

    Annotations the server declares

    • title: Comment on issue
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_comment_prAdd a comment to a pull request.No findings

    Why it is in this group

    • The name "merjax_comment_pr" says "comment": a word for a change.
    Description, as the server wrote it
    Add a comment to a pull request. Requires authenticated caller with write access. Returns {commentId}.

    Annotations the server declares

    • title: Comment on pull request
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_commit_pr_conflict_resolutionCommit the saved resolutions for a PR's conflicts ON THE PR HEAD as a two-parent merge commit (old head, base tip) — never on the base branch — moved through the push gates so CI r…No findings

    Why it is in this group

    • The name "merjax_commit_pr_conflict_resolution" says "commit": a word for a change.
    Description, as the server wrote it
    Commit the saved resolutions for a PR's conflicts ON THE PR HEAD as a two-parent merge commit (old head, base tip) — never on the base branch — moved through the push gates so CI runs on it before anything merges. Every unresolved file needs a draft (merjax_resolve_pr_conflict) or an entry in `resolutions`; files the merge rules settle are settled automatically. Both shas are compare-and-swapped: a branch that moved since is refused with nothing changed. The commit carries `Conflict-Resolution:` trailers; a gluecron[bot] comment records it. Requires write access and 'repo' scope.

    Annotations the server declares

    • title: Commit PR conflict resolution
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_create_agent_sessionMint a new agent-multiplayer session.No findings

    Why it is in this group

    • The name "merjax_create_agent_session" says "create": a word for a change.
    Description, as the server wrote it
    Mint a new agent-multiplayer session. Returns the plaintext `token` exactly once (store it). Requires 'admin' scope.

    Annotations the server declares

    • title: Create agent session
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_create_branchCreate a new branch ref pointing at an existing sha.No findings

    Why it is in this group

    • The name "merjax_create_branch" says "create": a word for a change.
    Description, as the server wrote it
    Create a new branch ref pointing at an existing sha. Mirrors POST /api/v2/repos/.../git/refs. Gated like a push of the new branch (rulesets, secret scan of commits no other ref reaches) and fires CI/webhooks. Requires 'repo' scope. Returns {ref, sha}.

    Annotations the server declares

    • title: Create branch
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_create_deploy_tokenMint a short-lived, repository-scoped HTTPS clone credential (a deploy token) for a sandbox or CI box that has no PAT.2 findings

    Why it is in this group

    • The name "merjax_create_deploy_token" says "create": a word for a change.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...rt-lived, repository-scoped HTTPS clone credential (a deploy token) for a sandbox or CI bo..."

      What this check looks for
    • Info

      The input schema at properties.deliver.description mentions "credential".

      Matched text

      inputSchema.properties.deliver.description: "...(default): a single-use 60 s URL git's credential helper spends — the secret never appear..."

      What this check looks for
    Description, as the server wrote it
    Mint a short-lived, repository-scoped HTTPS clone credential (a deploy token) for a sandbox or CI box that has no PAT. By default it returns NO token: {id, exchangeUrl, exchangeExpiresAt, gitConfig, url}. Run the gitConfig lines right before the first clone/fetch (the URL is single-use and dies in 60 s) and git fetches the token itself, so it never enters your transcript. Read-only by default; `read_only: false` asks for push access and is granted only if you have write access. Expires in 2 h by default (`expires_in_hours`, max 24). Needs owner / collaborator / team / org access to the repo (public read is not enough) and 'repo' scope. Audit-logged. Pass `token_id` (an id this tool returned) for a fresh exchange URL for the same grant; each exchange rotates the secret. `deliver: "token"` returns a read-only secret in the result instead (refused for push access: a push-capable secret in an agent's transcript outlives the run). Revoke the grant with merjax_revoke_token {type: "deploy", id}.

    Annotations the server declares

    • title: Create deploy token
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_create_issueCreate a new issue on a Merjax repository.Can send data outNo findings

    Why it is in this group

    • The name "merjax_create_issue" says "create": a word for a change.

    What it can reach

    • outboundThe name "merjax_create_issue" says "create" and "issue": it writes something other people read.
    Description, as the server wrote it
    Create a new issue on a Merjax repository. Requires authenticated caller with write access on the target repo. Returns {number, url}.

    Annotations the server declares

    • title: Create issue
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_create_prOpen a new pull request.No findings

    Why it is in this group

    • The name "merjax_create_pr" says "create": a word for a change.
    Description, as the server wrote it
    Open a new pull request. `head_branch` is required; `base_branch` defaults to the repo default branch. Requires authenticated caller with write access. Returns {number, url}.

    Annotations the server declares

    • title: Create pull request
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_create_repo_tokenMint a fine-grained repository token (`gcft_…`) for ONE repository and return it once.No findings

    Why it is in this group

    • The name "merjax_create_repo_token" says "create": a word for a change.
    Description, as the server wrote it
    Mint a fine-grained repository token (`gcft_…`) for ONE repository and return it once. It authenticates the REST API (/api/v2 and the GitHub-compatible /api/v3), git over HTTPS and the container registry (images under owner/repo, by contents) for that repository only. `permissions` sets none/read/write for contents, issues, pull_requests, statuses and actions, and none/read for runners (admin and settings are never grantable); `expires_in` is optional: omit it (or "never") for no expiration, or give seconds or "30m", "12h", "7d", "1y" (min 5 minutes, max 1 year). Effective access is always held to YOUR current access to the repo, re-checked on every use, and branch protection applies as it does to you. Needs 'repo' scope. Audit-logged. Returns {id, name, repository, permissions, expiresAt, tokenPrefix, token}.

    Annotations the server declares

    • title: Create repository token
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_create_runner_registration_tokenCreate a one-time CI runner registration token for an owner (your username, an org you own or admin, or 'platform' as a site admin).1 finding

    Why it is in this group

    • The name "merjax_create_runner_registration_token" says "create": a word for a change.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...isters once and gets its own long-lived credential; that owner's CI then runs on it. Expir..."

      What this check looks for
    Description, as the server wrote it
    Create a one-time CI runner registration token for an owner (your username, an org you own or admin, or 'platform' as a site admin). A runner started with RUNNER_REGISTRATION_TOKEN=<token> registers once and gets its own long-lived credential; that owner's CI then runs on it. Expires in an hour. Pass exclusive: true for a label-only runner (a Mac for Xcode, a GPU box): it takes only jobs whose runs-on names its labels (e.g. [self-hosted, macos, xcode]), never runs-on: self / ubuntu-*, and the account keeps its shared lane; repositories narrows it to some of the owner's repositories. Both are fixed for the runner's life. Returns {owner, token, expiresAt, exclusive, repositoryIds, gluecronUrl}.

    Annotations the server declares

    • title: Create runner registration token
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_dismiss_reviewDismiss the standing 'changes requested' reviews on a PR (all of them, or one reviewer's), so they no longer hold the merge.No findings

    Why it is in this group

    • The name "merjax_dismiss_review" says "dismiss": a word for a change.
    Description, as the server wrote it
    Dismiss the standing 'changes requested' reviews on a PR (all of them, or one reviewer's), so they no longer hold the merge. Requires 'repo' scope and write access; the reason is required and audited.

    Annotations the server declares

    • title: Dismiss a request for changes
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_fork_repoFork a repository to the authenticated caller's namespace.No findings

    Why it is in this group

    • The name "merjax_fork_repo" says "fork": a word for a change.
    Description, as the server wrote it
    Fork a repository to the authenticated caller's namespace. Mirrors POST /:owner/:repo/fork. Returns {owner, repo, url}. Requires 'repo' scope.

    Annotations the server declares

    • title: Fork repository
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_generate_commit_messageGenerate a commit message for a diff.Can send data out1 finding

    Why it is in this group

    • The name "merjax_generate_commit_message" says "generate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe name "merjax_generate_commit_message" says "generate" and "message": it writes something other people read.

    Findings

    • Warn

      The server marks "merjax_generate_commit_message" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false}; The name "merjax_generate_commit_message" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Generate a commit message for a diff. Same engine as merjax_generate_pr_description but explicit for the commit-message use case.

    Annotations the server declares

    • title: Generate commit message
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_generate_pr_descriptionGenerate an AI commit-message-style description for a diff.1 finding

    Why it is in this group

    • The name "merjax_generate_pr_description" says "generate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "merjax_generate_pr_description" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false}; The name "merjax_generate_pr_description" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Generate an AI commit-message-style description for a diff. Uses src/lib/ai-commit-message.ts under the hood; gracefully degrades to a heuristic when ANTHROPIC_API_KEY is missing. Returns {subject, body}.

    Annotations the server declares

    • title: Generate PR description
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_generate_release_notesGenerate release notes between two tags.1 finding

    Why it is in this group

    • The name "merjax_generate_release_notes" says "generate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "merjax_generate_release_notes" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false}; The name "merjax_generate_release_notes" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Generate release notes between two tags. Wraps src/lib/ai-release-notes.generateReleaseNotes. Returns the rendered Markdown + section data.

    Annotations the server declares

    • title: Generate release notes
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_generate_testsGenerate tests for a PR via Claude.No findings

    Why it is in this group

    • The name "merjax_generate_tests" says "generate": a word for a change.
    Description, as the server wrote it
    Generate tests for a PR via Claude. Wraps src/lib/ai-test-generator.generateTestsForPr. Mode 'follow-up-pr' opens a new PR; 'append-commit' commits onto the head branch. Requires 'repo' scope.

    Annotations the server declares

    • title: Generate tests for PR
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_handoverStart here when picking up work: the live state of a repository, read from git and CI rather than from a handoff doc.1 finding

    Why it is in this group

    • The description's first verb is "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "merjax_handover" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false}; The description's first verb is "start": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Start here when picking up work: the live state of a repository, read from git and CI rather than from a handoff doc. Returns `summary` (one paragraph), `blockers` (most urgent first), the default branch's CI per workflow (red streak, since when, last green run), the build this Merjax instance serves and how many commits it is behind (when it is this repository), every open PR grouped green / pending / failing / draft as the merge gate judges it, PRs merged in the last `merged_since_hours` (default 48), the CI queue, and — when the default branch carries `docs/plans/capacity-plan.json` — `plan`: the next items, items in flight, decisions waiting on the owner and drift between the ledger and the PRs; and `plans`, the same for every `docs/plans/*-plan.json` ledger (each read with the `idPrefix` it declares, default CAP; at most 10). Read-only.

    Annotations the server declares

    • title: Handover
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_import_actionSite admins only (needs an 'admin'-scoped token).No findings

    Why it is in this group

    • The name "merjax_import_action" says "import": a word for a change.
    Description, as the server wrote it
    Site admins only (needs an 'admin'-scoped token). Import a third-party GitHub Action at ONE tag, branch or full commit SHA into the Merjax mirror namespace (gluecron-actions/<owner>--<repo>), so workflows that say `uses: owner/repo@ref` can run it. Workflow runs never fetch from github.com; an action that is not imported is skipped. Re-importing the same ref updates it to what upstream has now. Audit-logged. Returns {action, ref, sha, previousSha, mirror, upstreamUrl, hasActionYml}.

    Annotations the server declares

    • title: Import action (admin)
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_label_issueAttach one or more labels to an issue.Can send data outNo findings

    Why it is in this group

    • The name "merjax_label_issue" says "label": a word for a change.

    What it can reach

    • outboundThe name "merjax_label_issue" says "label" and "issue": it writes something other people read.
    Description, as the server wrote it
    Attach one or more labels to an issue. Labels are created if they don't yet exist on the repo. Requires 'repo' scope. Returns {labels}.

    Annotations the server declares

    • title: Label issue
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_open_draft_prOpen a draft pull request.No findings

    Why it is in this group

    • The name "merjax_open_draft_pr" says "open": a word for a change.
    Description, as the server wrote it
    Open a draft pull request. Same payload as merjax_create_pr but forces is_draft=true. Useful for AI-in-progress PRs that shouldn't run mergeability checks yet.

    Annotations the server declares

    • title: Open draft pull request
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_prioritize_workflow_runMove a QUEUED workflow run into the priority lane: the runner claims it ahead of the class order, highest `level` first (normal < high < critical), then oldest (issue #10898).No findings

    Why it is in this group

    • The name "merjax_prioritize_workflow_run" says "run": a word for a change.
    Description, as the server wrote it
    Move a QUEUED workflow run into the priority lane: the runner claims it ahead of the class order, highest `level` first (normal < high < critical), then oldest (issue #10898). The lane holds at most a third of the runner slots, so prioritizing many runs cannot starve the rest. Calling again on a prioritized queued run changes its level. Only queued runs; a running or finished run is reported, not changed. Requires 'repo' scope and write access; `high` and `critical` also require a site admin.

    Annotations the server declares

    • title: Prioritize workflow run
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
  • merjax_propose_doc_updateManual trigger for the AI doc-update flow: scans tracked sections on the default branch and opens a PR rewriting stale prose.No findings

    Why it is in this group

    • The name "merjax_propose_doc_update" says "update": a word for a change.
    Description, as the server wrote it
    Manual trigger for the AI doc-update flow: scans tracked sections on the default branch and opens a PR rewriting stale prose. Requires 'repo' scope.

    Annotations the server declares

    • title: Propose doc update PR
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_propose_migrationPropose a dependency-upgrade PR.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Propose a dependency-upgrade PR. Wraps src/lib/migration-assistant.proposeMajorMigration. Requires 'repo' scope.

    Annotations the server declares

    • title: Propose migration PR
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_propose_pr_conflict_resolutionAsk AI (Opus 5.5) to PROPOSE a resolution for each conflict block of a PR's text files — the Conflicts tab's 'Propose resolutions' button.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Ask AI (Opus 5.5) to PROPOSE a resolution for each conflict block of a PR's text files — the Conflicts tab's 'Propose resolutions' button. Nothing is committed: each proposal (the block's lines, an explanation, a confidence 0..1) is stored for the (base, head) pair and shown on the Conflicts tab and in merjax_list_pr_conflicts (`unresolved[].proposal`); accept a block with merjax_resolve_pr_conflict `choices: {<hunk id>: 'ai'}`, edit it with a custom choice, or pick another option, then merjax_commit_pr_conflict_resolution. Refused when the repository's merge-conflict mode is Manual only, when the PR author opted out of AI for conflicts, or when AI is unavailable (paused, not configured, over budget) — the error says which. A file over 60 KiB is reported too-large; repository text is sent as fenced data with secrets redacted. A file already proposed at this pair is not sent again unless again: true. Requires write access and 'repo' scope.

    Annotations the server declares

    • title: Propose PR conflict resolutions (AI)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
  • merjax_provision_pr_sandboxProvision (or re-provision) a sandbox for a PR.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Provision (or re-provision) a sandbox for a PR. Wraps pr-sandbox.provisionSandbox. Requires 'repo' scope. Returns {ok:false, reason:'not enabled on this host'} when no sandbox provisioner runs on the host.

    Annotations the server declares

    • title: Provision PR sandbox
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_refactor_across_reposPlan + execute a refactor that spans multiple repos owned by the caller.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Plan + execute a refactor that spans multiple repos owned by the caller. Wraps src/lib/multi-repo-refactor.ts. `dry_run: true` returns the plan only. Requires 'repo' scope.

    Annotations the server declares

    • title: Refactor across repos
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_release_leaseRelease a lease by id.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Release a lease by id. Idempotent. Returns {released}.

    Annotations the server declares

    • title: Release lease
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
  • merjax_reopen_issueReopen a previously closed issue.Can send data outNo findings

    Why it is in this group

    • The name "merjax_reopen_issue" says "reopen": a word for a change.

    What it can reach

    • outboundThe name "merjax_reopen_issue" says "reopen" and "issue": it writes something other people read.
    Description, as the server wrote it
    Reopen a previously closed issue. Requires authenticated caller with write access. Idempotent. Returns {state}.

    Annotations the server declares

    • title: Reopen issue
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
  • merjax_repo_healthCompute the current health report for a public repo: overall score (0-100), letter grade, per-category breakdown (security/testing/complexity/dependencies/documentation/activity), …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Compute the current health report for a public repo: overall score (0-100), letter grade, per-category breakdown (security/testing/complexity/dependencies/documentation/activity), and a list of insights to fix next. Backed by computeHealthScore in src/lib/intelligence.ts.

    Annotations the server declares

    • title: Repository health report
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_repo_ratingThe repository's letter rating A+/A/B/C/D/F — the health report's grade (the same number merjax_repo_health and the /health page show; A is 85+) — with the score, the six categorie…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The repository's letter rating A+/A/B/C/D/F — the health report's grade (the same number merjax_repo_health and the /health page show; A is 85+) — with the score, the six categories (score, weight, points still available), `to_a`: the ordered list of concrete items that move the repository to A (each with the action, the points available, whether a loop can do it mechanically, and the evidence: file:line for a security finding, counts otherwise), then the delivery blockers beside it (red default branch, conflicting PRs, PRs red for a week, open ai:repair issues, issues older than 30 days — shown under `delivery`, never merged into the letter), and the last 30 recorded days. Owner mandate 2026-11-04: every repository should be A. Read-only.

    Annotations the server declares

    • title: Repository letter rating
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_request_changesRequest changes on a PR.No findings

    Why it is in this group

    • The name "merjax_request_changes" says "request": a word for a change.
    Description, as the server wrote it
    Request changes on a PR. Records a 'changes requested' review by the caller, which holds the PR on every merge path (web button, API, MCP merge, merge queue, merge train, autopilot) until the caller approves or someone with write access dismisses it (merjax_dismiss_review), and posts the body as a comment. Requires 'repo' scope and write access.

    Annotations the server declares

    • title: Request PR changes
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_rerun_failed_jobsRe-run a failed or cancelled workflow run at the SAME commit (same inputs, same PR merge preview) — the run page's Re-run.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Re-run a failed or cancelled workflow run at the SAME commit (same inputs, same PR merge preview) — the run page's Re-run. Merjax re-runs every job of the run (per-job re-run does not exist yet); a successful or still-running run is refused. Joins an identical queued run instead of stacking another. Requires write access and 'repo' scope. Returns {runId, previousRunId, joinedExistingRun, url}.

    Annotations the server declares

    • title: Re-run failed workflow run
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_resolve_pr_conflictSave a resolution for ONE conflicted file of a PR, as a draft for the exact (base_sha, head_sha) pair merjax_list_pr_conflicts returned (a moved branch is refused: reload).Reads private dataNo findings

    Why it is in this group

    • The name "merjax_resolve_pr_conflict" says "resolve": a word for reading.
    • The description's first verb is "save": a word for a change.

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    Save a resolution for ONE conflicted file of a PR, as a draft for the exact (base_sha, head_sha) pair merjax_list_pr_conflicts returned (a moved branch is refused: reload). Pass exactly one of: `content` (the whole resolved file — no conflict markers, at most 512 KiB), `choices` (hunk id → 'mine' | 'main' | 'both-mine-first' | 'both-main-first' | 'base' | 'ai' (the block's AI proposal from merjax_propose_pr_conflict_resolution) | {kind:'custom', lines:[…]}; applied server-side, a stale hunk id is refused), or `keep` ('mine' = the PR branch's version, 'main' = the base branch's; the only options for binary files and files one side deleted). Nothing is committed until merjax_commit_pr_conflict_resolution. Requires write access and 'repo' scope.

    Annotations the server declares

    • title: Resolve one PR conflict (draft)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
  • merjax_restore_repoRestore a deleted repository by id (from merjax_list_deleted_repos) before its restorable_until date: git data, LFS objects, issues, PRs, collaborators and webhooks come back exact…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Restore a deleted repository by id (from merjax_list_deleted_repos) before its restorable_until date: git data, LFS objects, issues, PRs, collaborators and webhooks come back exactly as they were. Cancelled CI runs stay cancelled and stopped webhook deliveries are not re-sent. Refused when another repository now has the same name in that namespace. Owner (personal owner, or an org owner) or a site admin; needs 'admin' scope. Audited as repo.restore. Returns {restored: true, id, full_name}.

    Annotations the server declares

    • title: Restore deleted repository
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_resume_tokenResume one of your personal access tokens that suspended itself (daily bucket spent, or the tripwire): it authenticates again; today's spend still counts against its bucket, so rai…1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...nnot make this call itself: use another credential. A token that is not suspended is `unch..."

      What this check looks for
    Description, as the server wrote it
    Resume one of your personal access tokens that suspended itself (daily bucket spent, or the tripwire): it authenticates again; today's spend still counts against its bucket, so raise the bucket first with merjax_set_token_bucket if it is spent. A suspended token cannot make this call itself: use another credential. A token that is not suspended is `unchanged`; another person's token is not found. Needs `user` scope. Audit-logged. Returns {tokenId, name, resumed, effect}.

    Annotations the server declares

    • title: Resume a suspended token
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • merjax_review_deploymentApprove or reject a workflow run's jobs waiting on a protected environment (`environment:` with required reviewers).No findings

    Why it is in this group

    • The description's first verb is "approve": a word for a change.
    Description, as the server wrote it
    Approve or reject a workflow run's jobs waiting on a protected environment (`environment:` with required reviewers). The caller must be a reviewer of every environment selected (the environment's reviewers, or the repository owner when none are listed). An approval runs the job (after the environment's wait timer, if any); a rejection fails it. Mirrors POST /api/v2/repos/.../actions/runs/:id/pending_deployments. Requires 'repo' scope.

    Annotations the server declares

    • title: Review deployment
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_security_ioc_hitsSite admins only (needs an 'admin'-scoped token).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Site admins only (needs an 'admin'-scoped token). Campaign indicator-of-compromise hits: pushes, token uses and repositories that matched a reviewed signature in src/lib/security/campaign-iocs.json (e.g. the Gheist campaign: ci-sync-XXXXXX branches, sync-check.yml, user agent 'gheist'). Filter by signature_id, repository ('owner/name'), since (ISO date); limit (default 50, max 200) / offset. Returns {signatureVersion, signatures, totals, sweep, hits[{id, signatureId, campaign, severity, detectedBy, repository, ref, sha, tokenKind, tokenId, userAgent, evidence, createdAt}]}. Read-only; nothing is revoked.

    Annotations the server declares

    • title: Campaign IoC hits (admin)
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_security_scanEverything Merjax actually knows about a repository's security, in one honest call: OSV.dev CVE/GHSA advisories against the indexed dependency graph (with FIXED VERSIONS), Merjax's…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Everything Merjax actually knows about a repository's security, in one honest call: OSV.dev CVE/GHSA advisories against the indexed dependency graph (with FIXED VERSIONS), Merjax's supplemental advisory list, a full-tree committed-secret scan, and optionally a Claude semantic code review. Unlike merjax_repo_health, an empty result is NEVER reported as a pass: every category returns status 'assessed' | 'partial' | 'not_assessed' | 'error' with a machine-readable reason code, so you can tell 'we checked and it is clean' from 'we never looked'. In particular, a repo whose dependency graph was never indexed returns dependency_advisories.status='not_assessed' (reason 'dependency_graph_not_indexed'), not an empty advisory list. Read-only.

    Annotations the server declares

    • title: Repository security scan (honest coverage)
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_set_ai_workspace_quotaSet a provider workspace's daily spend limit (cents, UTC day) and calls per minute; 0 = no cap at that level (the platform ceiling still applies).No findings

    Why it is in this group

    • The name "merjax_set_ai_workspace_quota" says "set": a word for a change.
    Description, as the server wrote it
    Set a provider workspace's daily spend limit (cents, UTC day) and calls per minute; 0 = no cap at that level (the platform ceiling still applies). Site admins with an admin-scoped token only. Safe to retry: the same numbers again change nothing. Audit-logged. Mirrors PUT /api/v2/admin/ai-workspaces/:workspace/quota. Returns {workspace, dailyCents, rpm, effect: updated|unchanged}.

    Annotations the server declares

    • title: Set an AI workspace's quotas
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • merjax_set_auto_mergeArm (enabled: true) or disarm (enabled: false) auto-merge on one PR: it merges by itself through the full gated merge chain (CI, required checks, branch protection, CODEOWNERS, ris…No findings

    Why it is in this group

    • The name "merjax_set_auto_merge" says "set": a word for a change.
    Description, as the server wrote it
    Arm (enabled: true) or disarm (enabled: false) auto-merge on one PR: it merges by itself through the full gated merge chain (CI, required checks, branch protection, CODEOWNERS, risk) once CI and every required check are green and no reviewer with write access has changes requested. Stays armed while anything is pending; `last_attempt.reason` says what it waits for. Arming is also the merge train's consent: on a repository with the train on, the train merges only armed PRs, so disarming holds the PR from it (an explicit merjax_merge_pr still merges). Requires write access and 'repo' scope. merge_method: 'merge' only. Returns {number, auto_merge}.

    Annotations the server declares

    • title: Set PR auto-merge
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
  • merjax_set_branch_protectionSet branch protection for one branch (partial update: fields you omit keep their value).No findings

    Why it is in this group

    • The name "merjax_set_branch_protection" says "set": a word for a change.
    Description, as the server wrote it
    Set branch protection for one branch (partial update: fields you omit keep their value). Edits the rule named exactly after the branch; when only a glob rule covers it, a new exact rule is created seeded from the glob's settings and checks. required_checks replaces the required-check list; it may add checks, but REMOVING a check that applies to the branch is refused here (it needs a step-up: the web page or the REST API with the account password). require_pr_run: a required check that names a workflow is met only by that workflow's pull_request run. Requires ADMIN access to the repo and 'repo' scope. Audit-logged. Returns the resulting rule plus {created, warnings}.

    Annotations the server declares

    • title: Set branch protection
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
  • merjax_set_pr_ai_settingsChoose the model for a pull request's AI tasks (review, risk summary, CI fixes, conflict proposals): a model id from the catalog, or null / "" to inherit the repository's or the pl…No findings

    Why it is in this group

    • The name "merjax_set_pr_ai_settings" says "set": a word for a change.
    Description, as the server wrote it
    Choose the model for a pull request's AI tasks (review, risk summary, CI fixes, conflict proposals): a model id from the catalog, or null / "" to inherit the repository's or the platform's choice. Write access to the repository. run_via ("subscription" or "api": where AI runs and who pays) is for site admins only, with an admin-scoped token, and the subscription only on a repository a site admin owns. Omitted fields are kept; the same values again are `unchanged`. A model below a task's floor is raised and the effective list says so. Mirrors PUT /api/v2/repos/:o/:r/pulls/:n/ai-settings. Audit-logged. Returns {number, effect, model, repository_model, effective:[{task, label, model, model_label, source, raised, note}], updated_at} plus the run-on fields for a site admin.

    Annotations the server declares

    • title: Set a pull request's AI model
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • merjax_set_pr_draftMark a pull request ready for review (draft=false) or convert it back to a draft (draft=true).No findings

    Why it is in this group

    • The name "merjax_set_pr_draft" says "set": a word for a change.
    Description, as the server wrote it
    Mark a pull request ready for review (draft=false) or convert it back to a draft (draft=true). Same rule as the web 'Ready for review' button: the caller needs write access and must be the PR author or the repository owner; only an open PR changes; marking ready starts the AI review. Idempotent. Requires 'repo' scope. Returns {number, isDraft, changed}.

    Annotations the server declares

    • title: Set PR draft state
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
  • merjax_set_repo_secretCreate or replace one workflow secret on a repository, used in workflows as ${{ secrets.NAME }}.No findings

    Why it is in this group

    • The name "merjax_set_repo_secret" says "set": a word for a change.
    Description, as the server wrote it
    Create or replace one workflow secret on a repository, used in workflows as ${{ secrets.NAME }}. The name is saved upper-cased (cron_secret → CRON_SECRET); trailing spaces/newlines are removed from the value. The value is WRITE-ONLY: it is encrypted at rest and never returned, logged or audited — the result names the secret only. Pass expected_updated_at (the updated_at you last read) to update only if nobody changed it since: a newer value is never overwritten (error 'conflict'), a deleted secret is not re-created (error 'missing'). Setting the value it already has writes nothing (result 'unchanged'), so a retry is safe. Needs admin access to the repository and 'repo' scope. Audit-logged (name only). Returns {repository, name, created, result: 'created'|'updated'|'unchanged', updated_at}.

    Annotations the server declares

    • title: Set repository secret
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_set_token_bucketSet the daily model-spend bucket of one of your personal access tokens: daily_cents (1–1000000; 0 = the platform default; -1 = no bucket) or daily_usd ("2.50", "default", "none").No findings

    Why it is in this group

    • The name "merjax_set_token_bucket" says "set": a word for a change.
    Description, as the server wrote it
    Set the daily model-spend bucket of one of your personal access tokens: daily_cents (1–1000000; 0 = the platform default; -1 = no bucket) or daily_usd ("2.50", "default", "none"). The call that would cross the bucket is refused and the token suspends itself until resumed. Another person's token is not found; a canary token is refused. Safe to retry: the same figure again is `unchanged`. Needs `user` scope. Audit-logged. Returns {tokenId, name, dailyCents, bucketCents, bucket, effect}.

    Annotations the server declares

    • title: Set a token's daily bucket
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • merjax_trigger_workflowDispatch a workflow_dispatch run.No findings

    Why it is in this group

    • The name "merjax_trigger_workflow" says "trigger": a word for a change.
    Description, as the server wrote it
    Dispatch a workflow_dispatch run. Mirrors POST /api/v2/repos/.../actions/workflows/:filename/dispatches. Requires 'repo' scope.

    Annotations the server declares

    • title: Trigger workflow
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_unlabel_issueDetach a label from an issue.No findings

    Why it is in this group

    • The description's first verb is "detach": a word for a change.
    Description, as the server wrote it
    Detach a label from an issue. Idempotent. Requires 'repo' scope. Returns {removed: boolean}.

    Annotations the server declares

    • title: Remove issue label
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
  • merjax_update_prEdit a pull request's title, body, base branch and/or draft state.No findings

    Why it is in this group

    • The name "merjax_update_pr" says "update": a word for a change.
    Description, as the server wrote it
    Edit a pull request's title, body, base branch and/or draft state. Title / body / base: the PR's author or anyone with write access; draft: the same rule as merjax_set_pr_draft (write access and the PR author or repo owner; marking ready starts the AI review). Needs 'repo' scope. Changing the base (open PRs only) re-runs the PR's pull_request CI against the new base and disarms auto-merge. Returns {number, title, body, baseBranch, headBranch, isDraft, changed, autoMergeDisarmed, url}.

    Annotations the server declares

    • title: Update pull request
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
  • merjax_update_pr_branchBring a PR branch up to date with its base: merge the base into the head server-side (the PR page's 'Update branch').No findings

    Why it is in this group

    • The name "merjax_update_pr_branch" says "update": a word for a change.
    Description, as the server wrote it
    Bring a PR branch up to date with its base: merge the base into the head server-side (the PR page's 'Update branch'). Never a force-push — the new head is a merge commit moved through the push gates, so it gets CI. On conflict nothing changes and `conflictFiles` lists the paths. Requires write access and 'repo' scope. Returns {ok, status: 'updated'|'up-to-date', headSha, previousHeadSha, baseSha, url} or {ok: false, reason, message, conflictFiles}.

    Annotations the server declares

    • title: Update PR branch
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_voice_to_prInterpret a free-form voice transcript and either ship it as a spec or create an issue (caller picks via `as`).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Interpret a free-form voice transcript and either ship it as a spec or create an issue (caller picks via `as`). Wraps src/lib/voice-to-pr.ts. Requires 'repo' scope.

    Annotations the server declares

    • title: Voice to PR
    • readOnlyHint: false
    • destructiveHint: false
  • merjax_write_fileCreate or update a file on a branch via git plumbing.No findings

    Why it is in this group

    • The name "merjax_write_file" says "write": a word for a change.
    Description, as the server wrote it
    Create or update a file on a branch via git plumbing. Wraps `createOrUpdateFileOnBranch`. Pass `content` as a UTF-8 string OR `content_base64` for binary. Meets the same branch protection, rulesets and secret scan as a git push, and fires CI/webhooks like one. Requires 'repo' scope.

    Annotations the server declares

    • title: Write file
    • readOnlyHint: false
    • destructiveHint: false
Only reads 46Show 46 read-only tools
  • merjax_ai_cost_summaryReturn AI spend rollups.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    Return AI spend rollups. Scope by one of: user_id (self), repo {owner,repo}, or agent_session_id. Defaults to caller's user spend.

    Annotations the server declares

    • title: AI cost summary
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_ci_queue_statusHow full the shared CI queue is, and what to do about it: level (ok / busy / saturated), runs queued and running, runner slots, estimated minutes before a new run starts, and — wit…Reads private dataNo findings

    Why it is in this group

    • The name "merjax_ci_queue_status" says "status": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "repo": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    How full the shared CI queue is, and what to do about it: level (ok / busy / saturated), runs queued and running, runner slots, estimated minutes before a new run starts, and — with owner+repo — that repository's queued/running runs, its share of CI work, the slots it may hold while others wait (per work class, and across classes), a recommendation (e.g. batch changes into fewer pushes), and `explanation`: each work class's queued/running runs (interactive, review, push, schedule) and, for each of the repository's queued runs, its class and why it waits (code + sentence, from the claim plan itself). The same `ciQueue` block the write tools return. Ask before a burst of pushes. Also `executor`: where CI runs (external runners or in-process), runners configured / reachable / busy, and `holdReason` when no runner can take a run. Read-only.

    Annotations the server declares

    • title: CI queue status
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_clone_urlReturn the authenticated HTTPS clone URL for a repo + a credential-helper hint.Reads private dataReads text others write1 finding

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "repo": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    • untrusted-inputThe name "merjax_clone_url" says "url": it reads web pages, which anyone can write.
    • untrusted-inputThe description's first sentence says "return" and "http": it reads web pages, which anyone can write.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...nticated HTTPS clone URL for a repo + a credential-helper hint. Use this instead of embedd..."

      What this check looks for
    Description, as the server wrote it
    Return the authenticated HTTPS clone URL for a repo + a credential-helper hint. Use this instead of embedding tokens in URLs. Returns {url, owner, repo, defaultBranch, hint} using the repo's stored casing.

    Annotations the server declares

    • title: Get clone URL
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_explain_failureExplain a failed CI run: for each failed step, its class (compile / test / flaky / dependency / env / infra / lint / security / unknown) and the rule that chose it, the normalised …No findings

    Why it is in this group

    • The name "merjax_explain_failure" says "explain": a word for reading.
    Description, as the server wrote it
    Explain a failed CI run: for each failed step, its class (compile / test / flaky / dependency / env / infra / lint / security / unknown) and the rule that chose it, the normalised error signature, failing tests, the files the commit touched, prior occurrences of the same failure (this repo, your other repos with the same owner or org, and platform-wide counts only) with the fix rate, and a suggested fix — the commit / PR that fixed it last time plus its diff limited to the relevant files, or the class's standard remedy. Infra and flaky failures never suggest a code change. `run_id` is the run's full id; with `owner` + `repo` an 8+ hex prefix also works.

    Annotations the server declares

    • title: Explain CI failure
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_explain_repoReturn the cached AI 'explain this codebase' Markdown for a repo.No findings

    Why it is in this group

    • The name "merjax_explain_repo" says "explain": a word for reading.
    Description, as the server wrote it
    Return the cached AI 'explain this codebase' Markdown for a repo. Pure read — never triggers a new generation (use the web UI for that).

    Annotations the server declares

    • title: Explain repository (cached)
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_find_symbolFind definitions of a symbol by name within a repo.Reads private dataNo findings

    Why it is in this group

    • The name "merjax_find_symbol" says "find": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "find" and "repo": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    Find definitions of a symbol by name within a repo. Wraps src/lib/symbols.findDefinitions.

    Annotations the server declares

    • title: Find symbol
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_get_agent_budgetReturn spent / cap / remaining cents for an agent session.No findings

    Why it is in this group

    • The name "merjax_get_agent_budget" says "get": a word for reading.
    Description, as the server wrote it
    Return spent / cap / remaining cents for an agent session.

    Annotations the server declares

    • title: Get agent budget
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_get_branch_protectionRead the branch-protection rule that applies to a branch (exact name or the glob that covers it): required checks, require_pr_run, required approvals, AI / human review, green gate…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "merjax_get_branch_protection" says "get": a word for reading.

    What it can reach

    • private-dataThe name "merjax_get_branch_protection" says "get" and "branch": it reads repositories.
    • private-dataThe description's first sentence says "read" and "branch": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    • untrusted-inputThe description's first sentence says "read" and "review": it reads comments, which other people can write.
    Description, as the server wrote it
    Read the branch-protection rule that applies to a branch (exact name or the glob that covers it): required checks, require_pr_run, required approvals, AI / human review, green gates, force-push / deletion, auto-merge; plus `merge_train` {on, batch_max, effective_batch_max, host_ceiling} — whether the merge train runs for the repository and how many armed PRs it tests together; plus `gate_test` {enabled, server_configured, state: on | disabled_in_settings | not_configured_on_server, details} — whether GateTest scans the repository (set it with merjax_update_repo gate_test_enabled). Read-only. Returns {protected: false, merge_train, gate_test} when no rule applies, else {protected: true, pattern, matched_by, required_checks, …, merge_train, gate_test}.

    Annotations the server declares

    • title: Get branch protection
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_get_commitFetch a single commit by SHA: metadata plus the list of files it changed (path, status, additions, deletions).Reads private dataNo findings

    Why it is in this group

    • The name "merjax_get_commit" says "get": a word for reading.

    What it can reach

    • private-dataThe name "merjax_get_commit" says "get" and "commit": it reads repositories.
    • private-dataThe description's first sentence says "fetch" and "commit": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    Fetch a single commit by SHA: metadata plus the list of files it changed (path, status, additions, deletions). Mirrors GET /api/v2/repos/.../commits/:sha. Patch bodies are NOT included — use merjax_get_diff for those.

    Annotations the server declares

    • title: Get commit
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_get_diffRead the actual changes in a commit or a branch range.Reads private dataNo findings

    Why it is in this group

    • The name "merjax_get_diff" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "commit": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    Read the actual changes in a commit or a branch range. Pass `sha` for one commit against its first parent, or `base`+`head` for everything head adds since the merge base (what a PR proposes). Returns {files:[{path, oldPath?, status, additions, deletions, binary, patch, patchTruncated}], stats, truncated}. Patch text is byte-capped; set include_patch=false for a files-changed summary only.

    Annotations the server declares

    • title: Get diff
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_get_prFetch the full detail record of a pull request (title, body, state, branches, draft, author, timestamps), plus `mergeable` (true / false / null unknown) and `mergeState` from the s…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "merjax_get_pr" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "branch": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    • untrusted-inputThe description's first sentence says "fetch" and "pull request": it reads issues, which other people can write.
    Description, as the server wrote it
    Fetch the full detail record of a pull request (title, body, state, branches, draft, author, timestamps), plus `mergeable` (true / false / null unknown) and `mergeState` from the same conflict probe the merge gate uses: status up-to-date | clean | conflicts | unknown, the unresolved files with their kinds, the files the merge rules settle, and conflictsUrl; and `conflictRisk` (early warning): level none | overlap | conflicts, the files the base changed since the PR branched that the PR changed too, and updateIsClean when updating now would merge cleanly. Authenticated callers only (the read tool surface still works anonymously).

    Annotations the server declares

    • title: Get pull request
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_get_pr_checksList every check at a PR's current head — workflow runs, gates and commit statuses — with status, conclusion, whether branch protection requires it, and the run's log URL; plus eac…Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "merjax_get_pr_checks" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "commit": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...`{withheld, required, hint}` when this credential may not read the run's logs (a private..."

      What this check looks for
    Description, as the server wrote it
    List every check at a PR's current head — workflow runs, gates and commit statuses — with status, conclusion, whether branch protection requires it, and the run's log URL; plus each required check's state (passing / pending / failing / missing) and the merge gate's own CI verdict. A failed workflow run carries `failure`: the failed job and step, up to 8 file:line rows linked to the head sha, the tool's own guidance block ("What now?"), `budget` when a time budget rather than a test stopped the step (run conclusion `timed_out`: still blocks the merge), and the full step log URL — or `{withheld, required, hint}` when this credential may not read the run's logs (a private repository needs 'repo' scope). Read-only. Returns {head_sha, total_count, check_runs, required, ci}.

    Annotations the server declares

    • title: Get PR checks
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_get_preview_urlReturn the branch-preview URL + status for a (repo, branch) pair.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "merjax_get_preview_url" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "branch": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    • untrusted-inputThe name "merjax_get_preview_url" says "get" and "url": it reads web pages, which anyone can write.
    • untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Return the branch-preview URL + status for a (repo, branch) pair. Wraps branch-previews.getPreviewForBranch. Returns {ok:false, reason:'not enabled on this host'} when the host has no PREVIEW_DOMAIN (no preview would ever resolve).

    Annotations the server declares

    • title: Get preview URL
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_get_tokenOne of your tokens by type and id (from merjax_list_tokens): everything list shows plus the audit trail (create, edits with a before/after diff, rotations, revocation).No findings

    Why it is in this group

    • The name "merjax_get_token" says "get": a word for reading.
    Description, as the server wrote it
    One of your tokens by type and id (from merjax_list_tokens): everything list shows plus the audit trail (create, edits with a before/after diff, rotations, revocation). Never the secret. `type` is pat (personal access token, glc_), repo (repository token, gcft_) or deploy (deploy token, gcdt_). Same scopes as merjax_list_tokens.

    Annotations the server declares

    • title: Get token
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_get_variableRead one Actions variable by name.Reads private dataNo findings

    Why it is in this group

    • The name "merjax_get_variable" says "get": a word for reading.

    What it can reach

    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    Read one Actions variable by name. Pass owner + repo for a repository variable, owner + repo + environment for an environment variable, or org for an organisation variable (organisation variables need an admin-scoped token). Not found is an error. Returns {name, value, createdAt, updatedAt}.

    Annotations the server declares

    • title: Get an Actions variable
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • merjax_get_workflow_logsReturn a workflow run's logs plus a failure summary.Reads private data1 finding

    Why it is in this group

    • The name "merjax_get_workflow_logs" says "get": a word for reading.

    What it can reach

    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...ad is audited. For a read-only CI audit credential, a repository token with {"runners": "r..."

      What this check looks for
    Description, as the server wrote it
    Return a workflow run's logs plus a failure summary. Always includes run metadata (number, workflow, event, ref, sha), per-job and per-step status / exit code / duration, `failedSteps` (`job / step`) and `testFailures` (failing test names, read from each step's structured results parsed before its log was cut, or the reason they cannot all be named; null when no job failed). `testFailures.details` marks each failure `flaky` (an active forensic label with a repro, from another run — with its label and flip rate), `known` (also failing on the default branch's latest run), `infra` (timed out under load) or `new`, with its file, message, the targeted retry's verdict and this run's determinism-forensics finding (`forensic`: class, label, variable, repro) when they ran. A step whose log was cut carries `fullLog` (artifact download of the uncut output). `step` (a step name or 1-based position within its job) returns only that step's stdout/stderr; `tail_lines` keeps the last N lines. The full per-job logs are included only when neither is given. JSON-friendly companion to the ZIP-download endpoint. A private repository's logs require 'repo' scope (OAuth: write:repo); every token read is audited. For a read-only CI audit credential, a repository token with {"runners": "read", "actions": "read"} (the ci-audit preset, merjax_create_repo_token) reads the same masked logs over REST — GET /api/v2/repos/:owner/:repo/actions/runs/:id/logs, or one job's at actions/jobs/:job_id/logs — under the same rule and audit; repository tokens are not accepted on /mcp.

    Annotations the server declares

    • title: Get workflow logs
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_get_workflow_runFetch a workflow run's metadata + status.Reads private dataNo findings

    Why it is in this group

    • The name "merjax_get_workflow_run" says "get": a word for reading.

    What it can reach

    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    Fetch a workflow run's metadata + status. Mirrors GET /api/v2/repos/.../actions/runs/:id. Also says how it relates to automatic retries: `retryOf` / `retryOfRunNumber` (the run this one retries after a deploy or a lost runner) and `retriedAs` ({id, runNumber} of the run that retried this one, or null). A queued run that no runner can take carries `queueReason` (e.g. "waiting for a runner: 2 configured, 0 reachable, last seen 4m ago"). `workClass` (interactive / review / push / schedule — how the CI claim shares slots); a queued run carries `queue` ({code, text}: its place in the claim order, from the claim plan itself); a schedule run carries `coalescedFires` / `lastCoalescedAt`, and `coalescedNote` when later scheduled fires folded into it while it was queued.

    Annotations the server declares

    • title: Get workflow run
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_learning_statusSite admins only (needs an 'admin'-scoped token).No findings

    Why it is in this group

    • The name "merjax_learning_status" says "status": a word for reading.
    Description, as the server wrote it
    Site admins only (needs an 'admin'-scoped token). Whether CI failures are being turned into lessons: classified failures, lesson.pattern events (matched to a docs/ops/CI_GATE_LESSONS.md row, or candidates), recurring candidates, and failures left without a lesson for over an hour, over 7 days. 'N failures, 0 lessons' reads RED. Also each pattern's count and register row, and the register. Counts only: no log text or repository. Returns {health, patterns, register}.

    Annotations the server declares

    • title: Learning status (admin)
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_list_ai_workspacesThe three provider workspaces every model call is billed to by its purpose (ws-control-plane, ws-hosted-loops, ws-ci-gates): each with its daily spend limit, rate limit, today's sp…No findings

    Why it is in this group

    • The name "merjax_list_ai_workspaces" says "list": a word for reading.
    Description, as the server wrote it
    The three provider workspaces every model call is billed to by its purpose (ws-control-plane, ws-hosted-loops, ws-ci-gates): each with its daily spend limit, rate limit, today's spend and calls (UTC day), and the platform ceiling above all three. Site admins with an admin-scoped token only. Mirrors GET /api/v2/admin/ai-workspaces. Returns {day, platformDailyCents, workspaces:[{workspace, purpose, dailyCents, rpm, spentToday, callsToday, callsLastMinute, updatedAt, updatedBy}]}.

    Annotations the server declares

    • title: List AI workspaces
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • merjax_list_deleted_reposList deleted repositories you can restore or purge: your personal ones and those of organizations you own (a site admin may pass all: true for the whole instance).Reads private dataNo findings

    Why it is in this group

    • The name "merjax_list_deleted_repos" says "list": a word for reading.

    What it can reach

    • private-dataThe name "merjax_list_deleted_repos" says "list" and "repo": it reads repositories.
    • private-dataThe description's first sentence says "list" and "repository": it reads repositories.
    Description, as the server wrote it
    List deleted repositories you can restore or purge: your personal ones and those of organizations you own (a site admin may pass all: true for the whole instance). Each has its id, full_name and restorable_until — after that date it is purged automatically. Read-only. Needs 'repo' scope. Returns {total_count, repositories:[{id, full_name, private, deleted_at, deleted_by, restorable_until}]}.

    Annotations the server declares

    • title: List deleted repositories
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_list_flaky_testsList a repository's flaky tests.Reads private dataNo findings

    Why it is in this group

    • The name "merjax_list_flaky_tests" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "repository": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    List a repository's flaky tests. A test is flaky only with a forensic repro: when it failed, CI re-ran just that test in the same order, alone, with the clock shifted +137 ms and +1 s, in TZ=Pacific/Chatham and in a fixed random order, and a variable flipped its verdict N times in a row on the same git tree. Each entry has the test, file, state (active / expired / resolved, or unexplained = flipped with no repro, NOT flaky), label (clock-dependent, order-dependent, concurrency-dependent), the variable, the exact repro command, owner, expiry, issue number, flip rate and evidence runs. Information only — flaky tests are never skipped or quarantined; one targeted retry, and the merge gate excuses a failure only when that retry passed in the same run and the label is active.

    Annotations the server declares

    • title: List flaky tests
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_list_loop_secretsList the secrets a hosted Claude loop (or an organisation) holds — names and dates, never values.Reads private dataNo findings

    Why it is in this group

    • The name "merjax_list_loop_secrets" says "list": a word for reading.

    What it can reach

    • private-dataThe name "merjax_list_loop_secrets" says "list" and "secret": it reads secrets.
    • private-dataThe description's first sentence says "list" and "secret": it reads secrets.
    Description, as the server wrote it
    List the secrets a hosted Claude loop (or an organisation) holds — names and dates, never values. Pass loop (the hosted Claude loop's id, from /connect/claude/deploy) for the loop's own secret — its owner only — or org (organisation slug, admin-scoped token) for an organisation-level secret every loop of the organisation inherits; a loop-level name overrides the organisation's. ANTHROPIC_API_KEY is the loop's model key (CAP-S.8: the platform never lends its own); at organisation level it is the BYOK override. Returns {scope, secrets:[{name, scope, createdAt, updatedAt, lastUsedAt}], inherited:[…]} where inherited are the organisation-level names a loop gets unless it overrides them.

    Annotations the server declares

    • title: List hosted-loop secrets
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • merjax_list_pr_commentsList every comment on a pull request in chronological order: general comments (kind `issue_comment`), inline review comments (`review_comment`: path, line, thread {id, inReplyToId,…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "merjax_list_pr_comments" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "thread": it reads messages.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    • untrusted-inputThe name "merjax_list_pr_comments" says "list" and "comment": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "list" and "comment": it reads comments, which other people can write.
    Description, as the server wrote it
    List every comment on a pull request in chronological order: general comments (kind `issue_comment`), inline review comments (`review_comment`: path, line, thread {id, inReplyToId, position, replies, resolved, resolvedAt, resolvedBy}) and review summaries (`review`: state approved | changes_requested | commented). Each entry has author {login, type user|bot}, isAi (written by a model: false for gluecron[bot]'s own notes, e.g. a person's conflict resolution or a merge-train notice), onBehalfOf (on such a note, the person it was posted for), body, createdAt, updatedAt. A review thread is the inline comments on one file+line; the earliest is its root and holds the resolved state. Merjax does not store a review comment's commit or diff side, so `commitId` and `side` are always null. Only approved (moderated) comments; unsubmitted draft reviews are private to their author and not listed. `kind`: all (default) | issue | review (review comments + review summaries). `since`: ISO-8601 — only entries updated at or after it. Paged: `total` is the full filtered count, `nextOffset` pages through it. Works anonymously on public repos; private repos need read access.

    Annotations the server declares

    • title: List PR comments
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_list_pr_conflictsWhat stands between a PR and a clean merge, as the merge gate, the PR page and the Conflicts tab see it (one shared probe): status up-to-date | clean | conflicts | unknown, `mergea…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "merjax_list_pr_conflicts" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    • untrusted-inputThe description's first sentence says "browser": it reads web pages, which anyone can write.
    Description, as the server wrote it
    What stands between a PR and a clean merge, as the merge gate, the PR page and the Conflicts tab see it (one shared probe): status up-to-date | clean | conflicts | unknown, `mergeable`, the base/head shas the answer is for, files settled with no one in the loop (ruleSettled: each with `by` = structured (structured, code-aware merge) or rules (the deterministic merge rules)), and each unresolved file with its kind in plain words (both edited / binary / deleted on one side / added on both / rename / submodule / too large), whether the browser can edit it or only keep one side, and any saved draft. With hunks: true, each editable file's diff3 text labelled by branch name and its hunks (id, mine, base, main) for merjax_resolve_pr_conflict. Also the exact git commands for the command line. Read-only.

    Annotations the server declares

    • title: List PR conflicts
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_list_prsList pull requests on a repo, filtered by state (open|closed|merged|all).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "merjax_list_prs" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "repo": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    • untrusted-inputThe description's first sentence says "list" and "pull request": it reads issues, which other people can write.
    Description, as the server wrote it
    List pull requests on a repo, filtered by state (open|closed|merged|all). Authenticated callers only. Returns up to 50 summary rows.

    Annotations the server declares

    • title: List pull requests
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_list_ready_to_mergePull requests that are green and clean and that nobody has merged: open, not a draft, CI green at the head, no gate failing or running, no standing request for changes, branch prot…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "merjax_list_ready_to_merge" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "branch": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    • untrusted-inputThe description's first sentence says "pull request": it reads issues, which other people can write.
    Description, as the server wrote it
    Pull requests that are green and clean and that nobody has merged: open, not a draft, CI green at the head, no gate failing or running, no standing request for changes, branch protection satisfied, no conflicts (the merge gate's own conflict probe), and auto-merge NOT armed. Each comes with a plain sentence ("Green and clean for 3 days — nobody has merged it"), whether you can merge it (canMerge) or arm it (canArm), and the merge / arm endpoints. Also `waiting_on_you`: open PRs where you are a requested reviewer or code owner and have not reviewed. Scope: owner + repo for one repository; org for an organisation; neither for every repository you can merge in. `not_ready` lists the other open PRs in scope with the first reason. To act: merjax_set_auto_merge (arm) or merjax_merge_pr. Read-only.

    Annotations the server declares

    • title: List PRs ready to merge
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_list_repo_secretsList a repository's workflow secrets — NAMES ONLY, with created/updated times; values are never returned.Reads private dataNo findings

    Why it is in this group

    • The name "merjax_list_repo_secrets" says "list": a word for reading.

    What it can reach

    • private-dataThe name "merjax_list_repo_secrets" says "list" and "repo": it reads repositories.
    • private-dataThe description's first sentence says "list" and "repository": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    List a repository's workflow secrets — NAMES ONLY, with created/updated times; values are never returned. Use it to check that a secret such as CRON_SECRET exists before a workflow needs it. Needs admin access to the repository and 'repo' scope. Returns {repository, total_count, secrets:[{name, created_at, updated_at}]}.

    Annotations the server declares

    • title: List repository secrets
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_list_repo_tokensList the fine-grained repository tokens you have minted (never the secret): repository, permissions, state (active / expired / revoked), expiry and last use.Reads private dataNo findings

    Why it is in this group

    • The name "merjax_list_repo_tokens" says "list": a word for reading.

    What it can reach

    • private-dataThe name "merjax_list_repo_tokens" says "list" and "repo": it reads repositories.
    • private-dataThe description's first sentence says "list" and "repository": it reads repositories.
    Description, as the server wrote it
    List the fine-grained repository tokens you have minted (never the secret): repository, permissions, state (active / expired / revoked), expiry and last use. Needs 'repo' scope.

    Annotations the server declares

    • title: List repository tokens
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_list_runnersList the CI runners registered to an owner (username, org slug, or 'platform'): id, name, url, labels, slots, online, last seen, revoked; allowSharedOverflow (the setting); and sha…Reads text others write1 finding

    Why it is in this group

    • The name "merjax_list_runners" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...ge the owner's runners. For a read-only credential — a security audit watching for rogue r..."

      What this check looks for
    Description, as the server wrote it
    List the CI runners registered to an owner (username, org slug, or 'platform'): id, name, url, labels, slots, online, last seen, revoked; allowSharedOverflow (the setting); and sharedLane, whether the owner's jobs actually run on shared runners: 'used (no own runners)', 'overflow allowed' or 'not used (own runners only)', explained in sharedLaneDetail. Needs a PAT with 'repo' scope (or a session) and the right to manage the owner's runners. For a read-only credential — a security audit watching for rogue runners — mint a repository token with {"runners": "read"} (merjax_create_repo_token) and call GET /api/v2/repos/:owner/:repo/actions/runners: it lists the same runners and lane and can do nothing else (repository tokens are not accepted on /mcp). Add {"actions": "read"} (the ci-audit preset) and the same token also lists workflows, runs and jobs and reads their masked logs, still with no write anywhere.

    Annotations the server declares

    • title: List CI runners
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_list_token_spendToday's model spend (UTC day), the daily bucket in force and the state (active | suspended) of every personal access token of yours, as /settings/tokens/spend shows it.No findings

    Why it is in this group

    • The name "merjax_list_token_spend" says "list": a word for reading.
    Description, as the server wrote it
    Today's model spend (UTC day), the daily bucket in force and the state (active | suspended) of every personal access token of yours, as /settings/tokens/spend shows it. Canary tokens are not listed: they never authenticate. Needs `user` scope. Returns {platformDefaultCents, tokens:[{tokenId, name, tokenPrefix, spentTodayCents, bucketCents (0 = no bucket), bucketSource: own|default, state, suspendedAt, suspendedReason, suspendedSpentCents}]}.

    Annotations the server declares

    • title: Your tokens' spend today
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • merjax_list_tokensList your own tokens (never a secret): type, name, status (active / expiring / expired / revoked / never_used / stale), last 4 characters, scopes or permissions, repository, expiry…Reads private dataNo findings

    Why it is in this group

    • The name "merjax_list_tokens" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "secret": it reads secrets.
    Description, as the server wrote it
    List your own tokens (never a secret): type, name, status (active / expiring / expired / revoked / never_used / stale), last 4 characters, scopes or permissions, repository, expiry, last use (time, IP, client), use count and rotation state. `type` is pat (personal access token, glc_), repo (repository token, gcft_) or deploy (deploy token, gcdt_), or omit it for all three (types your token's scopes cannot read are listed under `omitted`). PATs need 'user' scope to read; repository and deploy tokens need 'repo'.

    Annotations the server declares

    • title: List tokens
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_list_treeList directory contents at a ref.Reads private dataNo findings

    Why it is in this group

    • The name "merjax_list_tree" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "directory": it reads files.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    List directory contents at a ref. `path` scopes the listing to a subtree and is honoured in BOTH modes; `recursive: true` walks the whole subtree instead of one level. Always returns the same shape: {path, ref, recursive, entries, truncated, totalCount}. Recursive entries carry full repo-relative paths; non-recursive entries carry names. A ref that does not exist is an error, never an empty listing.

    Annotations the server declares

    • title: List tree
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_list_variablesList Actions configuration variables (${{ vars.NAME }}) with their values.Reads private dataNo findings

    Why it is in this group

    • The name "merjax_list_variables" says "list": a word for reading.

    What it can reach

    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    List Actions configuration variables (${{ vars.NAME }}) with their values. Pass owner + repo for a repository variable, owner + repo + environment for an environment variable, or org for an organisation variable (organisation variables need an admin-scoped token). Admin of the repository or organisation only. Paged: limit (≤100, default 30) / offset. Mirrors GET …/actions/variables. Returns {scope, total, limit, offset, nextOffset, variables:[{name, value, createdAt, updatedAt}]}.

    Annotations the server declares

    • title: List Actions variables
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • merjax_list_workflow_runsList a repository's workflow runs, newest first, with optional branch/status/event filters.Reads private data1 finding

    Why it is in this group

    • The name "merjax_list_workflow_runs" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "repository": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...he repository. For a read-only CI audit credential (no code, no secrets, no writes), mint..."

      What this check looks for
    Description, as the server wrote it
    List a repository's workflow runs, newest first, with optional branch/status/event filters. Mirrors GET /api/v2/repos/.../actions/runs. The companion to merjax_get_workflow_run / merjax_cancel_workflow_run — this is how an agent finds the run ids to inspect or cancel (issue #10493: without it, stale queued runs could not be discovered from the tool surface at all). Needs read access to the repository. For a read-only CI audit credential (no code, no secrets, no writes), mint a repository token with {"runners": "read", "actions": "read"} (the ci-audit preset, merjax_create_repo_token) and call GET /api/v2/repos/:owner/:repo/actions/runs (and actions/workflows, actions/runs/:id/jobs): repository tokens are not accepted on /mcp.

    Annotations the server declares

    • title: List workflow runs
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_pr_status_summaryCompute a one-shot status summary for a PR: state, risk score (and whether it describes the current head), CI state for the head commit as the merge gate sees it (with `ci.failures…Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "merjax_pr_status_summary" says "status": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "commit": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...`{withheld, required, hint}` when this credential may not read the run's logs), AI-review..."

      What this check looks for
    Description, as the server wrote it
    Compute a one-shot status summary for a PR: state, risk score (and whether it describes the current head), CI state for the head commit as the merge gate sees it (with `ci.failures`: for each failed run, the failed step, up to 8 file:line rows linked to the head sha, the tool's own guidance block and the full step log URL, or `{withheld, required, hint}` when this credential may not read the run's logs), AI-review verdicts (trio), gate signals, `merge` — the conflict probe the merge gate uses (status up-to-date | clean | conflicts | unknown, unresolved files with kinds, files settled by structured merge or the merge rules, conflictsUrl), `conflictRisk` — the early warning (files the base changed since the PR branched that the PR changed too; updateIsClean when updating now would merge cleanly), auto-merge (armed? `last_attempt.reason` says what it waits for or what happens next), and `mergeTrain.lastDequeue` — the merge train's newest receipt for a green merge preview it did not merge (which commit, which runs, why). Read-only.

    Annotations the server declares

    • title: PR status summary
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_read_fileRead a file from a repo at a given ref.Reads private dataNo findings

    Why it is in this group

    • The name "merjax_read_file" says "read": a word for reading.

    What it can reach

    • private-dataThe name "merjax_read_file" says "read" and "file": it reads files.
    • private-dataThe description's first sentence says "read" and "file": it reads files.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    Read a file from a repo at a given ref. Mirrors GET /api/v2/repos/:owner/:repo/contents/:path. Returns {path, size, content, encoding, totalLines}. Pass `start_line` / `end_line` (1-based, inclusive) to read only part of a text file. A text file over ~60 KB read with no range returns its first ~60 KB of whole lines with `truncated: true`, `startLine`/`endLine` and a hint — ask for the next range to read on.

    Annotations the server declares

    • title: Read file
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_repo_explain_codebaseReturn the cached AI 'explain this codebase' Markdown for a public repo (most recent commit).No findings

    Why it is in this group

    • The name "merjax_repo_explain_codebase" says "explain": a word for reading.
    Description, as the server wrote it
    Return the cached AI 'explain this codebase' Markdown for a public repo (most recent commit). Returns null when no cached explanation exists yet.

    Annotations the server declares

    • title: Explain codebase (cached)
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_repo_list_issuesList open issues for a public repository.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "merjax_repo_list_issues" says "list": a word for reading.

    What it can reach

    • private-dataThe name "merjax_repo_list_issues" says "list" and "repo": it reads repositories.
    • private-dataThe description's first sentence says "list" and "repository": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    • untrusted-inputThe name "merjax_repo_list_issues" says "list" and "issue": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "list" and "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    List open issues for a public repository. Returns up to 50 ordered by most-recent.

    Annotations the server declares

    • title: List open issues
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_repo_read_fileRead a single file from a repository at a given ref (branch / tag / commit).Reads private dataNo findings

    Why it is in this group

    • The name "merjax_repo_read_file" says "read": a word for reading.

    What it can reach

    • private-dataThe name "merjax_repo_read_file" says "read" and "repo": it reads repositories.
    • private-dataThe description's first sentence says "read" and "file": it reads files.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    Read a single file from a repository at a given ref (branch / tag / commit). Private repos are readable when the authenticated caller has access. Returns the text content (binary files rejected).

    Annotations the server declares

    • title: Read repository file
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_search_codeLiteral / regex code search (git grep, basic regex) across a repo at a ref.Reads private dataNo findings

    Why it is in this group

    • The name "merjax_search_code" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "repo": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    Literal / regex code search (git grep, basic regex) across a repo at a ref. The dependable way to find code on this host — works on every repo, indexed or not. Optional scoping: `path` (a directory or file prefix, literal), `glob` (git pathspec glob such as `src/**/*.ts`, relative to `path` when both are given), `ignore_case`, and `files_only` (unique files with match counts instead of lines). Returns {owner, repo, ref, total, truncated, matches: [{file, line, text}]}, or with files_only {owner, repo, ref, total, totalMatches, truncated, files: [{file, count}]}. Omit `ref` for the default branch.

    Annotations the server declares

    • title: Search code (grep)
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_search_issuesSearch issues by title/body keyword on a single repo, filtered by state.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "merjax_search_issues" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "repo": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    • untrusted-inputThe name "merjax_search_issues" says "search" and "issue": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "search" and "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    Search issues by title/body keyword on a single repo, filtered by state. Returns ranked rows.

    Annotations the server declares

    • title: Search issues
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_search_prsSearch pull requests by title/body keyword on a repo.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "merjax_search_prs" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "repo": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    • untrusted-inputThe description's first sentence says "search" and "pull request": it reads issues, which other people can write.
    Description, as the server wrote it
    Search pull requests by title/body keyword on a repo.

    Annotations the server declares

    • title: Search pull requests
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_search_reposSearch repositories by owner, name, owner/name or description, case-insensitively: every public repo, plus the private ones you own or collaborate on when authenticated.Reads private dataNo findings

    Why it is in this group

    • The name "merjax_search_repos" says "search": a word for reading.

    What it can reach

    • private-dataThe name "merjax_search_repos" says "search" and "repo": it reads repositories.
    • private-dataThe description's first sentence says "search" and "repository": it reads repositories.
    Description, as the server wrote it
    Search repositories by owner, name, owner/name or description, case-insensitively: every public repo, plus the private ones you own or collaborate on when authenticated. Omit `query` (authenticated) to list YOUR repositories — the ones you own or were invited to — instead of searching. Mirrors GET /api/v2/search/repos. `total` is the full match count (not the page size) and `nextOffset` pages through it.

    Annotations the server declares

    • title: Search repositories (ranked)
    • readOnlyHint: true
    • destructiveHint: false
  • merjax_whoamiWho this connector is on this Merjax instance: the signed-in username and email, whether that account is a site admin, the token's scopes, and how many repositories it owns or coll…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "merjax_whoami" says "whoami": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Who this connector is on this Merjax instance: the signed-in username and email, whether that account is a site admin, the token's scopes, and how many repositories it owns or collaborates on. Call it first when a repository seems missing — the answer is usually which account authorized the connector. Anonymous callers get authenticated:false and a hint.

    Annotations the server declares

    • title: Who am I
    • readOnlyHint: true
    • destructiveHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

5130 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 9 outbound tools breaks every one.

Can send data out9
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__gluecron__merjax_assign_issue",
      "mcp__gluecron__merjax_chat_continue",
      "mcp__gluecron__merjax_close_issue",
      "mcp__gluecron__merjax_comment_issue",
      "mcp__gluecron__merjax_create_issue",
      "mcp__gluecron__merjax_edit_comment",
      "mcp__gluecron__merjax_generate_commit_message",
      "mcp__gluecron__merjax_label_issue",
      "mcp__gluecron__merjax_reopen_issue"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 20, 2026, 18:39 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://gluecron.com/.well-known/oauth-protected-resource
RFC 9728 protected resource metadata
https://gluecron.com/.well-known/oauth-protected-resource
Authorization servers
https://gluecron.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no

Posture changes

  1. Nov 20, 2026
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 85 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://gluecron.com/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: https://gluecron.com/.well-known/oauth-protected-resource/mcp to https://gluecron.com/.well-known/oauth-protected-resource
  2. Nov 6, 2026
    • Tools that change things, listed without credentials: 74 to 85
  3. Oct 29, 2026
    • Tools that change things, listed without credentials: 67 to 74

Findings

Matches of fixed checks, with the text they matched.

7 warn13 info
  • The server marks "merjax_undo_kill_switch" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "merjax_undo_kill_switch" says "kill": a word for removing or ending something.

    What this check looks for
  • The server marks "merjax_backup_status" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false}; The name "merjax_backup_status" says "status": a word for reading.

    What this check looks for
  • The server marks "merjax_generate_pr_description" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false}; The name "merjax_generate_pr_description" says "generate": a word for a change.

    What this check looks for
  • The server marks "merjax_ship_spec" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false}; The description's first verb is "drop": a word for removing or ending something.

    What this check looks for
  • The server marks "merjax_generate_commit_message" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false}; The name "merjax_generate_commit_message" says "generate": a word for a change.

    What this check looks for
  • The server marks "merjax_generate_release_notes" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false}; The name "merjax_generate_release_notes" says "generate": a word for a change.

    What this check looks for
Show 14 more findings

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 85 -> 0 (and 4 more).View diff
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 85 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://gluecron.com/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: https://gluecron.com/.well-known/oauth-protected-resource/mcp to https://gluecron.com/.well-known/oauth-protected-resource
  2. Tools131 added, 117 removed.+131 added−117 removedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 74 -> 85.View diff
    • Tools that change things, listed without credentials: 74 to 85
  4. Tools9 added, 11 changed.+9 added~11 changedView diff
    • Added:gluecron_ci_healthChanges things
    • Added:gluecron_commit_pr_conflict_resolutionChanges things
    • Added:gluecron_delete_branchDeletes or cancels
    • Added:gluecron_delete_commentDeletes or cancels
    • Added:gluecron_edit_commentDeletes or cancels
    • Added:gluecron_list_pr_conflictsOnly reads
    • Added:gluecron_list_ready_to_mergeOnly reads
    • Added:gluecron_resolve_pr_conflictChanges things
    • Added:gluecron_security_ioc_hitsChanges things
    • Changed:gluecron_create_repo_tokenChanges thingsinputSchema
    • Changed:gluecron_create_runner_registration_tokenChanges thingsdescriptioninputSchema
    • Changed:gluecron_get_branch_protectionOnly readsdescription
    • Changed:gluecron_get_prOnly readsdescription
    • Changed:gluecron_get_pr_checksOnly readsdescription
    • Changed:gluecron_get_workflow_logsOnly readsdescription
    • Changed:gluecron_handoverChanges thingsdescription
    • Changed:gluecron_list_pr_commentsOnly readsdescription
    • Changed:gluecron_list_runnersOnly readsdescription
    • Changed:gluecron_pr_status_summaryOnly readsdescription
    • Changed:gluecron_set_auto_mergeChanges thingsdescription
  5. PostureRemote posture changed. Tools that change things, listed without credentials: 67 -> 74.View diff
    • Tools that change things, listed without credentials: 67 to 74

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http gluecron https://gluecron.com/mcp
claude mcp add --transport http gluecron https://gluecron.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__gluecron__merjax_repo_search",
      "mcp__gluecron__merjax_repo_read_file",
      "mcp__gluecron__merjax_repo_list_issues",
      "mcp__gluecron__merjax_repo_explain_codebase",
      "mcp__gluecron__merjax_get_pr",
      "mcp__gluecron__merjax_list_prs",
      "mcp__gluecron__merjax_search_repos",
      "mcp__gluecron__merjax_whoami",
      "mcp__gluecron__merjax_clone_url",
      "mcp__gluecron__merjax_list_repo_tokens",
      "mcp__gluecron__merjax_list_tokens",
      "mcp__gluecron__merjax_get_token",
      "mcp__gluecron__merjax_list_repo_secrets",
      "mcp__gluecron__merjax_list_deleted_repos",
      "mcp__gluecron__merjax_list_variables",
      "mcp__gluecron__merjax_get_variable",
      "mcp__gluecron__merjax_list_token_spend",
      "mcp__gluecron__merjax_list_loop_secrets",
      "mcp__gluecron__merjax_list_ai_workspaces",
      "mcp__gluecron__merjax_learning_status",
      "mcp__gluecron__merjax_search_issues",
      "mcp__gluecron__merjax_search_prs",
      "mcp__gluecron__merjax_list_pr_comments",
      "mcp__gluecron__merjax_list_pr_conflicts",
      "mcp__gluecron__merjax_list_ready_to_merge",
      "mcp__gluecron__merjax_get_pr_checks",
      "mcp__gluecron__merjax_get_branch_protection",
      "mcp__gluecron__merjax_read_file",
      "mcp__gluecron__merjax_list_tree",
      "mcp__gluecron__merjax_get_commit",
      "mcp__gluecron__merjax_get_diff",
      "mcp__gluecron__merjax_explain_repo",
      "mcp__gluecron__merjax_get_workflow_run",
      "mcp__gluecron__merjax_list_workflow_runs",
      "mcp__gluecron__merjax_get_workflow_logs",
      "mcp__gluecron__merjax_explain_failure",
      "mcp__gluecron__merjax_list_flaky_tests",
      "mcp__gluecron__merjax_list_runners",
      "mcp__gluecron__merjax_get_preview_url",
      "mcp__gluecron__merjax_get_agent_budget",
      "mcp__gluecron__merjax_semantic_search",
      "mcp__gluecron__merjax_search_code",
      "mcp__gluecron__merjax_find_symbol",
      "mcp__gluecron__merjax_pr_status_summary",
      "mcp__gluecron__merjax_ci_queue_status",
      "mcp__gluecron__merjax_ai_cost_summary"
    ],
    "ask": [
      "mcp__gluecron__merjax_repo_health",
      "mcp__gluecron__merjax_create_issue",
      "mcp__gluecron__merjax_comment_issue",
      "mcp__gluecron__merjax_reopen_issue",
      "mcp__gluecron__merjax_create_pr",
      "mcp__gluecron__merjax_comment_pr",
      "mcp__gluecron__merjax_fork_repo",
      "mcp__gluecron__merjax_create_deploy_token",
      "mcp__gluecron__merjax_create_repo_token",
      "mcp__gluecron__merjax_set_repo_secret",
      "mcp__gluecron__merjax_restore_repo",
      "mcp__gluecron__merjax_set_token_bucket",
      "mcp__gluecron__merjax_resume_token",
      "mcp__gluecron__merjax_set_ai_workspace_quota",
      "mcp__gluecron__merjax_set_pr_ai_settings",
      "mcp__gluecron__merjax_import_action",
      "mcp__gluecron__merjax_backup_status",
      "mcp__gluecron__merjax_security_ioc_hits",
      "mcp__gluecron__merjax_label_issue",
      "mcp__gluecron__merjax_unlabel_issue",
      "mcp__gluecron__merjax_assign_issue",
      "mcp__gluecron__merjax_request_changes",
      "mcp__gluecron__merjax_dismiss_review",
      "mcp__gluecron__merjax_open_draft_pr",
      "mcp__gluecron__merjax_set_pr_draft",
      "mcp__gluecron__merjax_generate_pr_description",
      "mcp__gluecron__merjax_update_pr_branch",
      "mcp__gluecron__merjax_resolve_pr_conflict",
      "mcp__gluecron__merjax_commit_pr_conflict_resolution",
      "mcp__gluecron__merjax_repo_rating",
      "mcp__gluecron__merjax_propose_pr_conflict_resolution",
      "mcp__gluecron__merjax_update_pr",
      "mcp__gluecron__merjax_set_auto_merge",
      "mcp__gluecron__merjax_rerun_failed_jobs",
      "mcp__gluecron__merjax_set_branch_protection",
      "mcp__gluecron__merjax_approve_pr",
      "mcp__gluecron__merjax_write_file",
      "mcp__gluecron__merjax_create_branch",
      "mcp__gluecron__merjax_atomic_multi_file_commit",
      "mcp__gluecron__merjax_apply_patch",
      "mcp__gluecron__merjax_voice_to_pr",
      "mcp__gluecron__merjax_refactor_across_repos",
      "mcp__gluecron__merjax_chat_with_repo",
      "mcp__gluecron__merjax_chat_continue",
      "mcp__gluecron__merjax_generate_tests",
      "mcp__gluecron__merjax_generate_commit_message",
      "mcp__gluecron__merjax_generate_release_notes",
      "mcp__gluecron__merjax_propose_migration",
      "mcp__gluecron__merjax_propose_doc_update",
      "mcp__gluecron__merjax_trigger_workflow",
      "mcp__gluecron__merjax_prioritize_workflow_run",
      "mcp__gluecron__merjax_review_deployment",
      "mcp__gluecron__merjax_create_runner_registration_token",
      "mcp__gluecron__merjax_ci_executor",
      "mcp__gluecron__merjax_ci_health",
      "mcp__gluecron__merjax_provision_pr_sandbox",
      "mcp__gluecron__merjax_create_agent_session",
      "mcp__gluecron__merjax_acquire_lease",
      "mcp__gluecron__merjax_release_lease",
      "mcp__gluecron__merjax_handover",
      "mcp__gluecron__merjax_security_scan"
    ],
    "deny": [
      "mcp__gluecron__merjax_close_issue",
      "mcp__gluecron__merjax_merge_pr",
      "mcp__gluecron__merjax_close_pr",
      "mcp__gluecron__merjax_delete_repo",
      "mcp__gluecron__merjax_update_repo",
      "mcp__gluecron__merjax_revoke_repo_token",
      "mcp__gluecron__merjax_rotate_token",
      "mcp__gluecron__merjax_revoke_token",
      "mcp__gluecron__merjax_delete_repo_secret",
      "mcp__gluecron__merjax_purge_repo",
      "mcp__gluecron__merjax_set_variable",
      "mcp__gluecron__merjax_delete_variable",
      "mcp__gluecron__merjax_delete_branch",
      "mcp__gluecron__merjax_edit_comment",
      "mcp__gluecron__merjax_delete_comment",
      "mcp__gluecron__merjax_set_loop_secret",
      "mcp__gluecron__merjax_delete_loop_secret",
      "mcp__gluecron__merjax_press_kill_switch",
      "mcp__gluecron__merjax_undo_kill_switch",
      "mcp__gluecron__merjax_revoke_all_credentials",
      "mcp__gluecron__merjax_delete_file",
      "mcp__gluecron__merjax_ship_spec",
      "mcp__gluecron__merjax_cancel_workflow_run",
      "mcp__gluecron__merjax_revoke_runner"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as gluecron. Review it before you use it.

Capability tags behind 48 rules
  • mcp__gluecron__merjax_repo_search private-data
  • mcp__gluecron__merjax_repo_read_file private-data
  • mcp__gluecron__merjax_repo_list_issues private-data, untrusted-input
  • mcp__gluecron__merjax_create_issue outbound
  • mcp__gluecron__merjax_comment_issue outbound
  • mcp__gluecron__merjax_close_issue outbound
  • mcp__gluecron__merjax_reopen_issue outbound
  • mcp__gluecron__merjax_get_pr private-data, untrusted-input
  • mcp__gluecron__merjax_list_prs private-data, untrusted-input
  • mcp__gluecron__merjax_search_repos private-data
  • mcp__gluecron__merjax_whoami private-data, untrusted-input
  • mcp__gluecron__merjax_clone_url private-data, untrusted-input
  • mcp__gluecron__merjax_list_repo_tokens private-data
  • mcp__gluecron__merjax_list_tokens private-data
  • mcp__gluecron__merjax_list_repo_secrets private-data
  • mcp__gluecron__merjax_list_deleted_repos private-data
  • mcp__gluecron__merjax_list_variables private-data
  • mcp__gluecron__merjax_get_variable private-data
  • mcp__gluecron__merjax_edit_comment outbound
  • mcp__gluecron__merjax_list_loop_secrets private-data
  • mcp__gluecron__merjax_label_issue outbound
  • mcp__gluecron__merjax_assign_issue outbound
  • mcp__gluecron__merjax_search_issues private-data, untrusted-input
  • mcp__gluecron__merjax_search_prs private-data, untrusted-input
  • mcp__gluecron__merjax_list_pr_comments private-data, untrusted-input
  • mcp__gluecron__merjax_list_pr_conflicts private-data, untrusted-input
  • mcp__gluecron__merjax_resolve_pr_conflict private-data
  • mcp__gluecron__merjax_list_ready_to_merge private-data, untrusted-input
  • mcp__gluecron__merjax_get_pr_checks private-data, untrusted-input
  • mcp__gluecron__merjax_get_branch_protection private-data, untrusted-input
  • mcp__gluecron__merjax_read_file private-data
  • mcp__gluecron__merjax_list_tree private-data
  • mcp__gluecron__merjax_get_commit private-data
  • mcp__gluecron__merjax_get_diff private-data
  • mcp__gluecron__merjax_chat_continue outbound
  • mcp__gluecron__merjax_generate_commit_message outbound
  • mcp__gluecron__merjax_get_workflow_run private-data
  • mcp__gluecron__merjax_list_workflow_runs private-data
  • mcp__gluecron__merjax_get_workflow_logs private-data
  • mcp__gluecron__merjax_list_flaky_tests private-data
  • mcp__gluecron__merjax_list_runners untrusted-input
  • mcp__gluecron__merjax_get_preview_url private-data, untrusted-input
  • mcp__gluecron__merjax_semantic_search private-data
  • mcp__gluecron__merjax_search_code private-data
  • mcp__gluecron__merjax_find_symbol private-data
  • mcp__gluecron__merjax_pr_status_summary private-data, untrusted-input
  • mcp__gluecron__merjax_ci_queue_status private-data
  • mcp__gluecron__merjax_ai_cost_summary private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.gluecron/gluecron/verify?hash=29bf0f5f6614eaa2f3964bcb6fc6a72beb2b222da50eb056226515b40f40f6b2" | jq -e '.changed == false'

Pinned hash 29bf0f5f6614, from Nov 13, 2026, 09:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.gluecron/gluecron/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.gluecron/gluecron
[![Anlyon Radar](https://radar.anlyon.com/badge/com.gluecron/gluecron.svg)](https://radar.anlyon.com/servers/com.gluecron/gluecron)

Source: MCP Registry. Synced Oct 21, 2026, 17:55 UTC.

Gluecron MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Gluecron MCP server safe?

No scan can promise that. What its definitions show: 131 tools, 85 of which can change, send or delete something, and 20 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Gluecron MCP server delete data?

Yes. 24 tools can delete, cancel or revoke something: merjax_close_issue, merjax_merge_pr, merjax_close_pr, merjax_delete_repo, merjax_update_repo, merjax_revoke_repo_token and 18 more.

Can the Gluecron MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: merjax_chat_continue.

What tools does the Gluecron MCP server have?

131 tools: 24 destructive, 1 irreversible, 60 write, 46 read. merjax_close_issue, merjax_merge_pr, merjax_close_pr, merjax_delete_repo, merjax_update_repo, merjax_revoke_repo_token, merjax_rotate_token, merjax_revoke_token and 123 more.

Does the Gluecron MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.

Does the Gluecron MCP server send data to outside services?

9 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): merjax_create_issue, merjax_comment_issue, merjax_close_issue, merjax_reopen_issue, merjax_edit_comment, merjax_label_issue and 3 more.

Has the Gluecron MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.