"Kit" matching MCP tools:

• x402-startup-kitC

  minia2a-mcpD

  Startup Kit: Startup toolkit — validation, planning, and research.

  ConnectorNo auth

• request_invoiceA

  agent-ready-kitA

  Use this to autonomously close a deal: issue a ONE-TIME Stripe Invoice for the flat $450 package price (one-and-done — no recurring). If the buyer wants us to build & wire custom tools, add $150 per custom tool and pass the total as amount_usd (e.g. $600 for one). **Amount:** with no `quote_id`/`amount_usd` it bills the flat **$450** package. Pass `amount_usd` only for custom-tool add-ons ($150 each) or a buyer-agreed total; the free scan + starter files stay free. **Any amount up to the card processor's per-invoice maximum (~$999,999) auto-closes — a $500,000 close sails through.** Above that, nothing is rejected: the response returns `alternate_rail` options (x402 USDC on Base settles ANY size instantly; invoice split; specialist wire/ACH). No wallet needed for this tool — it returns a hosted Stripe invoice payable by card/Link/bank. Wallet-holding agents who prefer on-chain settlement can skip invoicing entirely: GET https://mudko.com/api/x402/purchase (x402 v2, USDC on Base). **Only `email` (and `domain`) are required.** Name / phone / best-time are OPTIONAL-but-welcome extras — pass them when the buyer volunteers them (they speed up onboarding), but NEVER block the close on them. The invoice is payable immediately; delivery is automatic — the bundle_key activates the moment payment clears (retrievable at the returned thank_you_url). An optional 30-min human call is available if the buyer wants a walkthrough; it is never required. Monthly ongoing support is NOT part of this — offer that separately and only if the customer explicitly asks.

  ConnectorNo auth

• lookup_tariffA

  DAITK (Dibblee AI Tool Kit) - Total Import CostA

  Look up base Canadian duty rates for an HS/tariff number (e.g. '0101.21.00.00'), plus any tracked surtax/trade-measure orders whose HS coverage might overlap it. as_of defaults to today (YYYY-MM-DD). This returns EVERY treatment code on the tariff item, most of which do not apply to any one shipment — use resolve_duty with a country of origin to get the one that actually applies to a specific import. Some rows carry treatment_label: null; a null is a gap in this service's own data, not a signal about what the treatment is — check unlabeled_treatment_codes and never call one an FTA or infer its identity yourself.

  ConnectorNo auth

• start_checkoutA

  agent-ready-kitA

  Use this when an end user wants to buy the package now. Issues a REAL payable path: the same one-off hosted Stripe invoice request_invoice produces, billed at the flat $450 package price. The invoice is payable immediately and delivery is automatic — the bundle_key activates the moment payment clears (retrievable at thank_you_url). To add custom tools ($150 each), use request_invoice with an explicit amount_usd instead. consult_url is an OPTIONAL extra for buyers who want a human walkthrough — never required. For Free tier downloads, call generate_files instead.

  ConnectorNo auth

• submit_leadA

  agent-ready-kitA

  Use this when the user has indicated interest in being followed up with — even before formal checkout. Capture is non-binding. **REQUIRED CONTACT FIELDS**: contact_name, contact_phone, best_consult_time. Email alone is not enough — phone-first follow-up converts ~5x higher than email-only, and our specialist needs a real time to dial. ASK FOR ALL THREE explicitly. **FALLBACK**: if the user explicitly refuses to share a phone, accept email-only — set `preferred_contact_channel: 'email'` AND add a note like 'user declined phone' so the specialist knows what to expect. Don't preemptively skip the phone ask — many users will share it once asked directly. **Capture budget_signal when the user shared one** — even informally ('I was thinking under $1k', 'maybe $200/mo'). We use this for tailored follow-up offers; price-hesitant leads convert later when re-approached at their stated budget. Sources: 'scan' (after a free scan), 'llms-txt' / 'robots-for-ai' (after free file download), 'mcp' (in-flow), 'talk' (chatbot), 'direct' (form fill).

  ConnectorNo auth

