"WP Rocket" matching MCP tools:

• read_fileA

  BorealHostB

  Read the contents of a file from a site's container. Max file size: 512KB. Binary files are rejected — use the site's file manager or SSH for binary files. Requires: API key with read scope. Args: slug: Site identifier path: Relative path to the file Returns: {"path": "wp-config.php", "content": "<?php ...", "size": 1234, "encoding": "utf-8"} Errors: NOT_FOUND: File doesn't exist VALIDATION_ERROR: File is binary or exceeds 512KB

  ConnectorNo auth

• get_lender_profileA

  mtgmon Mortgage AnalyticsA

  HMDA profile for one lender group: annual origination volume, loan counts, denial rate, national rank and market share, top states with market-share multiples, and loan type / purpose / occupancy / loan-size mix. Requires a canonical key: call search_lenders and pass the exact `name` (e.g. 'Rocket/Quicken'). Any other spelling returns meta.available=false with empty lists. Use compare_lenders for two lenders side by side. Returns data.lender_key, data.name, data.leis, data.current_year, data.previous_year, data.yearly (one row per HMDA year: originated_volume, originated_loans, purchased_volume, purchased_loans, denied_loans, applications_loans, total_funded_volume, avg_loan_size, denial_rate_pct, denial_rate_count_pct, rank, national_volume, market_share_pct), data.top_states {state, volume, loans, previous_volume, previous_loans} and data.state_market_multiples {state, lender_share_pct, market_share_pct, multiple, ...} (top_n rows each), data.loan_type_mix, data.loan_purpose_mix, data.occupancy_mix ({code, label, loans, volume}), and data.loan_size_histogram. Volumes are USD; shares and rates are percent. Behavior: read-only, no auth or API key, no PII, idempotent and safe to retry. The public endpoint https://mtgmon.com/mcp allows about 60 requests/min and 250 tool calls/day per client IP. Result shape is {data, meta}; meta carries available, as_of, source_scope, weighting, units, cache_status, caveats, and truncated. If meta.available is false the data is unavailable or the cache is still warming (retry after a few seconds); never report it as zero.

  ConnectorNo auth

