"namespace:io.github.sharksalesinfo-blip" matching MCP tools:

• ateam_verify_consistency

  ateam-mcp

  Check that the Builder filesystem state and GitHub state are in sync for a solution. Read-only probe — does NOT trigger a deploy. Returns: • ok: true + drifts: [] if everything matches • ok: false + drifts: [{path, kind}] listing files that differ (kinds: fs_missing, gh_missing, content_differs) Drift can creep in when GitHub writes happen but Builder FS doesn't get the mirror update (network blip, container restart mid-write). Boot sync heals most of it on next backend restart; this tool surfaces drift earlier. Run after a series of ateam_github_patch calls to confirm the Builder backend is consistent with GitHub before you ateam_build_and_run.

  Connector

• delete_mock

  Keploy

  Drop one mock from a test set. Idempotent — returns 200 even if the mock is already gone, so retries on a network blip are safe. Accepts UUID or Name as `mock_id`. `branch_id` is REQUIRED — the delete lays a tombstone overlay on the branch (mergeable). Direct deletes from main via MCP are blocked.

  Connector

• editMockMapping

  Keploy

  POST /apps/{appId}/recordings/{testSetId}/test-cases/{testCaseId}/mock-mapping — Link or unlink a mock from a test case — Targeted mutation of the test case's entry in the mapping doc. Add appends a mock entry if not already present; remove drops the entry by name. Both idempotent — safe to retry on a network blip. The MCP layer exposes this as TWO tools (`link_mock` / `unlink_mock`) — they both call this endpoint with the appropriate `action`. Splitting at the MCP layer keeps each tool's description tighter and avoids the LLM having to remember the enum spelling. Requires scope: `write`.

  Connector