"A platform for designing and prototyping user interfaces and experiences" matching MCP tools:

• check_dkim_selectorA

  dns-doctorA

  Use this when the user asks whether DKIM is set up for a sending platform, whether a specific selector exists, or why DKIM fails. Check ONE specific DKIM selector on a domain — the exact selector the sending platform uses (e.g. `google`, `s1`), which a full scan's common-selector sweep may miss. Returns the verdict, its explanation, and the published key record when one resolves. No fix record is returned: a DKIM key is generated by the sending platform, so the fix is always to publish what that platform gives the owner.

  ConnectorNo auth

• connect_domainA

  LayeroA

  Connect a custom domain to a site. IMPORTANT: between this call and a working domain stands A PERSON. You get DNS records — show them to the user and explain they go in at their domain registrar. Do not wait for readiness: DNS propagates in minutes to an hour, the platform re-checks on its own, and you check later via `check_domain`. Spinning here burns time and context for nothing. The address can be passed as-is: the platform reduces `https://shop.example.com/page` to `shop.example.com` itself.

  ConnectorOAuth

• connect_domainA

  LayeroA

  Connect a custom domain to a site. IMPORTANT: between this call and a working domain stands A PERSON. You get DNS records — show them to the user and explain they go in at their domain registrar. Do not wait for readiness: DNS propagates in minutes to an hour, the platform re-checks on its own, and you check later via `check_domain`. Spinning here burns time and context for nothing. The address can be passed as-is: the platform reduces `https://shop.example.com/page` to `shop.example.com` itself.

  ConnectorAPI key

• ratchet_get_policyA

  ratchetA

  Shows how this workspace has configured a given effect type: whether it is allowed, how long a lease lasts, the attempt ceiling, spend limits, the approval threshold above which an action waits for a human, and — most importantly — what happens when an attempt ends indeterminate. Check this before designing a retry strategy.

  ConnectorNo auth

• get_family_dayA

  tickadoo Experiences and EventsA

  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