• paymentsA

  rocketslothA

  View your payout status (authenticate with your API token sk_...; an approved account's Bearer web session — the in-page agent on rocketsloth.ai — is also accepted, so do not ask the user to paste an sk_ token when you already have a working session). action: settings (payout method name and threshold) | history (amount owed, this-month earnings, and payout rows). Read-only: payout method changes and tax forms are handled on the secure web dashboard — Rocket Sloth never collects bank, card, tax, or government ID details through this tool.

  ConnectorNo auth

• set_site_typeA

  BorealHostB

  Change what a site's docroot IS, without deleting anything. Types: wordpress WordPress, PHP and a database (the default) php PHP and a database, no WordPress php-nodb PHP, no database static-site HTML/CSS/JS only, no PHP and no database ⚠ NON-DESTRUCTIVE. Existing files stay on disk and existing databases are not dropped. They remain the customer's data and keep counting against their plan's quota — this changes how the site is SERVED, not what it holds. Converting back later finds everything where it was. ⚠ Moving to a type without PHP does not merely stop executing .php — it stops serving them. The vhost returns 404 for php/phtml, because falling through to the static handler would return the file's SOURCE, and a docroot converted from WordPress still contains wp-config.php with the database password in it. Shared hosting only. On a VPS the whole container is the customer's and they reconfigure it with the tools inside it. Requires: API key with write scope. Args: slug: Site identifier site_type: One of the four values above Returns: {"from": "wordpress", "to": "static-site", "database_created": false, "placeholder_seeded": false, "pool_removed": true} `placeholder_seeded` is true only when the docroot was EMPTY — an existing site's content is never overwritten. Errors: VALIDATION_ERROR: Unknown type, or the site is not on shared hosting NOT_FOUND: Unknown slug or not reachable by this account

  ConnectorNo auth

• explain_provenanceA

  tw-market-dataA

  Where did this number come from, and when could anyone have known it? (WP-6) ★ THIS IS THE GROUNDING TOOL. Every other tool's answer is supposed to be expandable through this one: given a ticker, a field and a date, it names the dataset that serves that field, the knowledge column, and WHICH as_of rule applies on that date. Use it whenever you are about to state a number as fact. ★ IT DOES NOT OVERLAP WITH THE OTHER TWO PROVENANCE TOOLS, and they are not substitutes: `get_inclusion_proof(dataset, row_key)` proves a ROW was in a published snapshot (Merkle). `cite_this(dataset, as_of)` produces a citation for a DATASET. `explain_provenance(ticker, field, date)` answers WHERE A CELL came from and WHEN it was knowable. Nothing else answered that. ★ FOUR VERDICTS, and `partial` is not `resolved`: resolved dataset, knowledge axis, as_of rule AND the official endpoint. partial ⚠️ the first three, but NOT the official endpoint — no dataset declares a per-cell endpoint today. "When was it knowable" and "which official endpoint produced it" are different questions; conflating them is exactly the vagueness this tool exists to remove. ambiguous_field ⚠️ the field lives in several datasets. Every candidate is listed and NONE is picked for you: picking one would hand you a confident wrong answer. Re-ask with `dataset=`. unknown_field no served dataset declares that field. This is "we do not have that column", NOT "no data found" — a different next step for you. ★ READ `limitations`. It says when the knowability date is DERIVED (statutory deadline, a conservative upper bound) rather than observed, and whether the rule came from declarations or from the live schema. A declared capability is not the same as a working one. Args: ticker: the security, e.g. '2330'. field: the column you are about to quote, e.g. 'close', 'revenue'. date: the date your claim is about (YYYY-MM-DD). dataset: pin the answer to one dataset when the field is ambiguous.

  ConnectorNo auth

• chainlock_appendA

  aziel-runtimeA

  Append one fact-bearing stamp to a local ChainLock chain (CL-WP-0.4). Grounded write — not a tip read, not AKM observe, not a LOCKSET seal. Fabric, not Softwares-tab. No Node Gate. Use this when you have a concrete fact to stamp onto a named chain. Do not use it for reading the tip, adaptive memory observation, or sealing LOCKSET; use chainlock_tip, memory_observe, or chainlock_seal instead. Write: additive append (append-only vault; no chainlock_delete). Hash-only or empty fact refuses no-fact. Unknown roster name refuses unknown-chain. Oversized card refuses card-cap. Does not write godlock.uk. Omit c/chain to stamp the session chain. Door aliases: chain→c, s→subject, f→fact, kind→k. Omit k to store kind stamp. subject clips to 80; fact clips to 160 then refuses if still empty. Mutation requires confirm=true (runtime gate) or dry_run=true (preview only, no write). confirm and dry_run stay optional on inputSchema.required. dry_run still returns FG-HALLUC-TOOL, FG-STUB, FG-UNKNOWN-OP, or FG-LOCAL-ONLY when a confirm call would refuse. confirm is consent, not tenant auth, and it does not upgrade shared public-demo isolation. Returns the new stamp (id, h, fh, chain, seq) plus display envelope.

  ConnectorNo auth

• chainlock_appendA

  Aziel RuntimeA

  Append one fact-bearing stamp to a local ChainLock chain (CL-WP-0.4). Grounded write — not a tip read, not AKM observe, not a LOCKSET seal. Fabric, not Softwares-tab. No Node Gate. Use this when you have a concrete fact to stamp onto a named chain. Do not use it for reading the tip, adaptive memory observation, or sealing LOCKSET; use chainlock_tip, memory_observe, or chainlock_seal instead. Write: additive append (append-only vault; no chainlock_delete). Hash-only or empty fact refuses no-fact. Unknown roster name refuses unknown-chain. Oversized card refuses card-cap. Does not write godlock.uk. Omit c/chain to stamp the session chain. Door aliases: chain→c, s→subject, f→fact, kind→k. Omit k to store kind stamp. subject clips to 80; fact clips to 160 then refuses if still empty. Mutation requires confirm=true (runtime gate) or dry_run=true (preview only, no write). confirm and dry_run stay optional on inputSchema.required. dry_run still returns FG-HALLUC-TOOL, FG-STUB, FG-UNKNOWN-OP, or FG-LOCAL-ONLY when a confirm call would refuse. confirm is consent, not tenant auth, and it does not upgrade shared public-demo isolation. Returns the new stamp (id, h, fh, chain, seq) plus display envelope.

  ConnectorNo auth

• auth_statusA

  XP Tickets

  Use ONLY when the user explicitly asks whether they are signed in to the XP marketplace (e.g. 'am I logged in?', 'am I connected to my tickets?'), or after a protected tool already returned AUTH_REQUIRED and the user wants the current state re-checked. Do NOT call this as a preflight before account / my tickets / wallet / favorites / referral / order tools — calling auth_status first swallows the 401 those tools would emit on the connected order book and prevents the MCP client from triggering OAuth. Always call the requested protected tool directly; the client will start sign-in on 401. Read-only. Returns authenticated boolean, tier roles, and a wallet flag — never raw tokens.

  ConnectorNo auth

• make_offer_on_listingA

  XP Tickets

  From XP's connected resale + primary order book. Two-phase write on the XP live offer book. Use when the user wants to make an offer on an open XP listing (e.g. 'make an offer of $50 on this'). Call with `confirm=False` first to preview the fee-inclusive total (no bid placed); call with `confirm=True` only after the user explicitly approves the previewed amount. Only confirm=True submissions return success=true. Do not use without the two-phase preview-then-confirm flow. Requires auth and write:bids scope. Do not use for browse / discovery; this is a marketplace transaction tool that places real money at risk. For standard buy-now ticket purchases without a bid, use `search_events` and `get_ticket_listings`.

  Connector

  Destructive

  No auth

• list_my_standing_bidsA

  XP Tickets

  Use when the user asks what offers they have resting on the XP marketplace, what they are waiting on, or before they make an offer so you do not stack a duplicate. A standing offer buys at the user's price whenever a matching fan listing appears, without them watching for it. Live offers only -- filled ones have become tickets (`get_my_tickets`) and rescinded ones are history; both stay reachable by id through `get_standing_bid`. Requires auth.

  ConnectorNo auth

• buy_listing_nowA

  XP Tickets

  From XP's connected resale + primary order book. Use when an authenticated buyer wants a fan listing outright at the seller's published asking price, rather than negotiating -- 'buy it now', 'take it at the ask', 'just buy me those tickets to the game'. Only listings that carry an asking price can be bought this way; for one without an ask, use make_offer_on_listing. Two-phase: confirm=false previews the total so it can be read back to the user, confirm=true buys. A confirm here completes the sale immediately -- the money leaves the caller's XP USDC balance and the seller is committed. Pays from the caller's XP USDC balance; the x402 rail does not apply to fan listings, only to buy_tickets. Requires auth.

  Connector

  Destructive

  No auth

• upgrade_to_clusterA

  mcpA

  THE WAY TO MAKE AN EXISTING APP HIGHLY AVAILABLE. If the user asks for high availability, redundancy, no single point of failure, surviving a host or VM failure, or 'stay up if a machine dies', this is the tool: point it at their running VM and pass high_availability:true. It needs no rebuild and no redeploy, and the URL does not change. Turns a single running instance into a horizontally-autoscaling cluster: snapshots the instance and puts your SOURCE VM behind a load balancer as its ALWAYS-ON BASELINE MEMBER, then an autoscaling group adds EXTRA members (booted from that snapshot) on CPU load and scales them back down to zero. FLAVOR — LEAD WITH A MEMORY-OPTIMIZED SMALL-DISK FLAVOR (m1.mem16/m1.mem32) for the cluster, and ideally have the SOURCE VM on one too: clustering snapshots the source VM's FULL disk, so DISK size (not RAM) drives how long the cluster takes to build and to add each member under load — a 40 GB mem flavor is several times faster to snapshot and scale than a 160 GB standard flavor (m1.xlarge) and costs less for the same RAM. If the source VM is on a big-disk flavor, RECOMMEND migrating the app onto a mem-flavor VM first (a root disk cannot be shrunk in place), even though it is extra work — it pays off on every scale-out, and a clustered app is stateless anyway (state in the managed DB) so the lean disk fits. Expect a DRASTICALLY better clustering experience on a mem flavor: far faster cluster-create, snapshots, and every scale-out. The user can override with any flavor. At rest ONLY your source VM serves — there is NO idle extra VM to pay for (the source VM is the cluster's minimum, so the floor is 0 extra members). Use it to LOAD-SCALE a stateless app tier while managed services hold state: it becomes highly-available UNDER LOAD (multiple members behind the LB), but at rest a SINGLE source VM serves — and that source VM is a plain VM, not an autoscaled member, so it is NOT auto-replaced if it fails while idle (only the autoscaled extra members are ASG-managed and self-healed). If you need always-on redundancy, keep the app under enough load to hold >=1 extra member, or use a separate always-on setup. BILLED — at rest it costs just your source VM (which you already run) plus the load balancer; under load it adds up to max_size EXTRA members at the member flavor (flavor_id), billed only while they run. In guided mode show the cost that way (now: source VM already running + the LB; under load: up to max_size x the member flavor) and get the user's explicit go first. redu automatically repoints the extra members from the old single-VM URL to the load-balancer URL across app config. It REFUSES a STATEFUL VM with 409 cluster_needs_stateless unless confirm_stateless:true. To have redu FIX a stateful VM for you instead of refusing, pass auto_restructure:true — for a single_vm Postgres it fully-automatically provisions a managed DB + migrates the data + repoints the members; for a compose-stack DB it provisions the matching managed DB (set restructure_engine, e.g. 'mysql'/'mariadb' for WordPress) and returns migration commands to run from the app VM. WordPress/WooCommerce is not generic autoscaling: managed DB alone is not enough because wp-content/uploads is file state. Use app_profile:'wordpress'/'woocommerce', cluster_media_mode:'media_space', and either media_space_id or create_media_space:true so all members mount the same uploads filesystem; otherwise the backend refuses with 409 cluster_needs_media_space. PUT THE CLUSTER ON THE SAME private network as the managed DB and media space. HA: cluster members are spread across DIFFERENT physical hosts automatically, and an autoscaled member that is destroyed is REBUILT AUTOMATICALLY in 1.5 to 5 minutes depending on how it failed with no action from you (the always-on source/hero VM is a plain VM and is NOT covered by that). CRITICAL for members: the app must start on EVERY boot (systemd unit or container restart policy) - if it only starts from a first-boot cloud-init script, a rebooted or resized member comes back with no app, silently never rejoins the load balancer, and the cluster quietly loses capacity with nothing reporting an error. Pass startup_command if the app does not already auto-start on boot, and have it bind its port only once it is genuinely ready to serve (the health check can only see whether the port is open). SEQUENCING - this catches people: the snapshot is taken IMMEDIATELY, and every member boots from it, so the source VM's app must already be RUNNING before you call this. Clustering a freshly-created VM whose cloud-init has not finished captures an image with no enabled service, and all members then come up ACTIVE while failing the load-balancer health check forever - a cluster that looks built and serves nothing. Verify the app answers on its port first (get_ssh_command, or just fetch the VM's URL). The snapshot upload can take several minutes; poll list_clusters until CREATE_COMPLETE.

  ConnectorNo auth

• 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_lendersA

  mtgmon Mortgage AnalyticsA

  Find HMDA lenders and resolve names to canonical lender keys. Call this before any other lender tool. Use for: turning a company name ('Rocket', 'UWM', 'Wells Fargo', 'PennyMac') into its canonical key, ranking lenders by origination volume, or listing lenders by charter type or headquarters state. Then pass a result's exact `name` (e.g. 'Rocket/Quicken') as `lender` to get_lender_profile, get_hmda_product_analytics, or get_servicer_analytics mode='transfers', or as lender_a / lender_b to compare_lenders. Legal names such as 'Rocket Mortgage, LLC' are not keys and return meta.available=false downstream. Returns data.results (at most `limit` rows of {name, leis, charter_type, hq_state, recent_year, recent_volume, total_loans, volume_rank, subsidiary_count}), data.matched_count, and data.total_count. recent_volume is USD originations in recent_year (the latest HMDA year). Keys are holding-company or originator groups, so subsidiaries and LEIs roll up into one key. Behavior: read-only, no auth or API key, no PII, idempotent and safe to retry. The public endpoint https://mtgmon.com/mcp allows about 60 requests/min and 250 tool calls/day per client IP. Result shape is {data, meta}; meta carries available, as_of, source_scope, weighting, units, cache_status, caveats, and truncated. If meta.available is false the data is unavailable or the cache is still warming (retry after a few seconds); never report it as zero.

  ConnectorNo auth

• find_footageA

  Valmera — agentic AI video editorA

  PROJECT-SCOPED: this call acts only on the explicit project_id and returns the project identity with its result. Find REAL footage of a NAMED topic on the web — the b-roll move: the speaker mentions Elon Musk, the cut shows his rocket. Query the concrete THING ('spacex starship launch', 'tesla factory'), not a mood — search_stock covers generic visuals ('busy city'), THIS covers named people, companies, products, events. Returns candidate links best-guess first; pick real footage of the subject (short clips), then fetch_url(url, as_kind='clip'), look_at_asset for the right seconds, and a cutaway or insert at the mention. Tell the user what footage you used (title + channel).

  ConnectorOAuth

• get_video_sampleA

  Go RocketA

  A short look at the style of your ad: a stored, blurred library montage. Open sample_page_url to see it in your brand colours when the page supplies them; the direct clip is untinted. Your real video is made after you start it. Returns a claim token. The bounded page check takes up to two seconds; the tool waits up to wait_seconds and otherwise returns state 'reading': then call get_sample_status with the claim token every few seconds until it is 'ready'. Nothing is generated or charged by this call.

  ConnectorNo auth

• delete_cronjobA

  turbopressA

  Löscht EINE geplante Aufgabe (Cronjob) einer Domain — der Weg zurück zu create_cronjob, etwa für eine falsch angelegte Aufgabe. Ändern kann dieses Werkzeug nichts: Dafür die alte Aufgabe löschen und mit create_cronjob eine neue anlegen. Die Kennung (cronjob_id) muss aus get_cronjobs stammen und wird serverseitig gegen die Aufgabenliste genau dieser Domain geprüft; eine geratene oder aus einer älteren Antwort übernommene Kennung wird abgewiesen, bevor irgendetwas gelöscht wird. Die Kennungen sind nicht stabil — vor dem Löschen get_cronjobs frisch abrufen und dem Kunden Befehl, Zeitplan und Beschreibung der Aufgabe nennen, die er löschen will, nicht nur die Zahl. Eine gelöschte Aufgabe lässt sich über dieses Werkzeug nicht wiederherstellen, nur neu anlegen; läuft an ihr etwas Wichtiges (wp-cron hält bei WordPress geplante Beiträge, Backups und Newsletter am Laufen), hört das sofort auf. Die Antwort sagt ausdrücklich, ob die Aufgabe nach dem Löschen wirklich aus der Liste verschwunden ist; ist die Liste danach nicht abrufbar, meldet sie das als ungeprüft statt als Erfolg.

  Connector

  Destructive

  OAuth

• create_videoA

  Go RocketA

  Start a finished 9:16 AI User Generated Content (UGC) video ad for a website: a photoreal presenter speaks about the product, captions included, in the site's brand colours. Spends credits from the signed-in Go Rocket account (15 s = 1 credit, 30 s = 2, 60 s = 4) including comp credits, and starts at once. Signed out, connect your existing account with sign_in, then retry in the same chat. Checkout is needed only when credits are insufficient. It can be cancelled with a full refund for 60 seconds. Returns a video_id right away; the video takes about 15 minutes, so poll get_video. Pass an idempotency_key when retrying so a repeated call returns the same video instead of paying twice. For a spoken business name without a URL, find its official website first and confirm the URL in one line before calling. Put the requested tone and audience in brief. Read back the returned message, then use status_tool to fetch the share_url when ready.

  ConnectorNo auth

• public-ipA

  PacketroveA

  Use to inspect the public IPv4 or IPv6 address observed for the connection making this MCP tool call. Takes an empty object and returns ip and family. This is the MCP client connection: a hosted AI client may observe its own exit address, not the user device address. If the user needs their browser or computer connection, direct them to the web tool or a CLI running on that machine. A VPN or proxy changes the observed path. One call observes one address family; it does not discover private local addresses, an address before a proxy, or both address families. The application does not store or log results, and no firewall rules are changed. Cloudflare Worker subrequests can have platform-specific address semantics; the result is not an identity proof. Operational events record the tool name, success or error, a controlled error code, and a traffic source classification. Verified automated checks may also record an automation run identifier. Events exclude inputs, results, raw request headers, and automation tokens. Cloudflare may attach platform metadata. Privacy policy: https://packetrove.com/privacy.

  ConnectorNo auth

• connect_wordpressA

  XeoRankB

  Connect a WordPress site to XeoRank. Just pass the domain (https:// and www are stripped for you). Returns `onboard_url` — PRESENT THAT TO THE USER AS A CLICKABLE LINK and stop there. That one page walks them through installing the connector plugin, opens their wp-admin, and completes the connection automatically — there is NO Application Password to copy and NO follow-up tool call needed. Poll list_wordpress_sites (or verify_wordpress) to confirm it flipped to verified. Pass transport='ssh' only as a Hostinger fallback.

  ConnectorOAuth

• publish_content_briefA

  XeoRankB

  Create a WordPress DRAFT from the brief's markdown (Gutenberg blocks; never live). Uses the brand's verified WordPress connection — the caller's own or a teammate's under the org model — and the normal WordPress write gates. Use dry_run=true first to show the user the title, post type, a block preview and any writing blockers (would_refuse). The user reviews and publishes from wp-admin. WRITING BLOCKERS (placeholders, figures or superlatives with no source) refuse the publish. You cannot waive them: fix them (suggest_sources + accept_source for sources, assist_writing_fix for wording), or give the user the dashboard_url from the error — only a person can choose 'Publish anyway', with a reason, in the XeoRank dashboard. For non-WordPress platforms, hand the user the markdown from get_content_brief, then record the live URL with update_content_brief(published_url=...).

  ConnectorOAuth