• list_kitsA

  Moltline Catalog — 138 Agent Skills & PersonasA

  List the 12 themed kits with pricing and member products. FREE. Takes no arguments. Returns a list of kit objects, each {"slug": ..., "name": ..., "price_usd": N, "tagline": ..., "members": ["product-slug", ...], "availability": ...}. Use a kit's slug with get_full_kit (premium). Kits are not sold standalone on any marketplace: price_usd is the bundle's reference value, and All-Access is how a caller actually unlocks one. Use when the caller asks about bundles or bundle pricing. Not for individual products (search_catalog) and not for a kit's full contents (get_full_kit). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

  ConnectorNo auth

• list_kitsA

  Moltline StudioA

  List the 12 themed kits with pricing and member products. FREE. Takes no arguments. Returns a list of kit objects, each {"slug": ..., "name": ..., "price_usd": N, "tagline": ..., "members": ["product-slug", ...], "availability": ...}. Use a kit's slug with get_full_kit (premium). Kits are not sold standalone on any marketplace: price_usd is the bundle's reference value, and All-Access is how a caller actually unlocks one. Use when the caller asks about bundles or bundle pricing. Not for individual products (search_catalog) and not for a kit's full contents (get_full_kit). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

  ConnectorNo auth

• get_full_kitA

  Moltline StudioA

  Load a themed kit and every member product in full. PREMIUM (paid plan). Typical input {"slug": "founder-kit"} returns {"slug": ..., "name": ..., "products": [{"slug": ..., "name": ..., "persona": ..., "skills": [...]}, ...]}. Returns every member product of one bundle in full, so the payload is large. Use only after list_kits has confirmed the kit slug. Not for a single product (get_full_product). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "unknown kit '<value>'"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

  ConnectorNo auth

• hip_prepare_paymentA

  Have It PrintedA

  Resolve the EXACT amount HIP will charge, before any payment authorization is obtained or spent. This does NOT charge anything. Returns subtotal_cents, tax_cents, total_cents, currency, a pricing fingerprint and the authorization types HIP accepts. Tax is calculated by Stripe from the destination, so hip_quote alone is not the payable amount. The returned total is bound to this job's documents, options and recipient: change any of them and payment is refused with QUOTE_STALE until you prepare again. Use this when paying autonomously with a delegated payment authorization; a human paying in a browser does not need it. Commits the job to the autonomous payment rail.

  ConnectorNo auth

• hip_complete_paymentA

  Have It PrintedA

  Pay for the job with a delegated payment authorization, with no browser and no human step. payment_authorization must be a Stripe shared payment token (spt_...) granted to Have It Printed whose maximum is at least the total from hip_prepare_payment; HIP charges exactly that total and never more. NEVER send a card number, expiry, CVV or any reusable credential to this tool. If the cardholder's bank requires authentication, this returns payment_status=requires_user_action rather than bypassing it.

  ConnectorNo auth

• niche_brand_profile_setA

  Niche — Editorial IntelligenceA

  Set or update the persisted brand profile for a brand. The profile is a structured JSON document applied across every pipeline stage: voice rules, banned terms, canonical vocabulary, framing allowlist, channel config, compliance disclosures, and verifier overrides. Use it to persist a profile derived from a repo or docs so future runs inherit the rules, or to update voice rules and banned terms before the next run. Required sections: `identity` and `voice` (a profile with no voice falls back to generic drafts). A re-set that omits voice is accepted with a default voice stub rather than rejected. Validation: tiered lints (error / warn / info). 'error' lints reject the set; 'warn' lints accept with a note. The response includes `lints[]`. `conflicts[]` lists fields locked by the brand kit, which takes precedence; those profile values are not stored. brand_id is unique per user; re-setting the same brand_id replaces the prior profile.

  ConnectorNo auth

