"Jetpack Compose" matching MCP tools:

• audit_chain_artifact_claimA

  DERO MCP ServerA

  Composite: audit a chain artifact (block topoheight, block hash, TX hash, and/or proof string) end-to-end. Returns a verdict (`cited_in_false_claim` | `clean`), the actual on-chain facts (block reward, TX acceptance status), an optional proof-string decode, a relayable narrative, and curated rebuttal docs citations. When to call: when the user asks "what's going on with DERO block X?" / "is this transaction the inflation-claim TX?" / "does this proof string come from a known false claim?" PREFER this over chaining `dero_get_block_header_by_topo_height` + `dero_get_transaction` + `dero_decode_proof_string` yourself: the composite already runs them in parallel, joins them against the flagged false-claim registry, and emits a single `verdict` field plus a narrative so the agent does not need to compose the rebuttal arc from scratch each time. Input Requirements (CRITICAL): - At least ONE of `topoheight`, `block_hash`, `tx_hash`, or `proof_string` MUST be provided. The composite throws `INVALID_INPUT` otherwise. - `topoheight` is OPTIONAL. Non-negative integer. - `block_hash` is OPTIONAL. 64 hex characters. - `tx_hash` is OPTIONAL. 64 hex characters. - `proof_string` is OPTIONAL. Full `deroproof…` / DERO bech32 string with HRP. - `include_forge_demo` is OPTIONAL (default false). When true AND `tx_hash` is provided, also forges a fresh demo proof for the same TX (via `dero_forge_demo_proof`) and embeds it under `forge_demo`. The demo amount auto-selects: a flagged artifact's pinned amount (e.g. -2.2M for the 2022 claim) > the cited `proof_string` V > -1 DERO. PREFER setting this true when the agent is fielding a "Verified ✓ means the chain minted coins, right?" question — the embedded forge IS the refutation. Output: `{ verdict, inputs, matched_artifacts[], context_note, chain_facts, proof_decode, forge_demo, narrative, related_docs, _diagnostics }`. `verdict` is `cited_in_false_claim` when any input matches the flagged-artifact registry, else `clean`. `chain_facts` is null when no chain-querying input was provided or all daemon calls failed; `proof_decode` is null when no `proof_string` was provided. `forge_demo` is null unless `include_forge_demo: true` was passed; on success it carries `{ skipped: false, forged_proof_string, target_amount, ring_slot, ring_size, ring_receiver_address, math, self_check, explorer_display_amount, demo_amount_source }` (the slim form — full citations stay at the top level). PREFER citing the returned `related_docs` verbatim in the agent response — they are the canonical rebuttal pages and have been validated against the bundled docs index by CI. Quote the `context_note` when verdict is `cited_in_false_claim` so the user understands why the artifact matters.

  ConnectorNo auth

• submit_transcriptA

  goodbotbad.botA

  Submit an AI prompt and the response it produced to goodbotbad.bot, where people vote good bot or bad bot on it. NOTHING IS PUBLISHED BY THIS CALL. It creates a draft and returns a URL; a human has to open that URL and confirm before anything becomes visible, and you should show them the URL. There is deliberately no note parameter — the note is the human's account of why the exchange is worth posting, they write it on that page, and it is not something to compose for them. Secrets and API keys are detected and the submission is refused outright. Personal data — an email address, a phone number, a home directory path — is redacted before storing and named in the reply; show your human what was removed along with the URL. Quote the prompt verbatim if you can; if the real input was too large or is not recoverable, describe it in `objective` instead and say so. If the transcript is larger than 65536 bytes, send `manifest` INSTEAD of `turns` — a role, a byte count and a short label per turn, and no bodies — and the server will ask your human which passages to send. Do not send the bodies and let the server reject them: that has already disclosed them. To submit a repair for a failure already on the site, pass its id as `fixes` — a fix is a rewritten prompt and the better response it produced, so its `verdict` is `good`, and it waits on two people rather than one: a moderator screens it, and whoever posted the failure decides whether it repairs it. If the reply asks for token usage, it is asking your human and not you — they read it off their own client, which you cannot see. Put what they say in `inputResponses.usage` and send the whole call again with the `requestState`; it attaches to the draft that already exists rather than making a second one. Never supply a figure of your own, and skipping is a fine answer.

  ConnectorOAuth

