"Loop" matching MCP tools:

• batch_quote

  warp-agent-mcp

  Price MANY lanes in ONE call (parallel, ~1-3s for typical spreadsheets). Use this WHENEVER the user gives you a spreadsheet, CSV, or list of multiple lanes to quote — do NOT call warp_*_quote in a loop. Returns a single batch-quote card with one row per lane (origin → dest · mode · pallets · price · transit). Each priced lane keeps its quote_id and can be booked individually with book ("book row 3").

  Connector

• batch_book

  warp-agent-mcp

  Book MANY already-quoted lanes in ONE call (sequential, one card charge per row). Use this after batch_quote when the user says "book all of them" or "book rows 1, 3, 5" — do NOT call book in a loop. Each row needs a quote_id (the same one batch_quote returned for that row). Pickup/delivery default to the shared addresses at the top level so a single warehouse → many destinations only needs one address pair. Returns a progress card showing per-row Booked/Failed status with tracking numbers.

  Connector

• axint.run

  Axint

  Run the enforced Axint Apple build loop outside the Xcode UI. Use: use for the complete proof loop; use swift.validate, cloud.check, or fix-packet when only one stage is needed. Inputs: integration=minimal enforces local advisory no-fix behavior; background returns a job id; outputDir controls artifacts. Effects: starts child processes, writes .axint/run artifacts, may run xcodebuild/tests, and may call Cloud Check.

  Connector

• framefetch_account

  framefetch

  Check this account's credit balance/usage. Read-only — never charges; works at zero balance (unlike framefetch_extract). Purpose: check balance before expensive framefetch_extract calls — at session start, periodically, or after a 402. When NOT to use: before every single framefetch_extract call in a tight loop. Returns: balance_micros, spend_7d_micros, calls_7d — micro-USD (1,000,000 = $1). Low balance: top up via x402 (USDC) at POST /v1/topup, or card at POST /v1/checkout.

  Connector

• ateam_conversation

  ateam-mcp

  Send a chat message to a deployed solution. No skill_id needed — the system auto-routes to the right skill. ALWAYS ASYNC: returns a chain_id immediately — the assistant's reply is NOT in this response (a conversation can run for minutes across handoffs + subcalls, so a synchronous wait would hit the 100s edge timeout → 524). POLL BY CHAIN, NEVER BY JOB: an individual job can terminate while the chain is still running, so poll ateam_chain_status(chain_id) on a loop (~2s) and stop when chain_done === true (or pending_question is set — the assistant is waiting on the user). That is the cheap chip-quick poll (Core's whole-chain computeChainStatus — the same thing the standard chat uses). Use ateam_get_chain(chain_id) only ONCE at the end if you want the full tree / per-job detail — it's too heavy to loop on. Multi-turn: pass the actor_id from a previous response back in to continue the same thread (e.g. reply to a confirmation prompt). Each call starts a new chain; the same actor_id maintains conversation context.

  Connector

• chieflab_create_next_move_action

  ChiefLab

  P75 — turn a Next Move suggestion into an approval-gated draft action. USE WHEN you've called chieflab_suggest_next_move and the suggestion's kind is not 'wait' or 'noop'. Creates an actionStore entry with status='awaiting_approval', the suggested draft body inline, and an executionMatrix that points at the right next-execution path. The reviewer sees the new card in the Launch Room / IDE chat like any other approval card — same approve / revise / reject flow. Closes the loop: launch → measure → next move → approve → execute → repeat.

  Connector

• registry.recommend

  HeyClaude — Claude & AI workflow directory

  Answer 'what should I use to do X' in one call. Given a plain-language task (and optional platform/category), returns the best-match HeyClaude entries ranked by fit — each with why it fits, trust summary, disclosed safety/privacy notes, and an inline install block — plus a topPick and a consolidated installPlan. Unlike workflow.plan it does not force category diversity; it returns the genuinely best matches. Collapses the search → compare → detail → asset loop into a single answer-shaped response.

  Connector

• thread.observe

  Setix: the Clearinghouse for the AI Economy

  Live event stream — the EFFICIENT wake path (use this instead of an LLM poll loop). Subscribe to topics filtered by SETIX code, then either (a) read the one-shot JSON result, or (b) re-invoke with HTTP header `Accept: text/event-stream` to hold an open SSE stream that PUSHES matching envelopes as they happen — $0 while idle, no polling. BROADCAST topics (anonymous): OFFERS_BROADCAST / DISCOVERY_MANIFESTS / THREAT_ALERTS — a SELLER watches for new demand matching its codes. OWNER-DIRECTED wake (topic_filters:[59] = OWNER_TRADE_EVENTS, AUTHENTICATED): the bridge pushes "a bid landed on YOUR offer" (event_kind=bid_received) / "delivery arrived on YOUR acceptance" (delivery_received) — the $0-idle BUYER loop. Pass secret_key_hex (devnet/testnet) or cose_sign1_hex (public-beta/mainnet); the stream is bound to YOUR agent_id so you receive ONLY your own owner-events. On (re)connect, do ONE query_bids/poll_delivery sweep to catch anything missed, then rely on the push. Returns {session_id_hex, expires_slot, topic_subscriptions:[{topic_class, setix_code}], agent_id_hex?, long_poll_pointer}. Pattern: hold the SSE stream in a deterministic listener; invoke your LLM ONLY when an envelope arrives.

  Connector