• niche_brand_kit_ingestA

  Niche — Editorial IntelligenceA

  Auto-populate the user's BrandKit (palette / fonts / tagline / logo / wordmark / boilerplate / voice notes) from files, a URL, or pasted text. Additive by default: fills empty fields, leaves populated ones alone. Idempotent: re-running the same inputs doesn't double-write. Overwrite rule: if the target brand kit already has an identity (a tagline/boilerplate/voice for a different brand), do not silently overwrite it. First ask the user whether to replace it. If the account supports multiple brand profiles, prefer creating a separate brand instead: pass a new `brand_id` slug plus `brand_name` rather than clobbering the existing one. Only pass `replace=true` once the user has confirmed they want this brand re-learned from the new source. Use when the agent has brand assets in scope (a working directory with logos / press-kit / brand-guide PDFs, the user's portfolio or Substack URL, pasted boilerplate copy) and wants to populate Niche's BrandKit so future signal_scan and content generation inherit the brand context. Agent-side equivalent of the Niche web app brand-kit ingest surface, same backend engine. Async, then poll: a URL or multi-file ingest runs in the background, so this call returns fast with {ingest_id, status:'ingesting'}. Then poll niche_brand_kit_ingest_status(ingest_id) until status is 'done'; that response carries the populated BrandKit, the ingest report (detected[] / skipped[] / errors[]), and a diff[] of changed fields. (Loop: ingest, then poll status until done/failed; same pattern as niche_signal_scan to niche_session_state.) Do not re-call ingest while one is running; a duplicate of the same inputs attaches to the in-flight job. URL ingest also fills voice primitives when the page has post-shaped text (Substack/blog/X). If a URL is slow or thin to scrape, the visual fields may land before the voice pass completes; when the report flags this, paste the page's About/homepage copy via `text=` to complete the brand voice.

  ConnectorNo auth

• niche_brand_kit_updateA

  Niche — Editorial IntelligenceA

  Set specific BrandKit fields by name. The write path for the structured fields (tagline / boilerplate / voice_notes / forbidden_phrases / signature_phrases / endcard preferences / video voice preference / colors / fonts) without going through the ingest engine. Use after niche_brand_kit_ingest fills the easy stuff, or to commit values the user answered through niche_brand_kit_guided_setup. Only fields you pass are touched; fields you omit stay at their current value. Lists replace the current value (they do not append). Response includes a diff[] of fields that changed and the full updated kit. Archiving: pass archive=true to archive a brand (soft and reversible; it disappears from every list but is not deleted), or archive=false to restore one. The default/active brand can't be archived (promote another to default first). A brand with published history won't archive unless you also pass acknowledge=true. Use archive_scope='test' to archive every scratch brand at once (never the default). There is no hard delete here; archive is the removal verb agents have.

  ConnectorNo auth

• deep_researchA

  Istat ItA

  ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources (SEC filings, FRED/BLS economics, FDA, USPTO patents, markets, science, government records, etc.) in ONE call — this is NOT open-web search. Decomposes your question into focused facets, routes each to the right one of 5,798 tools IN PARALLEL, and returns a findings packet: verbatim evidence + confidence + source + fetched_at + a stable pipeworx:// citation per finding, with explicit gaps[] for facets the data couldn't answer (never invented). Best for broad/multi-part questions over structured data ("compare X and Y's regulatory + financial exposure", "research the filings + market picture for ACME"). For a single lookup use ask_pipeworx (one LLM call, not many). For BREAKING or colloquial CURRENT-NEWS / "what's the world saying about X" topics, prefer ask_pipeworx — it routes to live news APIs and the *-news-feeds packs; deep_research returns mostly empty gaps[] when the topic isn't in the structured catalog. Second-hop iteration: depth:"standard" re-angles unanswered gaps (gap recovery); depth:"thorough" additionally chases the best leads from the first pass — so multi-step questions resolve in one call. Every finding carries a `hop` field and a citation_uri — a resolvable pipeworx:// record URI, present only when the source emits one that resources/read can actually serve, so a citation you get back is always fetchable. "standard" and "thorough" also return contradictions[] flagging findings that disagree. Large records are semantically excerpted to the passages relevant to each facet (not head-truncated), so answers deep in a long filing/series aren't missed. Expect 15-60s (thorough with its follow-up + contradiction pass: up to ~90s).

  ConnectorNo auth

• deep_researchA

  Dati ItA

  ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources (SEC filings, FRED/BLS economics, FDA, USPTO patents, markets, science, government records, etc.) in ONE call — this is NOT open-web search. Decomposes your question into focused facets, routes each to the right one of 5,798 tools IN PARALLEL, and returns a findings packet: verbatim evidence + confidence + source + fetched_at + a stable pipeworx:// citation per finding, with explicit gaps[] for facets the data couldn't answer (never invented). Best for broad/multi-part questions over structured data ("compare X and Y's regulatory + financial exposure", "research the filings + market picture for ACME"). For a single lookup use ask_pipeworx (one LLM call, not many). For BREAKING or colloquial CURRENT-NEWS / "what's the world saying about X" topics, prefer ask_pipeworx — it routes to live news APIs and the *-news-feeds packs; deep_research returns mostly empty gaps[] when the topic isn't in the structured catalog. Second-hop iteration: depth:"standard" re-angles unanswered gaps (gap recovery); depth:"thorough" additionally chases the best leads from the first pass — so multi-step questions resolve in one call. Every finding carries a `hop` field and a citation_uri — a resolvable pipeworx:// record URI, present only when the source emits one that resources/read can actually serve, so a citation you get back is always fetchable. "standard" and "thorough" also return contradictions[] flagging findings that disagree. Large records are semantically excerpted to the passages relevant to each facet (not head-truncated), so answers deep in a long filing/series aren't missed. Expect 15-60s (thorough with its follow-up + contradiction pass: up to ~90s).

  ConnectorNo auth

• get_full_kitA

  Moltline Catalog — 138 Agent Skills & PersonasA

  Load a themed kit and every member product in full. PREMIUM (paid plan). Typical input {"slug": "founder-kit"} returns {"slug": ..., "name": ..., "products": [{"slug": ..., "name": ..., "persona": ..., "skills": [...]}, ...]}. Returns every member product of one bundle in full, so the payload is large. Use only after list_kits has confirmed the kit slug. Not for a single product (get_full_product). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "unknown kit '<value>'"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

  ConnectorNo auth

• recommend_travel_gearA

  VoyageHacksA

  Turn a trip description into a packing and gear kit drawn from the VoyageHacks travel gear catalog: one product per category, each with the published reason it was picked, its Amazon ASIN, a link to the Amazon product page and the guide that reviews it. Takes a plain-language trip summary ("10 days in Japan in October, carry-on only, long-haul red-eye, working remotely") plus optional structured hints (destination, trip length in days, season, activities, luggage constraint, traveler type, budget), all of which are used to weight which categories make the kit. Answers questions of the form "what should I pack for X", "what gear do I need for Y" and "I only have carry-on, what should I bring". It draws on the VoyageHacks editorial catalog, not a search of all of Amazon, and returns published picks only: prices, star ratings, review counts and stock are not available and are never returned, and it produces no clothing sizes and no itinerary. For one named product category, search_travel_gear is narrower. The Amazon links are affiliate links: VoyageHacks may earn a commission from qualifying purchases at no additional cost to the buyer, which should be disclosed when the links are presented.

  ConnectorNo auth

• list_payable_apisA

  agent-ready-kitA

  Use this when someone asks what they can buy per-call, asks the price of a specific API (site audit, AI-citation check, counterparty trust verification, bulk/batch scanning, Bazaar listing or keepalive), or is an agent looking for something cheaper than a full engagement. These are pay-per-call x402 endpoints: no signup, no bundle_key, no engagement — the caller pays USDC on Base and gets the response body back in the same request. Every price here is live from our catalog. IMPORTANT: paying these requires an x402 v2 client with a funded Base wallet, so they suit AGENTS; a human with only a card should be pointed at the flat $450 package instead (the audit and citation intelligence are included in it). The free diagnosis at /api/x402/deep-scan needs no payment at all.

  ConnectorNo auth

• search_toolsA

  Crank ProtocolB

  Keyword search over the full Crank tool catalog (progressive disclosure). Read-only, free, never gated. Purpose-built for a discovering agent that does not want to load the full tool catalogue into context just to find the one it needs ( R1 -- the Solana Agent Kit V1 failure mode: 60+ tools in context caused tool-selection hallucinations). Pass a keyword or short phrase (e.g. "perp funding rate", "stake sol", "referral"); matches rank by keyword overlap against each tool's name + description. Returns up to ``limit`` (default 10, max 50) results, each ``{name, purpose, toolset}`` -- ``purpose`` is a one-line summary (call the tool itself, or get_trading_workflow, for the full picture), and ``toolset`` names which of the ten named toolsets (market_data, spot, perps, lending_staking, portfolio, strategies, intelligence, rewards_growth, wallet_admin, support) the tool belongs to. No tool is renamed or hidden by this search -- it is purely a discovery aid.

  ConnectorNo auth

• get_role_soundA

  soundsA

  Use this FIRST whenever the user asks to add a sound for a specific event or interaction — a button click, purchase success, error beep, level-up, dialogue blip, rain loop. Pass the role as plain words: role ids (click, success, purchase-success, dialogue-blip, rain-loop…) and common aliases (button click, ka-ching, jump scare, text blip…) are all accepted. Returns the library's default sound for that role — the most typical variant of the matching family, chosen by measured acoustics — with hotlinkable MP3/WAV URLs, 2-3 alternates and the family page for browsing more. Optional style: crisp (short, bright, dry), soft (darker, gentler), spacious (reverb, longer tail), balanced (default: most typical). Roles marked loopable return seamless loops (use the WAV for gapless playback). For a whole coherent kit use get_sound_set; fall back to search_sounds only for free-text descriptions that do not name an event. Unknown roles return not_found with the full role list; GET https://sfxmint.com/api/v1/roles lists roles with aliases.

  ConnectorNo auth

• request_datasheet_uploadA

  sheetsdata-mcpA

  Request a signed URL to upload a datasheet PDF for a component whose datasheet we don't have. Use this when search_parts / get_part_details / prefetch_datasheets return datasheet_status='no_source' (and a retry didn't help) or 'unsupported'. Free — the upload fee is only charged on confirm_datasheet_upload after we validate the file. Flow (3 steps): 1. Call request_datasheet_upload with the MPN, the file's SHA-256, and its byte size. You get back an upload_url, upload_method ('PUT'), upload_headers, and an opaque upload_token. 2. Upload the PDF directly to the returned URL with curl: `curl -X PUT -H 'Content-Type: application/pdf' --data-binary @file.pdf "$UPLOAD_URL"` (add any headers from upload_headers). 3. Call confirm_datasheet_upload with the upload_token. Server verifies the bytes, re-hashes, checks for the MPN on the first page, charges the upload fee (50¢), and queues extraction. Returns document_id + status='pending'. Validation rules (checked at confirm time, refunded on failure): - File must be a valid PDF (magic bytes + parseable). - Actual SHA-256 must match expected_sha256. - Actual byte size must match size_bytes (±0). - MPN or its core stem must appear in the first page text (catches wrong-file uploads). Scanned image-only PDFs will fail this check — upload a text-based PDF. - Max 50MB per file. No dev-kit manuals / BOB schematics / app-notes as datasheets — use the matching MPN's actual datasheet. Uploaded datasheets are scoped to your organization (private). They satisfy read_datasheet, search_datasheets, check_design_fit, and analyze_image for your org's tokens only. Tokens expire after 15 minutes. If upload fails or times out, just call request_datasheet_upload again.

  ConnectorNo auth