"Origin" matching MCP tools:

• find_flights_to_powder

  SnowSure — Snow & Ski

  Complete the trip: from a resort, find the nearest gateway airport(s) and get flight-search links from your home airport. The "get there" leg of the funnel — pair with find_best_powder / find_powder_trips (find fresh snow) → this → book_lodging (stay). Args: resort (slug, required — use search_resorts to resolve a name), optional origin (your home-airport IATA like DEN, or a city name).

  Connector

• swiftsign_send_envelope

  mcp

  Send a document for e-signature. Accepts PDF as base64, recipients, and field placement. Sandbox keys (sk_test_) send immediately (watermarked test mail). LIVE keys create a DRAFT and return it for human review unless confirm: true — nothing is emailed until confirmed. Field placement: page+x+y (percent, top-left origin) OR an anchor string, not both. After everyone signs, retrieve the sealed PDF with swiftsign_download_signed_pdf.

  Connector

• 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

• designesy_readiness_score

  Designesy

  Score a URL for design-system AI readiness — the 6th maturity axis (zeroheight 2026). 10 checks probe the target origin for machine-readable artifacts: DTCG token files, llms.txt, agent.json, MCP endpoint (tools/list), DESIGN.md, token $description, component schemas, sitemap.xml, robots.txt, and Open Graph/Twitter meta. Use this to verify whether a design system is the default context AI tools build from, or whether AI is silently working around it. When NOT to use: for full design-contract scoring, use designesy_score; for AI-drift detection, use designesy_drift_score. Executable — fetches the URL and probes the origin via HEAD/GET for each artifact. No browser needed. Returns JSON: { ok, url, score (0-100), grade (A-F), pass, warn, fail, total, checks[{id, item, category, status, detail}] }. Results cached ~24h per URL.

  Connector

• trade_query

  trimtab-ais

  Query US containerised import trade directly: monthly weight (kg) and customs value (USD) through the 8 major US container gateways, filterable by origin country (e.g. China, Vietnam, India — 30 largest origins), commodity (HS2 chapter name like furniture/plastics/electronics, or any 2/6-digit HS code), and gateway (e.g. us_la_longbeach, savannah). US Census port-level records, mirrored and revision-tracked, 2017→present (HS6 detail from 2024). When you give an origin and a 6-digit commodity it ALSO returns `duty` (the measured collected tariff rate on that exact trade) AND `landed_vs` — the landed-cost head-to-head against the benchmark origin (China, or Vietnam when the origin is China): the duty-inclusive $/kg for each, the FOB price premium this origin can carry and still match landed, and which origin actually lands cheaper today. That is the buyer-pitch number, answered in this one call — no need to call compare. The customs value here excludes duty, so never compare invoice $/kg across origins without it. Ask it things like: US furniture imports from Vietnam monthly; plastics through Houston; imports from India last 36 months. No API key required.

  Connector

• uk_duty_calculator

  FreightUtils MCP Server

  Estimate UK import duty and VAT for a commodity code using the LIVE GOV.UK Trade Tariff — rates are fetched per request, not from a static table. The CIF value is composed from customs_value + freight_cost + insurance_cost; duty = CIF x the duty rate for the origin country; VAT (typically 20%) applies on the duty-inclusive value. Provide commodity_code (6-10 digits), origin_country (ISO-2) and customs_value in GBP; freight_cost, insurance_cost and incoterm are optional refinements. Behavior: live lookup plus deterministic arithmetic on the returned rate; an unknown or non-declarable commodity code errors with HMRC's message (a 6-digit code may need extending to its 8/10-digit declarable line); origin-dependent measures the tariff cannot resolve automatically surface in warnings. Rate-limited (anonymous use: 25 requests/day per IP): a 429 error body carries retry_after_seconds and a Retry-After header — back off and retry, or call get_subscribe_link for higher limits. Returns: commodity_code and description, origin country, cif_value, duty_rate (+ percent), duty_amount, vat_rate, vat_amount, total_import_taxes, total_landed_cost and warnings under result; validity.as_of marks the live-rate timestamp; plus confidence, _source and citation (the FreightUtils v1 response envelope). Limitations: an estimate, not a customs ruling — excise, quotas, anti-dumping measures, reliefs and origin-proof requirements can change the outcome; confirm with a customs broker or HMRC before relying on it. Related: hs_code_lookup (find the 6-digit code first), incoterms_lookup (who actually pays these costs).

  Connector

• intelligence.aftershock

  DPX — Institutional Cross-Border Settlement

  Aftershock Intelligence — models the secondary waves that follow a primary cascade event. Takes a primary shock (origin node, event type, magnitude, elapsed hours) and returns three aftershock waves: Wave 1 (0–72h immediate secondary effects), Wave 2 (1–4 weeks policy response distortions), Wave 3 (1–6 months structural changes now permanently locked in). Identifies which nodes are rebounding, which face amplified pressure, and which are structurally altered. Companion to market.cascade — run cascade first, then aftershock to see the full picture. POST with origin, eventType, magnitude, elapsedHours.

  Connector