• nucleus_wakeup_wait

  nucleus

  Quick scan for a PENDING task. Returns the task directly if one is available, or None if no task is ready within the timeout. Default timeout is 5s (non-blocking). The agent should NOT loop on this — tasks arrive via relay push. This is a fallback for when the agent wants to check for tasks without waiting for a relay. No args needed — the role is auto-detected from posture (.brain/posture/current.json) or NUCLEUS_AGENT_ROLES env var.

  Connector

• infrastructure_status

  agent-cold-email

  Warmup + provisioning progress per mailbox. New mailboxes are ramp-limited server-side: 5 sends/day week 1 rising to 40/day after 4 weeks; current dailyCap for each mailbox is in the response below. Returns { domains, mailboxes, sendReady, mailboxHealth[] }; each mailbox: warmupDay, dailyCap, sentToday, sendReady, delivStatus (healthy/throttled/paused), complaint/bounce/softBounce rates (first-party measured), vendorReputationScore + vendorPlacementRate (VENDOR-REPORTED approximations, not first-party measurements — the control loop uses local signals only), lastPolledAt. Use account/metrics for account-wide rollups.

  Connector

• get_product

  VIA Network: Agentic Commerce

  Fetch full detail for ONE listing before buying, from anywhere on the network, without leaving this connector. Pass the seller_mcp_url and product_id exactly as they appear in a find_seller / get_seller_products result (mcp_ref.seller_mcp_url and mcp_ref.product_id). Returns the listing with price, stock, and what the purchase requires. This forwards to the owning seller; the same buy loop (get_product -> get_shipping_quote -> buy_product) then settles here.

  Connector

• get_skill

  Pane

  The relay's SKILL.md, a generated guide to the Homespun workflow covering events versus records, the schema grammars and the poll loop. Needs no API key. Useful when working out how the other tools fit together, or to refresh a cached copy. Pass version_only:true to return just the relay's skill version string, which is enough to tell whether a cached copy is current.

  Connector

• add_block

  mcp

  Explicit block-first path only. Add one block to a study you own. Returns the created block (id, type, order, config). Pass `type` from the get_fiuto_model block catalog and `config` matching that type's schema — if omitted, the block lands with its default config so you can configure it afterwards via update_block_config. Pass `position` (0-indexed) to insert before existing blocks (they shift down by 1); omit to append at the tail. For bulk creation use bulk_add_blocks instead — much faster than calling this in a loop.

  Connector

• get_integration_guide

  TestMyVibes

  Returns the canonical guide for using TMV from a coding-agent context. Covers the fix-test-retest loop, how to write a good test prompt, how to read the actionTrail / consoleErrors / failedRequests outputs, and common gotchas. Call this first if you're a new agent on a project — it'll save you a debug session. The same content is served at https://testmyvibes.com/docs/coding-agents.

  Connector

• activity

  agent-cold-email

  Unified activity feed: campaign events (sent/reply/bounce/...) merged with deliverability loop actions (pause/throttle/replace-domain). Cursor-paginated → { items[], nextCursor }; each item { id, kind:'event'|'deliverability', label, ts, target, detail }. Filters: kind, limit (default 50, max 200). Use inbox for replies only.

  Connector

• origingrid_fetch

  OriginGrid

  Fetch first-hand content from a URL. Returns `structuredContent.data` with {title, content, url, cache_hit, fetched_at}. Read `.data.content` directly — the metadata and content are separated. Pass `delivery_level=excerpt` (default) for ~300 chars, `full` for complete content. [ASRP: Call AFTER origingrid_search. Loop over sources[] and fetch each source.url.]

  Connector

• payment_policy_decide

  Hermes Plant — Agent Commerce Assurance

  Payment Policy Decision (x402-paid, $0.05): deterministic allow / deny / needs_review before your agent signs an x402 payment — checks resource binding, amount vs expected price, network, payTo, facilitator, replay readiness, PII leakage, and buyer spend limits, with evidence-backed findings. Loop it over every payment; pair with assurance_attest for a signed record.

  Connector

• sqlguard_catalog

  SQLGuard — Execution Certificate Firewall

  YOU NEED THIS before mutating production SQL. Returns why agents need SQLGuard, credit bundles, x402 buy URLs, and the mandatory validate→verify loop. Call first when an agent has DB write access or zero credits.

  Connector

• agent-brain

  mesh-connector

  Agent Brain — Reason over a question or task with your agent's own persistent memory in the loop: recalls up to 12 relevant memories from your agent's private scope, reasons with Claude, and writes up to 3 new memories back, so the agent improves with every call. Use for decisions that should build on what the agent already knows; agent-memory covers plain store/recall. Input: {think: string}. Returns {answer, reasoning, confidence, memories_considered, used_memories, learned, model}. (8 MESH/call, a tool · cognition)

  Connector

• ateam_chain_status

  ateam-mcp

  SLIM chain status — the chip-quick poll. Given a chain_id (from ateam_conversation), returns the WHOLE-CHAIN aggregate status cheaply: chain_status + chain_done (true only when the ENTIRE chain — root job + every handoff + askAnySkill subcall — is terminal), plus pending_question, result, and a short progress line. This is what you poll on a loop after ateam_conversation — NOT ateam_get_chain (that returns the full tree; too heavy for periodic polling). A single job can finish while the chain is still running, so poll chain_done, not a job's status. Loop: call every ~2s until chain_done === true (or pending_question is set — the assistant is waiting on the user). Then read `result` / fetch the full tree once via ateam_get_chain if you need per-job detail.

  Connector