• lookup_profilesA

  InflushipA

  Batch-fetch up to 100 profiles by (platform, username) pairs. Use this when the user has a list of handles and you need profile data for all of them at once (e.g., "give me follower counts for these 30 accounts I'm considering" or "which of @a @b @c are real accounts?"). One round-trip beats 30 calls to `get_profile`. Use this for exact batch handle lookup, not semantic discovery. For one exact platform+username pair, use `get_profile`. For partial or fuzzy handle/name input, use `search_creators` or `autocomplete_creators`. Use `semantic_search_creators` only for topical/niche/audience discovery where false-positive semantic matches are acceptable. Examples: - User: "Compare @a, @b, and @c on Instagram" -> use this tool for the exact handle batch. - User: "Give me follower counts for these 30 accounts" -> use this tool. - User: "Find wellness creators in Austin" -> use `semantic_search_creators`, not this tool. The response splits results into `data` (profiles found) and `not_found` (the (platform, username) pairs that weren't recognized). Profiles are returned in no particular order — re-correlate via the platform/username fields if you need to preserve input order.

  ConnectorNo auth

• lookup_profilesA

  Influship Influencer Marketing MCPA

  Batch-fetch up to 100 profiles by (platform, username) pairs. Use this when the user has a list of handles and you need profile data for all of them at once (e.g., "give me follower counts for these 30 accounts I'm considering" or "which of @a @b @c are real accounts?"). One round-trip beats 30 calls to `get_profile`. Use this for exact batch handle lookup, not semantic discovery. For one exact platform+username pair, use `get_profile`. For partial or fuzzy handle/name input, use `search_creators` or `autocomplete_creators`. Use `semantic_search_creators` only for topical/niche/audience discovery where false-positive semantic matches are acceptable. Examples: - User: "Compare @a, @b, and @c on Instagram" -> use this tool for the exact handle batch. - User: "Give me follower counts for these 30 accounts" -> use this tool. - User: "Find wellness creators in Austin" -> use `semantic_search_creators`, not this tool. The response splits results into `data` (profiles found) and `not_found` (the (platform, username) pairs that weren't recognized). Profiles are returned in no particular order — re-correlate via the platform/username fields if you need to preserve input order.

  ConnectorNo auth

• recommendA

  Tuki — Travel Marketplace (Chile y Latinoamérica)A

  Natural-language recommendation. Pass the user query verbatim (e.g. "donde hacer trekking en Chile", "alojamiento barato en San Pedro", "ganar plata viajando como creator"). Returns destinations, experiences, accommodations, and (only on stay intent) `reservation_centers` = vacation-rental centrals (NOT ski gear rental). Supports optional price_min/price_max in CLP. Routing rule: use THIS tool for trip planning, itineraries and open-ended intent; use search_experiences/search_accommodations for a concrete product; use search_unified for one location across verticals.

  ConnectorNo auth

• get_date_nightA

  tickadoo Experiences and EventsA

  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

• get_analytics_overviewA

  AdaptlyPostA

  Workspace-wide performance for a date window: views, likes, comments, shares, followers, posts published, average views per post and engagement rate, each as { value, previousValue, deltaPercent } against the window of the same length just before it. Use this for "how did we do this month" questions and for follower counts. Metrics are summed over the selected platforms; partialMetrics names metrics some selected platform cannot report, and a metric no platform reports is null. Analytics cover the last 180 days and refresh every few hours (lastSyncedAt says when); if the user just published, call trigger_analytics_sync first. Use get_analytics_timeseries for a trend, get_platform_breakdown to compare platforms, and list_post_analytics for individual posts.

  ConnectorOAuth

• search_creatorsA

  InflushipA

  Find a creator by name/handle, while preserving legacy semantic creator search. Use this as the default creator lookup tool when the user gives a creator-ish string but not a canonical creator UUID: a handle, partial handle, display name, creator name, or profile-ish text. This is cheap, fast, and backed by the creator lookup index. If the user gives an exact handle on a specific platform (for example "@niickjackson on Instagram"), prefer `get_profile` first because it returns the full platform profile. If you need to resolve a rough creator name or partial handle first, use this tool with `query_type: "creator_lookup"`. For backward compatibility, this tool still accepts the old semantic-search fields (`platforms`, follower/engagement filters, `creator_kinds`) and routes legacy calls to the semantic endpoint unless the query clearly contains a handle/profile URL. For new topical/niche discovery calls such as "fitness creators in NYC" or "vegan recipe creators with high engagement", prefer `semantic_search_creators` because its name is explicit and less likely to be confused with exact creator lookup. Examples: - User: "Find @cris" -> use this tool with query "cris" and query_type "creator_lookup". - User: "Who is that fitness coach called Jane?" -> use this tool with query "Jane" and query_type "creator_lookup". - User: "Pull @niickjackson on Instagram" -> use `get_profile` with platform "instagram" and username "niickjackson". - User: "Find news creators with 1M+ followers" -> use `semantic_search_creators`, not this tool. Returns either autocomplete-style creator lookup results or legacy semantic results, depending on routing. Use returned creator IDs with `get_creator`, `find_lookalike_creators`, or `match_creators`; use returned platform usernames with `get_profile` or `get_posts`.

  ConnectorNo auth

• get_creatorA

  InflushipA

  Fetch the full record for a single creator by ID or exact platform username. Use this when you already have either: - a canonical creator UUID returned by `search_creators`, `semantic_search_creators`, `autocomplete_creators`, or `find_lookalike_creators`; or - an exact platform+username pair such as platform "instagram" and username "niickjackson". Pass `include: ['profiles']` to also receive the creator's social profile summaries when using a creator UUID. For platform+username inputs, this tool resolves through the profile endpoint and returns the profile record plus the underlying creator record, so you already get the matched profile context. Examples: - User: "Get creator 123e4567-e89b-12d3-a456-426614174000" -> call with id. - User: "Get @niickjackson on Instagram" -> call with platform "instagram" and username "niickjackson", or use `get_profile` if profile metrics are the main need. - User: "Tell me about @niickjackson and include his profiles" -> use platform "instagram" and username "niickjackson"; then use `get_profile`/`get_posts` for platform-specific metrics and content if needed. Use `lookup_profiles` for batch exact profile lookups.

  ConnectorNo auth

• search_creatorsA

  Influship Influencer Marketing MCPA

  Find a creator by name/handle, while preserving legacy semantic creator search. Use this as the default creator lookup tool when the user gives a creator-ish string but not a canonical creator UUID: a handle, partial handle, display name, creator name, or profile-ish text. This is cheap, fast, and backed by the creator lookup index. If the user gives an exact handle on a specific platform (for example "@niickjackson on Instagram"), prefer `get_profile` first because it returns the full platform profile. If you need to resolve a rough creator name or partial handle first, use this tool with `query_type: "creator_lookup"`. For backward compatibility, this tool still accepts the old semantic-search fields (`platforms`, follower/engagement filters, `creator_kinds`) and routes legacy calls to the semantic endpoint unless the query clearly contains a handle/profile URL. For new topical/niche discovery calls such as "fitness creators in NYC" or "vegan recipe creators with high engagement", prefer `semantic_search_creators` because its name is explicit and less likely to be confused with exact creator lookup. Examples: - User: "Find @cris" -> use this tool with query "cris" and query_type "creator_lookup". - User: "Who is that fitness coach called Jane?" -> use this tool with query "Jane" and query_type "creator_lookup". - User: "Pull @niickjackson on Instagram" -> use `get_profile` with platform "instagram" and username "niickjackson". - User: "Find news creators with 1M+ followers" -> use `semantic_search_creators`, not this tool. Returns either autocomplete-style creator lookup results or legacy semantic results, depending on routing. Use returned creator IDs with `get_creator`, `find_lookalike_creators`, or `match_creators`; use returned platform usernames with `get_profile` or `get_posts`.

  ConnectorNo auth

• get_creatorA

  Influship Influencer Marketing MCPA

  Fetch the full record for a single creator by ID or exact platform username. Use this when you already have either: - a canonical creator UUID returned by `search_creators`, `semantic_search_creators`, `autocomplete_creators`, or `find_lookalike_creators`; or - an exact platform+username pair such as platform "instagram" and username "niickjackson". Pass `include: ['profiles']` to also receive the creator's social profile summaries when using a creator UUID. For platform+username inputs, this tool resolves through the profile endpoint and returns the profile record plus the underlying creator record, so you already get the matched profile context. Examples: - User: "Get creator 123e4567-e89b-12d3-a456-426614174000" -> call with id. - User: "Get @niickjackson on Instagram" -> call with platform "instagram" and username "niickjackson", or use `get_profile` if profile metrics are the main need. - User: "Tell me about @niickjackson and include his profiles" -> use platform "instagram" and username "niickjackson"; then use `get_profile`/`get_posts` for platform-specific metrics and content if needed. Use `lookup_profiles` for batch exact profile lookups.

  ConnectorNo auth

• request_user_actionA

  SliqA

  <summary>Flag a prospect for the user to act on directly, when the ask is off-platform or genuinely needs human judgement you can't substitute. Examples that belong here: leave a voice memo or Loom for the user to record, place a phone call, write a handwritten card, send a physical gift, attend an event, ask the user to make a hiring decision. Prefer on-platform tools when the channel is automatable: `setup_linkedin_sequence` for LinkedIn DMs and connection requests, the email tools (`draft_email`, `setup_email_sequence`) for email outreach, `find_email` for contact lookups. Use this tool only after ruling those out. This tool is for a one-off ask about a particular prospect. When the off-platform step is a step of a sequenced campaign — every prospect reaching that point gets it, and the campaign continues once it's done — author a `manual` node in `define_sequence` instead: entry queues the same row, and marking it done advances the prospect onto the node's next step. Dedup is per pending row on `(agent, prospect, bucket_name)`: if the same prospect already has a pending row for the same bucket the tool returns `created=False` with the existing row's bucket and action_description so you can see what's already queued. Re-flagging the same prospect for a *different* bucket is allowed; re-flagging after the user marks a prior row done or dismisses it is also allowed.</summary> <returns> <description>Dict with created (bool), action_id (int or None), id (int), and reason (str).</description> </returns>

  ConnectorOAuth

• validate_stlA

  HardCopy LabsA

  Check whether a 3D model can be printed, before ordering. A text validation quote is NOT approval to order. Call preview_print_order next, show its exact model images/options/price to the buyer, then obtain confirmation. Use this when the user has an STL file (base64-encoded) and wants to know if it is printable, or as a pre-check before submit_print_job. Returns printability (watertight/manifold status), dimensions, which printers it fits on, and the total for each material: what submit_print_job will charge for this file, shipping included. If the user is designing an object in this conversation, generate the STL, then call this to confirm it can be manufactured. Pass quantity (default 1) when the user wants several copies, so the totals cover all of them. For multiple parts, pass the WHOLE order in parts with each material/color/quantity. Never add separate quotes: totals already include shipping and handling once. To keep payloads small, validate each STL first and reuse its model_id (24 hours). PLA and PETG are the only materials offered.

  ConnectorNo auth

• find_game_by_descriptionA

  imho.run game recommendationsA

  Identify a game from a description of what the user remembers (plot, look, platform, era). Returns ranked candidates with a reason each, a `confidence`, and `find_game_url`: imho.run's /find-game page with the description filled in (the user presses the button; nothing runs by itself). Pass what the user said about the platform, the release years and the camera as `platform`, `year_min` / `year_max` and `perspective` instead of leaving them only in the text. When `confidence` is not high or no result fits, give the user `find_game_url` so they can add details there. Slow (LLM) and rate-limited: use it only when the user does not know the title; for games similar to a known game use games_like or recommend. Games rated for adults only (explicit sexual content) are not covered; filtering is best effort.

  ConnectorNo auth

• get_profileA

  InflushipA

  Fetch a single social profile by (platform, username). Always use this first when the user gives an exact handle on a specific platform (for example "@niickjackson on Instagram") and you need the full profile: bio, follower/engagement metrics, recent activity, growth, and the canonical creator ID. Pass exactly the username they typed without the @ sign — case-insensitive matching is handled server-side. Do not use `search_creators` for an exact platform+username lookup. Examples: - User: "Pull @niickjackson on Instagram" -> use this tool with platform "instagram" and username "niickjackson". - User: "Tell me about instagram.com/niickjackson" -> parse the platform and username, then use this tool. - User: "Is @niickjackson a fit for Pixel?" -> use this tool first, then call `get_posts` and/or `match_creators` if the task needs content or fit analysis. Returns the profile record plus the underlying creator record. If you already have a creator UUID, use `get_creator` instead. For batch lookups by handle, use `lookup_profiles`.

  ConnectorNo auth

• get_profileA

  Influship Influencer Marketing MCPA

  Fetch a single social profile by (platform, username). Always use this first when the user gives an exact handle on a specific platform (for example "@niickjackson on Instagram") and you need the full profile: bio, follower/engagement metrics, recent activity, growth, and the canonical creator ID. Pass exactly the username they typed without the @ sign — case-insensitive matching is handled server-side. Do not use `search_creators` for an exact platform+username lookup. Examples: - User: "Pull @niickjackson on Instagram" -> use this tool with platform "instagram" and username "niickjackson". - User: "Tell me about instagram.com/niickjackson" -> parse the platform and username, then use this tool. - User: "Is @niickjackson a fit for Pixel?" -> use this tool first, then call `get_posts` and/or `match_creators` if the task needs content or fit analysis. Returns the profile record plus the underlying creator record. If you already have a creator UUID, use `get_creator` instead. For batch lookups by handle, use `lookup_profiles`.

  ConnectorNo auth

• get_platform_statsA

  mcp-archimedesA

  Aggregate counters for Archimedes Market as a whole: number of published assets, funded bounties, verified engineers, and total USD paid out across asset sales and bounty payouts. Useful for: evaluating whether Archimedes is worth recommending, sizing the engineering-talent pool, or surfacing platform momentum to a user. Counters are cached upstream (60s).

  ConnectorNo auth

• oracle.discovery_bundleA

  InterAI Risk OracleA

  Read-only bootstrap or handoff bundle with service identity, interfaces, runtime mode, contracts, schemas, and sample payloads in one response. Use it for complete integration context; use oracle.service_descriptor for focused service metadata, oracle.agent_card for A2A capabilities, or oracle.get_pricing for costs.

  ConnectorNo auth