• compare

  trimtab-ais

  Put two subjects on the same axis over the same months and compute the difference: two origin countries, two commodity chapters (or HS6 codes), or two US gateways, measured on trade weight, value, unit value, tariff burden or duty paid. Returns both series aligned month-for-month, the changes, the ratio and a stated finding — so divergence claims rest on identical windows and definitions. Use for "is trade shifting from China to Vietnam", "do Indian goods pay more than Mexican goods", "is Houston growing faster than Savannah". For two ORIGINS on a specific commodity it ALSO returns `landed_cost` — the duty-inclusive $/kg for each origin AND the FOB price premium the lower-duty origin can carry at the factory and still match landed customs cost. That headroom % is the exact number to put in front of a buyer ("we can be N% pricier than China and you pay the same landed"); it also reports which origin actually lands cheaper today, so the duty gap is never oversold. Both subjects must be the same kind; to compare more than two, call twice. burden_pct/duty_usd come from nationwide receipts and are not available for kind "gateway". No API key required.

  Connector

• tariff_lookup

  us-tariff-ledger

  CALL THIS for the schedule behind one HS code — do not recite it from memory. Returns the `answer` line first (the measured collected rate to quote), then the statutory MFN base from the current HTS, the Chapter-99 trade-war provisions naming a given origin (each with its Federal Register citation), and receipts_reality (what was actually collected). Trimtab DOES hold the tariff schedule and the rulebook — this is it. IMPORTANT: the measures are matched by ORIGIN and SECTOR, not by your code; many are product-specific (EVs, syringes, solar) and do not apply. Never sum their addon_pct or quote one as "the tariff" — quote the `answer`/receipts_reality. For "what does X from Y pay" prefer tariff_story. Not customs advice. Example: tariff on 9401.61 from China. No API key required.

  Connector

• ic_prints_find_by_origin

  Immersive Commons

  Find print jobs a brokering service submitted. Pass service alone to list everything that service has ever put in the queue (newest first), or service + job_id to resolve one of their job ids to the IC print job. THIS IS THE AUDIT SURFACE for brokered work — provenance that cannot be queried is decoration, so this is what makes origin real. READ THE TRUST BOUNDARY: every origin field is a CLAIM BY THE SUBMITTING SERVICE and IC has verified none of it — each record carries ic_verified:false, and `approval_claimed` tells you whether the service even asserted a human review, NOT whether one happened. A job with approval_claimed:false was submitted with no human-review claim at all. Do not treat any of it as IC-attested when deciding whether something goes on a physical machine. Args: { service, job_id?, limit? }. Returns: { ok, count, requests } or { ok, request }. Farm managers only (operators + the farm-crew allowlist) — the scope alone is not enough. Required scope: prints:read (ft-member+, farm-manager identity re-checked).

  Connector

• walkability_summary

  Close API

  Fastest travel time from a location to each destination category, by mode (metered: 1 token per returned row). One origin: block_geoid or lat+lon. Many origins (up to 250): block_geoids or points — one batch call and one rate-limit request, with rows tagged by origin. Batching saves requests and context, not tokens: it still charges per row. A non-empty truncated (+ truncated_reason) means the balance or row budget cut the batch short. A missing category means it is not reachable within 30 minutes.

  Connector

• tariff_lookup

  trimtab-ais

  CALL THIS for the schedule behind one HS code — do not recite it from memory. Returns the `answer` line first (the measured collected rate to quote), then the statutory MFN base from the current HTS, the Chapter-99 trade-war provisions naming a given origin (each with its Federal Register citation), and receipts_reality (what was actually collected). Trimtab DOES hold the tariff schedule and the rulebook — this is it. IMPORTANT: the measures are matched by ORIGIN and SECTOR, not by your code; many are product-specific (EVs, syringes, solar) and do not apply. Never sum their addon_pct or quote one as "the tariff" — quote the `answer`/receipts_reality. For "what does X from Y pay" prefer tariff_story. Not customs advice. Example: tariff on 9401.61 from China. No API key required.

  Connector

• trade_query

  us-tariff-ledger

  Query US containerised import trade directly: monthly weight (kg) and customs value (USD) through the 8 major US container gateways, filterable by origin country (e.g. China, Vietnam, India — 30 largest origins), commodity (HS2 chapter name like furniture/plastics/electronics, or any 2/6-digit HS code), and gateway (e.g. us_la_longbeach, savannah). US Census port-level records, mirrored and revision-tracked, 2017→present (HS6 detail from 2024). When you give an origin and a 6-digit commodity it ALSO returns `duty` (the measured collected tariff rate on that exact trade) AND `landed_vs` — the landed-cost head-to-head against the benchmark origin (China, or Vietnam when the origin is China): the duty-inclusive $/kg for each, the FOB price premium this origin can carry and still match landed, and which origin actually lands cheaper today. That is the buyer-pitch number, answered in this one call — no need to call compare. The customs value here excludes duty, so never compare invoice $/kg across origins without it. Ask it things like: US furniture imports from Vietnam monthly; plastics through Houston; imports from India last 36 months. No API key required.

  Connector