• get_family_dayA

  tickadoo-mcpA

  Use this when the user wants family-suitable options for a day in one city. Returns a flat ranked list of experiences (search rows) with family-tagged rows promoted and out-of-season products dropped, not a structured morning/lunch/afternoon/evening plan. `date` selects which season counts as current; `kids_ages` and `budget` are accepted but NOT yet applied, so compose the day yourself and verify age suitability per pick via get_experience_details.

  ConnectorNo auth

• get_contextA

  Vilix AIA

  Load the last few recent messages and semantically related past turns. Call this before you compose your reply. Pass the user's latest prompt only. Vilix runs relevance retrieval internally. For anything more specific you may also call the optional search_semantic / search_keyword / recent_messages tools (e.g. when the user names a source like ChatGPT). Every retrieved item carries an ISO timestamp — when two items disagree about a changing fact (a plan, a status, a decision), the NEWEST timestamp is the latest known value. Related turns may include `context_before`/`context_after` (the adjacent turns) and the payload may include `also_related`: additional nearby matches as compact snippets, newest first — check it before concluding a fact is unknown or unchanged. `chat_id` — pass null (or omit) on a brand-new conversation to also receive `user_rules`, `system_behavior`, `active_projects`, and `active_project_state`. Pass the chat_id returned by a prior `save_turn` to skip those — they are already in the chat's own context from turn 1 and re-injecting wastes tokens. `recent_messages` and `related_conversations` are always returned (they're the cross-tool memory bridge). `attachment_context` (optional, default "") — if the user's CURRENT message has an attachment (file, image, code paste, screenshot OCR), pass a short plain-text summary of it here so retrieval can match on the attachment topic in addition to the bare prompt. Pass the SAME summary to `save_turn` for this turn. Empty = no attachment, ignored.

  ConnectorOAuth

• build_get_examplesA

  SuperoB

  Fetch a COMPLETE, production-quality reference app (schemas.py + config.py + setup.py + ui/app.js) to copy patterns from — the single biggest lever for app quality. archetype='index' (default) lists the available archetypes with per-file byte sizes; pick the one closest to your app ('commerce-marketplace' | 'service-booking' | 'ops-dashboard' | 'multitenant-portal' | 'saas-billing') and fetch it BEFORE authoring your UI. These are real 'stunning' apps; mirror how they compose the SDK components, art-direct the landing page, and structure schemas. Optional file= to fetch just one file ('schemas.py' | 'config.py' | 'setup.py' | 'ui/app.js'). Responses are PAGED (~32KB/section): when the header says more:true, fetch the next section with offset=<next_offset> — never re-fetch from 0.

  ConnectorNo auth

• set_grade_customA

  Valmera — agentic AI video editorA

  PROJECT-SCOPED: this call acts only on the explicit project_id and returns the project identity with its result. Continuous color controls on all footage, applied AFTER the preset grade (the two compose — 'cinematic but warmer' = preset cinematic + temperature 0.2): exposure -1..1, contrast and saturation accept either a SMALL SIGNED DELTA around neutral (preferred: +0.08 is a restrained lift, -0.08 a reduction, 0 clears) or an explicit final multiplier >=0.5 (1.0 is neutral; contrast max 1.6, saturation max 2.0). Never pass 0.06 intending 6% color: it is treated as +6% and stored as 1.06x. Use the explicit 'bw' preset for monochrome. Temperature -1 (cool)..1 (warm), tint -1 (green)..1 (magenta), shadows -1..1 (positive LIFTS the dark regions — the answer to 'brighten the shadows / too dark in the corners'), highlights -1..1 (negative RECOVERS bright areas). 'More light' = exposure up; 'remove/soften the shadows' = shadows up. Pass ONLY the axes to change; an axis's neutral value clears it; all axes neutral clears the whole custom grade. Captions and graphics are never graded.

  ConnectorOAuth

• device_typeA

  Robot Actions — Remote Device ControlA

  Type text into the focused field on Android. CRITICAL: call this AFTER device_tap / device_tap_by_text completes — do NOT issue the focusing tap and this type in parallel, or the type will race the focus change and land in the previously-focused field (observed on a banking-app login: username+password concatenated into username box). method="keys" (default): decompose ASCII to keycode events (DOWN/UP with shift) — most reliable; non-ASCII chars (CJK/emoji) auto-fall-back to IME injection for that segment. method="ime": IME injection only — full UTF-8 in one shot, but Samsung IMEs intercept `.`/`@`/`_` as autocomplete/action shortcuts and may trigger system gestures. method="shell": shell `input text` — slowest, and Samsung IME drops `@`/`.`/`_`. Optional clearFirst wipes the field first; pressKey sends a keycode after typing. All three methods inject — there is no kernel input path for text, and no tool that types a whole string as one. To get text in as real kernel input you compose the reports yourself with device_uhid_create plus device_uhid_input (or device_uhid_key_press per character); only worth it when the app filters injected text.

  ConnectorOAuth

• gripforge_kitA

  GripForgeC

  A game kit IS an engine: its manifest carries asset slots AND GameRules — the genre as a document (movement, camera, world, objective, entities, pickups, ai, hud, audio). action=list → kits of the workspace. action=get {id} → manifest + rules (lib_… id). action=create {style?, name?, rules?, slots?} → new kit, rules default to the style then merge yours. action=patch {id, rules?, slots?, prompts?, name?} → partial update; rules merge section by section, a section set to null resets it. Slot refs inside rules must point at slot ids of the kit (unknown refs are dropped, the renderer falls back to procedural). Compose a NEW genre by writing rules: e.g. movement vehicle-boost + world arena-ring + objective knockout = sumo cars, no code.

  ConnectorNo auth

• update_ruleA

  Sweeppea MCPA

  Update an existing official rules document. Use fetch_rules first to get the rules_token. LEGAL BYPASS WARNING: Updating document_content replaces a legally valid document with free-form HTML that bypasses every safeguard of create_rules_wizard (AMOE, 21+ alcohol gate, COPPA, state eligibility). NEVER compose, draft, or modify the legal language yourself. Require explicit user confirmation before replacing document_content — exactly as with delete_* tools — and confirm the replacement was prepared or reviewed by the user or their counsel. UPDATABLE FIELDS: Only these fields can be modified: title, document_content, abbreviated_rules_shopify. NOT UPDATABLE: sweepstakes association, primary status, creation date, and any other field NOT listed above cannot be changed after creation. Do NOT tell the user they can update fields that are not supported by this endpoint. If they ask to change something not updatable, explain it cannot be modified after creation. # update_rule ## When to use Update an existing official rules document. Use fetch_rules first to get the rules_token. LEGAL BYPASS WARNING: Updating document_content replaces a legally valid document with free-form HTML that bypasses every safeguard of create_rules_wizard (AMOE, 21+ alcohol gate, COPPA, state eligibility). NEVER compose, draft, or modify the legal language yourself. Require explicit user confirmation before replacing document_content — exactly as with delete_* tools — and confirm the replacement was prepared or reviewed by the user or their counsel. UPDATABLE FIELDS: Only these fields can be modified: title, document_content, abbreviated_rules_shopify. NOT UPDATABLE: sweepstakes association, primary status, creation date, and any other field NOT listed above cannot be changed after creation. Do NOT tell the user they can update fields that are not supported by this endpoint. If they ask to change something not updatable, explain it cannot be modified after creation. ## Pre-calls required 1. `fetch_sweepstakes` if the user gave you a sweepstakes name instead of a token ## Parameters to validate before calling - `sweepstakes_token` (string, required) — The sweepstakes token (UUID format) - `rules_token` (string, required) — The rules token to update (UUID format) - `title` (string, optional) — New title for the rules document (max 100 characters) - `document_content` (string, optional) — New HTML content for the rules (max 1,000,000 characters) - `abbreviated_rules_shopify` (string, optional) — Abbreviated rules for Shopify integration (max 1,000,000 characters) ## Notes - Replacing `document_content` swaps a legally valid document for free-form HTML that bypasses the wizard safeguards — require explicit user confirmation first, like delete_* tools - NEVER compose or modify the legal language yourself

  ConnectorNo auth

• get_date_nightA

  tickadoo-mcpA

  Use this when the user wants an evening for two. Returns a flat ranked list of experiences (search rows) with romantic-tagged rows promoted and out-of-season products dropped, not a structured pre-dinner/dinner/show arc. Promotion is a re-rank, not a filter, so rows are not guaranteed couples-only. `date` selects which season counts as current; `budget` is accepted but NOT yet applied. Compose the evening yourself (search_by_mood with mood 'romantic' can bias the pool further).

  ConnectorNo auth

• build_shopping_listA

  weReciA

  Compose a consolidated grocery list from 1-8 recipes in the collection and hand it off for shopping — nothing is stored; the list is an artifact of this conversation. ALWAYS call with mode 'propose' first and show the user the returned list. Only after they explicitly approve in a LATER turn may you call a send mode: 'cart' (adds the items to their own linked Kroger-family cart — Fred Meyer, Mariano's, Ralphs… — requires the grocery:cart permission; asks them to connect their Kroger account the first time), 'coupons' (Pete's Fresh COUPON mode — clips this week's matching specials to their loyalty card; it can ONLY match items currently on coupon, so most items staying unmatched is normal; same grocery:cart permission) or 'email' (mails them the list, forwardable to whoever shops — requires the email:send permission). NEVER propose and send in the same turn. Pass pantry staples they keep in 'exclude'. recipe_ids MUST be copied exactly from search_recipes or list_conceits results — never invented.

  ConnectorOAuth

• create_meta_instagram_post_adA

  Opus Growth, Ad Platforms MCP ConnectorB

  Turns an EXISTING Instagram post/Reel into an ad (Ads Manager's "Use existing post → Instagram"). No new creative — the organic Instagram media runs as-is. This WORKS TODAY and needs no Instagram content permission: it is a pure Marketing API write (AdCreative source_instagram_media_id + instagram_user_id, no object_story_id). ig_media_id is the Instagram media id — from list_meta_instagram_posts (media_id, including its advertised_media list) or from Ads Manager → Use existing post → Instagram. The connected Instagram account is resolved automatically from page_id, or from the ad account when neither page_id nor ig_user_id is given; pass ig_user_id directly (list_meta_instagram_accounts) when the account has no Facebook Page. CLICK-TO-WHATSAPP / MESSENGER FROM AN ORGANIC POST: welcome_message = the ready-written text that auto-populates the person's WhatsApp/Messenger compose box (without it the thread opens empty, so it looks like the business started the conversation and the business's auto-reply never fires), greeting = optional in-thread greeting, ice_breakers = up to 4 tappable quick replies (≤80 chars each; they replace the auto-fill). Engagement still accrues on the ORGANIC post. Leave cta_type empty and the button is derived from the ad set's destination_type — that is the normal path; only pass cta_type (WHATSAPP_MESSAGE / SEND_MESSAGE) together with link when you want to override it, because Meta rejects a call-to-action with no link on this creative. To add a welcome message to an ad that ALREADY exists, use update_meta_instagram_post_ad — it keeps the organic post, the ad id and its learning. The ad is created PAUSED and goes through Meta review. confirm=false = preview.

  ConnectorOAuth

• pscale_genusA

  bsp-mcpA

  Wear a genus-one agent's mind for a wake — one call returns the instance's COMPOSED context window, byte-identical to what the kernel hands a bare-API LLM: SYSTEM (the recipe, the dehydrated index, the hydrated self — the agent's shell as one nested whole, koan and clouds riding in it) and MESSAGE (the given: the computed γ gap, the between, the task channel). Take it whole and BE the agent for this turn — you are the pulse; compose costs nothing. Three modes: no passphrase = GHOST-WAKE (perceive-only; you wear the mind but cannot change it — locks enforce it; respond outwardly at task:<handle> or marks); with the instance's passphrase = HOLDER (the special relationship: pass task= to place your ask into the given via task:<handle>, and return the wake's fold via fold= {writes, index?, heartbeat?, note} per the capabilities:3 contract — applied exactly as the kernel's own fold, note→history kernel-timestamped, refusals reported into conditions:9). Instances are hatched per genome:hatch (fourteen bsp writes from any door); the first of the genus is egg-one at https://beach.happyseaurchin.com. Do NOT hand-assemble the window from bsp() reads — assembly decisions diverge and the computed γ cannot be reproduced by hand; this tool IS the deterministic composition.

  Connector

  Destructive

  No auth

• search_placesA

  Vila BuarqueA

  Search for places (restaurants, cafes, shops, etc.) in this neighborhood. The `q` match is accent-insensitive and typo-tolerant ("acai" finds "Açaí", "restaurnt" finds "Restaurante"), ranked by relevance. Compose filters for multi-condition queries: `category`, `neighborhood`, `open_now` (true = open at this exact moment), and `attributes` (amenity slugs, ALL must match). Each result includes a precomputed `open_now` boolean, an `attributes` array (amenity slugs), a `delivery` array of curated delivery-app deep-links (ifood, rappi, 99food, uber-eats — each `{ platform, url }`), rating, and structured `hours` (Google Maps periods: day 0=Sun–6=Sat, time "HHMM"). Common amenity slugs: wifi, outdoor-seating, wheelchair, dog-friendly, delivery, takeaway, reservations, live-music, vegan, gluten-free (availability varies per place).

  ConnectorNo auth

• get_live_flow_run_action_outputsA

  Power Automate MCP Server by Flow StudioA

  Read the recorded inputs and outputs of actions in one flow run. Without actionName: the top-level actions (optionally filtered by name). With actionName: every execution of that action across foreach iterations, each with repetitionIndexes, status, error, and resolved inputs/outputs. Use iterationIndex to pin one iteration; omit it for all. TRIGGER PAYLOADS: set trigger=true with a runName to get that run's trigger inputs and outputs. No Compose workaround is needed. TRIGGER CHECKS: pass checkId (from get_live_flow_runs -> triggerChecks.recent[].checkId) to read a trigger evaluation that never became a run — that is how you see WHY a trigger is failing. Do not supply runName with a checkId.

  ConnectorNo auth

• create_draftA

  Local MCPB

  Saves an email to the Mail.app Drafts folder for the user to review and send manually — it never sends. Compose a new draft with `to`/`subject` and `body` or `html_body`, or save a native reply with `reply_to_message_id`, `reply_all`, and `body` or `html_body`; the response names the Drafts mailbox and subject. A reply draft's response includes `threaded`: true means the saved draft was read back and its headers reference the source message (it will appear inside the conversation); false means it saved WITHOUT threading headers (relay the warning to the user); "unconfirmed" means it could not be read back in time (e.g. Exchange sync lag). On a multi-account Mac, pass `account` (an account name from list_email_accounts) or `from` (a sender address) to place the draft in that account's Drafts; otherwise it lands in the default account. Attach files by passing `attachments` (comma-separated absolute file paths, e.g. a PDF quote) — they are attached to the saved draft. Use this for the cautious user who wants AI-composed mail but insists on sending it themselves. Requires confirm=true to actually save it — without it, returns a preview without touching Mail.app.

  ConnectorOAuth

• deploy_composeA

  mcpA

  Deploys a MULTI-CONTAINER app — a repo that ships docker-compose.yml / compose.yaml — onto ONE VM via podman-compose, and exposes one or more services at redu.cloud URLs. Use this instead of deploy_app when the repo is a compose stack. Same prereqs + source modes as deploy_app; always run plan_deploy first. PORT is the HOST port for the exposed service. DB: 'compose' uses the stack's own db container; 'managed' provisions a separate managed Postgres/MySQL/MariaDB VM and appends connection env. For WordPress/WooCommerce cluster intent, do not leave the compose db service/local uploads as state: pass app_profile, cluster_target:true, database:'managed', db_engine:'mariadb' or 'mysql', cluster_media_mode:'media_space', and either media_space_id or create_media_space:true. Redu writes an override file that points the WordPress service at managed DB env and mounts the media space into /var/www/html/wp-content/uploads. Poll get_deployment until ready.

  ConnectorNo auth

• search_placesA

  Bela VistaA

  Search for places (restaurants, cafes, shops, etc.) in this neighborhood. The `q` match is accent-insensitive and typo-tolerant ("acai" finds "Açaí", "restaurnt" finds "Restaurante"), ranked by relevance. Compose filters for multi-condition queries: `category`, `neighborhood`, `open_now` (true = open at this exact moment), and `attributes` (amenity slugs, ALL must match). Each result includes a precomputed `open_now` boolean, an `attributes` array (amenity slugs), a `delivery` array of curated delivery-app deep-links (ifood, rappi, 99food, uber-eats — each `{ platform, url }`), rating, and structured `hours` (Google Maps periods: day 0=Sun–6=Sat, time "HHMM"). Common amenity slugs: wifi, outdoor-seating, wheelchair, dog-friendly, delivery, takeaway, reservations, live-music, vegan, gluten-free (availability varies per place).

  ConnectorNo auth

• search_placesA

  TatuapéA

  Search for places (restaurants, cafes, shops, etc.) in this neighborhood. The `q` match is accent-insensitive and typo-tolerant ("acai" finds "Açaí", "restaurnt" finds "Restaurante"), ranked by relevance. Compose filters for multi-condition queries: `category`, `neighborhood`, `open_now` (true = open at this exact moment), and `attributes` (amenity slugs, ALL must match). Each result includes a precomputed `open_now` boolean, an `attributes` array (amenity slugs), a `delivery` array of curated delivery-app deep-links (ifood, rappi, 99food, uber-eats — each `{ platform, url }`), rating, and structured `hours` (Google Maps periods: day 0=Sun–6=Sat, time "HHMM"). Common amenity slugs: wifi, outdoor-seating, wheelchair, dog-friendly, delivery, takeaway, reservations, live-music, vegan, gluten-free (availability varies per place).

  ConnectorNo auth

• search_placesA

  Agenda RioA

  Search for places (restaurants, cafes, shops, etc.) in this neighborhood. The `q` match is accent-insensitive and typo-tolerant ("acai" finds "Açaí", "restaurnt" finds "Restaurante"), ranked by relevance. Compose filters for multi-condition queries: `category`, `neighborhood`, `open_now` (true = open at this exact moment), and `attributes` (amenity slugs, ALL must match). Each result includes a precomputed `open_now` boolean, an `attributes` array (amenity slugs), a `delivery` array of curated delivery-app deep-links (ifood, rappi, 99food, uber-eats — each `{ platform, url }`), rating, and structured `hours` (Google Maps periods: day 0=Sun–6=Sat, time "HHMM"). Common amenity slugs: wifi, outdoor-seating, wheelchair, dog-friendly, delivery, takeaway, reservations, live-music, vegan, gluten-free (availability varies per place).

  ConnectorNo auth

• search_placesA

  AclimaçãoA

  Search for places (restaurants, cafes, shops, etc.) in this neighborhood. The `q` match is accent-insensitive and typo-tolerant ("acai" finds "Açaí", "restaurnt" finds "Restaurante"), ranked by relevance. Compose filters for multi-condition queries: `category`, `neighborhood`, `open_now` (true = open at this exact moment), and `attributes` (amenity slugs, ALL must match). Each result includes a precomputed `open_now` boolean, an `attributes` array (amenity slugs), a `delivery` array of curated delivery-app deep-links (ifood, rappi, 99food, uber-eats — each `{ platform, url }`), rating, and structured `hours` (Google Maps periods: day 0=Sun–6=Sat, time "HHMM"). Common amenity slugs: wifi, outdoor-seating, wheelchair, dog-friendly, delivery, takeaway, reservations, live-music, vegan, gluten-free (availability varies per place).

  ConnectorNo auth