Plugin tracker

Tools

Explore what tracked Claude Connectors and ChatGPT Plugins can actually do. Search by tool, Plugin, Brand, category, verb, or access requirement.

Latest snapshot2026-09-12USmethodology registry-public-v1

Searchable tools

113,018

Authless tools

7,424

Auth required

100,766

Described tools

61,167

113,018 tools

List migrationslist · List migrations visible from the account named by `account_id`. A FIG v1-to-v2 migration pairs an older account with its replacement and tracks linked datasets, targets, seven-day Lookup API pull counts, approval, finish time, and `account_tree_relationship`, which says how the two accounts sit in the account hierarchy. Use this before creating a new migration or approving an existing one.FaradayFaradayPluginrequiredData & Analytics
List outcomeslist · List the propensity models the account has trained — churn, conversion, repeat purchase, donation, attendance, upgrade, lead scoring, and similar goals. Each Outcome scores people on their likelihood of attaining the behavior represented by its target Cohort. If a request may already be solved by an existing Outcome, listing first helps reuse it and preserves continuity in deployed Scopes. Each full record carries attainment, eligibility, and optional attrition Cohort references, predictor and bias settings, preview and build status, summary performance values such as lift and ROC AUC, and a report URL when available. Use `get_outcome_analysis` for feature importance and full performance details.FaradayFaradayPluginrequiredData & Analytics
List persona setslist · List the data-driven personas the account already has — typically things like 'segments of our customer base', 'lapsed donor archetypes', 'high-value buyer typologies'. A Persona Set is a k-means++-style clustering of a Cohort into K personas. If a client's segmentation request may already be solved here, listing first lets you reuse an existing Persona Set and keeps deployed Scopes consistent. Each Persona Set carries the source Cohort, the requested number of personas, the resolved persona records, and the latest job state.FaradayFaradayPluginrequiredData & Analytics
List placeslist · List the geographic definitions the account already has — store footprints, service areas, sales territories, drive-time zones, and custom areas. Places are reusable geographic predicates for Cohorts, such as people within 10 miles of a store; those Cohorts can then define modeling, market-analysis, or delivery populations. Chains and franchises often already have their footprint loaded, so listing first helps reuse it.FaradayFaradayPluginrequiredData & Analytics
List recommenderslist · List the personalized-recommendation models the account already has — next-best products, content, offers, locations, categories, or upgrades. Each Recommender learns from one interaction Stream and its item property, then produces ranked recommendations per person when attached to a Scope. Listing first helps reuse an existing model instead of training a duplicate. Each full record carries its source `stream_name`, `stream_property_name`, predictor settings, preview state, report URL, and latest build status.FaradayFaradayPluginrequiredData & Analytics
List scopeslist · List the account's Scope configurations. Each Scope defines which people are in a delivery population and which person-level fields to produce, including predictions, Persona membership, recommendations, Traits, Attributes, Cohort membership, identity fields, and optional Atlas location proximity. The response contains configuration, status, output column names, and aggregate counts, not the person rows or values. Targets attached to a Scope can send those rows and values to external systems.FaradayFaradayPluginrequiredData & Analytics
List streamslist · List the behavioral data wired up on the account — which transactions / signups / cancellations / page views / donations / clicks / etc. Faraday can see. Streams are the event channels that power behavioral Cohorts ('people who purchased in the last 90d'), Outcomes ('predict who will churn based on usage'), and Recommenders ('next best product based on past purchases'). Each Stream has a `type` (the conventional name like `transactions`), the schema of events it accepts, and links to the Datasets that populate it. Listing first lets you reuse the right Stream rather than invent a new one when defining a stream-based Cohort or Outcome.FaradayFaradayPluginrequiredData & Analytics
List targetslist · List the destinations where the account delivers person-level predictions, segments, recommendations, Traits, Attributes, and identity fields. Destinations include ad platforms, email and customer systems, data warehouses, cloud storage, SFTP files, the Lookup API, Hosted CSVs, and custom webhooks. Each Target names the Scope whose population and payload it sends, its Connection or hosted destination, representation, filters, limits, status, and connector options with secrets concealed. The response contains Target configuration and counts, not the person rows sent to the destination. Hosted CSV files cannot be downloaded through this MCP.FaradayFaradayPluginrequiredData & Analytics
List traitslist · List definitions for the per-person fields available to Cohorts, Outcomes, Persona Sets, and Recommenders. The catalog contains about 1,400 built-in consumer fields plus fields derived from the account's own Datasets. Built-in definitions cover demographics, income and wealth, home and household facts, life events, geography, purchases, interests, brand affinities, and modeled propensities. The tool returns field names, descriptions, types, source details, and coverage, not values tied to named people. Other tools can use these fields to select people, train models, or include person-level values in a Scope delivered through a Target. On accounts WITH `identity_graph` (see `get_account`), the built-in consumer data lives in Attributes (`list_attributes`) instead, and this tool returns only the account's own first-party Traits; those accounts cannot use built-in `fig/` Traits in Cohort conditions.FaradayFaradayPluginrequiredData & Analytics
List uploadslist · List every previously uploaded file for the account named by `account_id`, with subpath, byte size, MD5 (hex), and creation timestamp. The `subpath` is `<directory>/<filename>` — the same shape `get_upload` and `create_upload` expect.FaradayFaradayPluginrequiredData & Analytics
List use case revisionslist · List every saved revision of a use case, newest first. Returns just `revision_id` and `created_at`; fetch a revision's full content with `get_use_case_revision`. Useful for auditing what changed and when.FaradayFaradayPluginrequiredData & Analytics
List use caseslist · List the use cases the account already has — one per specific problem the client is solving with Faraday. Each entry returns `id`, `title`, `created_at`, and (when applicable) `archived_at`. Listing first lets you reuse an existing use case rather than create a duplicate. Archived use cases are returned alongside live ones — filter on `archived_at` if you want only live entries.FaradayFaradayPluginrequiredData & Analytics
List webhook endpointslist · List the URLs that receive resource lifecycle events from the account, with their status and subscribed event types. The response omits each endpoint's signing secret. The secret appears only once, in the response from `create_webhook_endpoint`.FaradayFaradayPluginrequiredData & Analytics
Rotate connection credentialsrotate · Replace the generated keypair for a Snowflake or ClickHouse Connection. The new private key is stored immediately and the response includes the new public key, which must then be installed on the warehouse user. Until that installation is complete, new connection attempts may fail. Other connector types do not support this operation.FaradayFaradayPluginrequiredData & Analytics
Unarchive resourceunarchive · Unarchive a supported resource so it can update again. If archived upstream dependencies block the change, inspect the dependency graph and acknowledge the exact resources with `cascade_to`, or acknowledge all of them with `cascade_to_all`; unarchive cascades upstream. The operation is subject to live-resource quotas and can restart processing or external Target deliveries. Built-in Traits are read-only.FaradayFaradayPluginrequiredData & Analytics
Unarchive use caseunarchive · Unarchive a previously-archived use case by clearing its `archived_at` timestamp. No-op if the use case is already live.FaradayFaradayPluginrequiredData & Analytics
Unlink resource from use caseunlink · Detach a Faraday resource from a use case. Removes the matching `(use_case_id, resource_type, resource_id)` link. No-op if no such link exists. Does not touch the underlying resource.FaradayFaradayPluginrequiredData & Analytics
Update accountupdate · Update the account named by `account_id` with a JSON Merge Patch. Omitted fields stay unchanged and `null` clears nullable fields. To change one branding field without replacing the others, send only that field inside `branding`; send `branding: null` to clear all branding.FaradayFaradayPluginrequiredData & Analytics
Update account overviewupdate · Replace the account overview with a new markdown body. The `content` field is a whole-document replacement, not a patch — supply the full markdown every time. Pass back the `revision_id` you just read; if another user or session saved a newer revision in the meantime, the call is rejected with the current state in the response and you should re-merge your edit. Omit `revision_id` only on the very first save for an account (when no overview has ever been written). A history snapshot is recorded automatically.FaradayFaradayPluginrequiredData & Analytics
Update atlasupdate · Update an Atlas with a JSON Merge Patch. Read the current Atlas first before changing its column mapping. Omitted object fields stay unchanged, `null` clears nullable fields, and arrays replace their prior values. `options.type` cannot change and secret placeholders do not overwrite stored credentials. A name-only change is immediate; any other accepted change queues a rebuild, which replaces the Atlas's locations and can change downstream Cohort populations, Scope payloads, and analyses that depend on them.FaradayFaradayPluginrequiredData & Analytics
Update attributeupdate · Update an owner-managed Attribute with a JSON Merge Patch. Omitted fields stay unchanged and `null` clears nullable fields. Changing `stream_name`, `value_property_name`, aggregation, or interpretation changes the value seen by downstream Cohorts, models, and Scopes. Attributes visible only through another feature store are read-only and return 404.FaradayFaradayPluginrequiredData & Analytics
Update cohortupdate · Update a Cohort with a JSON Merge Patch. Omitted fields stay unchanged, `null` clears nullable fields, and condition arrays replace their prior values. Condition or recency edits start asynchronous population evaluation and can change every Outcome, Persona Set, Scope, or Target that uses the Cohort. The response may show the prior count while the job runs.FaradayFaradayPluginrequiredData & Analytics
Update connectionupdate · Update a Connection with a JSON Merge Patch. Omitted fields stay unchanged and `null` clears nullable fields. `options.type` cannot change; create a new Connection to use another connector. Stored secrets remain unchanged when omitted, and `<secret>` placeholders never overwrite them. Credential or source-setting changes affect every Dataset, Atlas, and Target that uses this Connection. This tool is disabled in this MCP client by policy. Ask the user to complete this action in Faraday Enterprise at https://app.faraday.ai.FaradayFaradayPluginrequiredData & Analytics
Update datasetupdate · Update a Dataset's identity, Trait, Stream, reference-key, or ingestion mappings with a JSON Merge Patch. These mappings control how customer-supplied source fields become person-level data used by audiences, models, and deliveries. Omitted object fields stay unchanged, `null` clears nullable fields, and arrays replace prior values. Most accepted changes queue new ingestion.FaradayFaradayPluginrequiredData & Analytics
Update market opportunity analysisupdate · Update a Market Opportunity Analysis with a JSON Merge Patch. Omitted fields stay unchanged and `null` clears nullable Persona or locations fields. Changing `scope_id`, `outcome_id`, `persona_set_id`, `persona_id`, or `locations` starts a new asynchronous report build; the Outcome and Persona Set must belong to the selected Scope payload.FaradayFaradayPluginrequiredData & Analytics
Update migrationupdate · Update a migration with a JSON Merge Patch. Configuration fields (`notes`, `datasets`, `targets`) may change only from the owning FIG v2 account while the migration is unapproved. Providing a non-null `approved_at` from either linked account queues the account move and requires an interactive signed-in user. Repeated approval requests succeed without changing the first approval. The queued move gives every FIG v1 member access to the FIG v2 account, moves the users working there, reparents accounts only when `account_tree_relationship` calls for it, and suspends the FIG v1 account. Usage stays under the account where it happened. Support can reverse the whole move for a limited window.FaradayFaradayPluginrequiredData & Analytics
Update outcomeupdate · Update an Outcome with a JSON Merge Patch. Omitted fields stay unchanged and `null` clears nullable fields. Changing cohort references, predictors, or other model settings starts an asynchronous rebuild; the prior generation remains available until the new one finishes.FaradayFaradayPluginrequiredData & Analytics
Update personaupdate · Update one Persona within a Persona Set. Use this after reviewing the dimensions to change its human-readable `name`; the cluster membership and centroid are not editable.FaradayFaradayPluginrequiredData & Analytics
Update persona setupdate · Update a Persona Set with a JSON Merge Patch. Omitted fields stay unchanged and `null` clears nullable fields. `cohort_id` cannot be changed after creation. Changing `number_of_clusters`, modeling inputs, or preview state starts a new asynchronous build.FaradayFaradayPluginrequiredData & Analytics
Update placeupdate · Update a Place with a JSON Merge Patch. Omitted fields stay unchanged and `null` clears nullable fields. Any accepted update queues the Place to rebuild; changing its GeoJSON or addresses can change every Cohort that uses it. Poll `status` and `last_updated_output_at` before relying on the new geometry.FaradayFaradayPluginrequiredData & Analytics
Update recommenderupdate · Update a Recommender with a JSON Merge Patch. Omitted fields stay unchanged and `null` clears nullable fields. Changing `stream_name`, `stream_property_name`, predictors, or preview state starts a new asynchronous build.FaradayFaradayPluginrequiredData & Analytics
Update scopeupdate · Update a Scope with a JSON Merge Patch. Population changes alter which people downstream Targets send; payload changes alter the person-level identity fields, predictions, segments, recommendations, Traits, Attributes, Cohort membership, and Atlas location proximity they send. Switching `payload.location.select` between `nearest` and `all` changes the type of the location columns, so Targets already receiving them must be rebuilt afterward. Omitted fields stay unchanged, `null` clears nullable fields, arrays replace prior values, and changing `preview` from true to false enables full billed output.FaradayFaradayPluginrequiredData & Analytics
Update streamupdate · Update a Stream's descriptive metadata with a JSON Merge Patch. Writable fields include `literate`, `description`, `category`, deprecation fields, and property metadata. Omitted fields stay unchanged and `null` clears nullable fields. The event-type name and events emitted by Datasets are not changed here.FaradayFaradayPluginrequiredData & Analytics
Update targetupdate · Update a Target with a JSON Merge Patch. Omitted fields stay unchanged, `null` clears nullable fields, and arrays replace prior values. `options.type`, `representation.mode`, and `limit.method` cannot change. Changes to the destination, representation, filter, limit, or columns change later deliveries of person-level data; changes to the Scope change which people and fields the Target sends.FaradayFaradayPluginrequiredData & Analytics
Update traitupdate · Update a user-defined Trait with a JSON Merge Patch. Omitted fields stay unchanged and `null` clears nullable fields. Changing `statistical_type` changes how Cohorts, analysis, and models interpret its values. Built-in Traits are read-only and return 403; a Trait not visible to the account returns 404.FaradayFaradayPluginrequiredData & Analytics
Update use caseupdate · Apply a JSON Merge Patch to a use case. Fields you omit are left at their current values; explicit `null` clears a preface field. `revision_id` is REQUIRED and must echo the value you read from `get_use_case` — if the server's current revision has moved past it the call is rejected with a 409 whose body carries the latest state; re-merge against that and retry. Editing the preface, technical details, or draft flag records a new history snapshot. Archive is NOT changed by this call (use `archive_use_case` / `unarchive_use_case`).FaradayFaradayPluginrequiredData & Analytics
Update webhook endpointupdate · Update a webhook endpoint's URL, event subscriptions, or status with a JSON Merge Patch. Set status to disabled to pause delivery without deleting it. The signing secret does not change and is omitted from the response.FaradayFaradayPluginrequiredData & Analytics
Find locations with favourable current aurora conditionsfind · Finds AuroraReach-tracked locations with a currently open/flagged aurora sighting event (status=active), optionally restricted to a country or a lat/lng radius. This is a narrower signal than a forecast score - most places, most of the time, have nothing formally flagged even when their forecast score is reasonable, so an empty result is common and expected, not broken. For "should I go look" or a ranked comparison of nearby options regardless of whether anything is formally flagged, use find_best_viewing_locations instead.AuroraReachAuroraReachPluginnoneTravel & Hospitality
Find the best aurora viewing locations near an originfind · AuroraReach's opinionated answer to "where nearby should I drive?" - evaluates AuroraReach-tracked locations near an origin using the real forecast engine (same as get_aurora_forecast) for the requested date/time, and returns them ranked with score, conditions, distance, and a `why` explaining how each one compares to the top pick. Bounded to a small number of forecast lookups regardless of radius/limit to avoid excess upstream load. Includes relevant offers by default.AuroraReachAuroraReachPluginnoneTravel & Hospitality
Get AuroraReach aurora forecastget · AuroraReach's primary forecast tool: returns AuroraReach's own interpreted forecast for a location (not raw upstream NOAA/weather data) - a 0-100 score, a yes/maybe/no recommendation, a heuristic confidence, the best viewing window in the next 24h, cloud/weather impact, darkness/viewing suitability, and the individual signals behind the score. Optionally target a specific future date/time (within AuroraReach's ~3-day coverage window); omit it for the current hour. Includes a few relevant bookable offers by default. Use should_i_go_outside instead for a single opinionated yes/no answer, or plan_aurora_experience for a full evening plan.AuroraReachAuroraReachPluginnoneTravel & Hospitality
Get AuroraReach country aurora summaryget · Country-level aurora intelligence: top AuroraReach-tracked locations (ranked by observation/activity volume, the most consistently available popularity signal), an aggregate kp range, `active_sighting_score_range` (null when nothing is currently formally flagged anywhere in the country - that is expected, not broken), a recent community-sighting count, the canonical AuroraReach country page, and (by default) relevant offers. Use this for "where in <country> should I look" or "tell me about aurora in <country>" questions; use find_active_locations or find_best_viewing_locations for a live/forecast-based comparison instead of the observation-based ranking here.AuroraReachAuroraReachPluginnoneTravel & Hospitality
Get AuroraReach location detailsget · Get everything AuroraReach knows about a single location in one call: basic metadata, its current aurora condition/score, a historical sighting-report summary, nearby AuroraReach-tracked locations, a link to the full AuroraReach page for this location (more photos, detail and booking options live there), and (by default) a few relevant bookable offers. Use this for "tell me about <place>" or as a follow-up after search_locations. For a dedicated "can I see it right now" answer use get_current_conditions instead; for the full forward-looking forecast use get_aurora_forecast.AuroraReachAuroraReachPluginnoneTravel & Hospitality
Get AuroraReach map conditions within an areaget · Returns the structured data behind AuroraReach's map view for a bounded circular area: AuroraReach-tracked locations and their current scores within radius_km of a centre point. Always requires a bounded scope (centre + radius, capped) - never returns an unbounded global dataset. Does not include per-point cloud cover or light pollution (not available at this scale/AuroraReach does not model light pollution) - use get_aurora_forecast for weather-level detail on one location.AuroraReachAuroraReachPluginnoneTravel & Hospitality
Get aurora viewing hotspots near a destinationget · Surfaces AuroraReach-tracked locations (towns/cities, not individual lookout points or photo spots) near a destination that are historically well-regarded for aurora viewing (ranked by rating and observation volume), plus a count of recent community aurora check-ins nearby as a real-activity signal, with an explicit date range and radius. Never fabricates hotspot data - everything returned already exists in AuroraReach's places/checkins data. Includes relevant offers by default.AuroraReachAuroraReachPluginnoneTravel & Hospitality
Get bookable AuroraReach offersget · Returns bookable aurora experiences/tours through AuroraReach's existing commercial offers integration (AuroraReach Partner Services, Viator, GetYourGuide, and AuroraReach's own activity/trip offers). Use this whenever booking/commercial intent is central, e.g. "find me an aurora tour in Levi". Affiliate URLs are AuroraReach's own tracked links, returned unmodified - never reconstruct a direct provider URL. Returns an empty offers array (not an error) when nothing is available. Provide `location` or `country` for relevant results - without either, results reflect the server's own location, not the user's.AuroraReachAuroraReachPluginnoneTravel & Hospitality
Get check-ins for a specific AuroraReach locationget · Returns AuroraReach community check-ins reported specifically at one location within an explicit time window, e.g. to answer "are people actually seeing auroras around Rovaniemi right now?". Only public fields are returned - no private user data or exact device GPS. For a wider area or country-level view use get_recent_checkins instead.AuroraReachAuroraReachPluginnoneTravel & Hospitality
Get current aurora conditionsget · Answers "can I see the aurora right now?" for a location - a concise snapshot of AuroraReach's current score, yes/maybe/no recommendation, live aurora activity signals (kp gap, Bz, solar wind), current cloud/visibility conditions, darkness state, the reasoning behind the recommendation, a link to the live AuroraReach page for this location, and (by default) a few relevant bookable offers. For a forward-looking forecast (best time tonight, future dates) use get_aurora_forecast instead.AuroraReachAuroraReachPluginnoneTravel & Hospitality
Get global aurora activityget · Returns AuroraReach's current worldwide aurora activity: the strongest continents, currently-active countries and cities (with scores, using the same threshold AuroraReach's public /highlights pages use), and any upcoming global geomagnetic storm windows (NOAA G-scale). Use this for "where is the aurora active right now?" or "is anything happening globally?" rather than iterating find_active_locations per country.AuroraReachAuroraReachPluginnoneTravel & Hospitality
Get historical aurora activity for a locationget · Returns AuroraReach's historical aurora activity for a location over a date range: how many community sighting reports were recorded and when the earliest/latest ones were. Built on the same activity stats behind AuroraReach's public stats endpoint. For a month/week/weekday/hour breakdown ("best time to visit") use get_best_aurora_times instead.AuroraReachAuroraReachPluginnoneTravel & Hospitality
Get nearby AuroraReach locationsget · Given an AuroraReach location, returns other AuroraReach-tracked locations near it - distance, compass direction, current score and canonical URL for each. Use this for "what else is nearby" or as an input to travel-planning questions. For an opinionated ranked recommendation of where to actually go tonight, use find_best_viewing_locations instead.AuroraReachAuroraReachPluginnoneTravel & Hospitality

Tool Explorer FAQ

What is Tool Explorer?

Tool Explorer indexes the callable tool names and descriptions attached to public registry profiles. It is useful for seeing what agents can actually invoke, not just which profile exists.

How do category and verb filters work?

Category filters use the live registry category rollup. Verb filters use the public tool insights rollup, so the page stays backed by the same read models as the tracker charts.

Why do auth requirements matter?

Auth requirements show whether a tool is likely usable without account connection, requires authentication, is private, or is unknown in the current snapshot.