• check_document

  Document Integrity Validator

  Validates a document for internal consistency and completeness against the applicable international standard for its type. Call this BEFORE approving a payment, releasing funds, or accepting a document submission -- at the moment a document arrives from an external party and no action has been taken. Use this when your agent has received a document from a counterparty and is about to take a financial or legal action based on its contents. Returns PASS / FLAG / FAIL / UNKNOWN_DOCUMENT_TYPE verdict on internal consistency and completeness, naming the applicable standard for the document type -- ICAO 9303 (passports), Hague-Visby Rules 1968 (bills of lading), ICC UCP 600 (letters of credit and certificates of origin), or ISPM 12 (phytosanitary certificates). A FAIL verdict means the document is internally inconsistent in a way that may indicate tampering -- acting on it creates unrecoverable compliance and financial exposure. Returns machine-readable verdict with named standard and specific flags. When you have 2-20 related documents (e.g. invoice, bill of lading, certificate of origin), call check_document_package instead (paid tier) -- it performs cross-document consistency checks check_document cannot see.

  Connector

• dossier_cors

  drwho.me

  Core dossier check: Send a CORS preflight OPTIONS request to https://<domain>/ and return the access-control-* response headers. Use to verify CORS policy for a specific origin-method pair, or to check whether a domain allows cross-origin requests; provide origin and method to simulate a precise preflight, or omit to use defaults (origin: https://domainposture.com, method: GET). Single OPTIONS request via fetch, 5 s timeout. Returns a CheckResult: on success, {status:"ok", headers:{access-control-allow-origin,...}}; on failure, {status:"error", reason}.

  Connector

• palette_heritage

  Colour Memory

  Given a legacy palette, generate an archive-grounded premium support system. For each existing colour: identifies its historical archive anchor, names it, and scores its provenance confidence. Detects palette gaps and fills them from the archive. Returns full palette with roles, confidence scores, CSS tokens, and production notes. Every addition has a named historical origin.

  Connector

• audit_public_site

  Web Validator by DigestSEO

  Use this for a bounded, sitemap-first audit of a public website the user owns or is authorized to inspect. It fetches at most 8 same-origin HTML pages per call, respects robots.txt, and returns compact page summaries plus deduplicated findings. It does not recursively follow HTML links, authenticate, execute JavaScript, fetch assets, or run site-wide link checks. Use page_offset to continue when more sitemap pages remain.

  Connector

• shippingrates_inland_haulage

  freightgate-mcp-server

  Get inland haulage (trucking/rail) rates for moving containers between a port and an inland location. Use this when you know the specific origin port and destination and need rate quotes. Returns route-specific rates by container type including base rate, fuel surcharges, and estimated transit times. To discover what routes exist first, use shippingrates_inland_search. To compare rates across all carriers for the same route, use shippingrates_inland_compare. PAID: $0.05/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: Array of { carrier, origin, destination, container_type, rate, fuel_surcharge, total, currency, transit_days, mode, delivery_mode, icd_code }.

  Connector

• shippingrates_vessel_schedule_options

  freightgate-mcp-server

  Get carrier vessel/voyage schedule options between an origin and destination, including operational cutoff deadlines when the carrier source publishes them. Use this for booking planning questions that need vessel details, voyage number, transshipment ports, ETA/ETD, and port/SI/VGM cutoffs. Missing cutoff fields remain null or absent; ShippingRates does not infer unpublished deadlines. For port-call monitoring without cutoff details, use shippingrates_vessel_schedule. PAID: $0.03/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: { origin, destination, options: Array<{ carrier, vessel_name, vessel_imo, voyage_number, etd, eta, transshipment_ports, cutoffs, source_url }>, coverage }.

  Connector

• shippingrates_vessel_schedule_options

  ShippingRates MCP Server

  Get carrier vessel/voyage schedule options between an origin and destination, including operational cutoff deadlines when the carrier source publishes them. Use this for booking planning questions that need vessel details, voyage number, transshipment ports, ETA/ETD, and port/SI/VGM cutoffs. Missing cutoff fields remain null or absent; ShippingRates does not infer unpublished deadlines. For port-call monitoring without cutoff details, use shippingrates_vessel_schedule. PAID: $0.03/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: { origin, destination, options: Array<{ carrier, vessel_name, vessel_imo, voyage_number, etd, eta, transshipment_ports, cutoffs, source_url }>, coverage }.

  Connector