io.github.livevariant/livevariant

Est-ce que io.github.livevariant/livevariant est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.livevariant/livevariant » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 9 outils

• build_test≈ 2655 tokens

  Creates a LiveVariant test and returns every URL needed to run it, plus a freshly generated stats secret. Pass `variants` to test one element, or `slots` to test several at once (hero image AND call-to-action, say). With slots the test optimizes the COMBINATION: one model learns how the elements interact, which two separate tests structurally cannot see. There is no algorithm to pick either way; every test runs the same joint model, sized from its shape. By default, nothing is registered anywhere: the config IS the test, encoded into the URLs, and the test's identity is a hash of it. Pass `publishableKey` on an account-enabled deployment to also register the new test to that key's organization, so it appears under My tests; the config and URLs are still the test, and registration failure is returned as a warning rather than failing the build. Editing a variant later produces a DIFFERENT test with its own empty history, which is usually what you want per campaign but is worth saying out loud to whoever you are building this for. The stats secret is returned once and never again. Only its hash goes into the config, so nobody, including this service, can recover it. Give it to the person who will read the results.

  Paramètres, retour & exemple (9)

  Paramètres

  • name · string · optionnel
    A label for your own reference, and the one field worth spending a merge tag on in a recurring ESP template: it is part of the test's identity, so n={{campaign_name}} mints a separate, separately readable test per campaign, and the name is what list_tests searches.
  • slots · object · optionnel
    Multi-element test: variants per element, keyed by a short name like "hero" or "cta". The test serves and learns combinations.
  • region · string · optionnel · wnam | enam | sam | weur | eeur | apac | oc | afr
    Where the test's state lives. A placement hint (wnam, enam, sam, weur, eeur, apac, oc, afr, me) or "eu" for the EU jurisdiction (state guaranteed created and kept inside the EU). Defaults to the creator's own region when the host can tell; without any, state is born wherever the FIRST request comes from, which in email is routinely a mail provider's US datacenter.
  • context · array · optionnel
    Dimensions to learn a separate winner for.
  • variants · array · optionnel
    Single-element test: two or more variants. The first is the control.
  • redirectUrl · string · optionnel
    Where clicks land when a variant does not say.
  • variantParam · string · optionnel
    Stamp the served combination into this parameter on redirect, e.g. "utm_content", so the test shows up in the customer's own analytics.
  • slotRedirects · object · optionnel
    Where clicks on ONE element land, when elements point at different pages (a hero leading to the campaign landing page, a CTA below it to pricing). Keyed like `slots`. Falls back to `redirectUrl`; a variant's own redirectUrl still wins over both. Setting any of these means every click link must name its slot, which slotLinks does for you.
  • publishableKey · string · optionnel
    Registers the new test to the organization identified by a publishable key the user provides for an organization they administer. Result access stays tied to this test's stats secret. Only works on account-enabled deployments; elsewhere a warning says so and the test still works.

  Exemple d'appel

  {"name": "build_test", "arguments": {"name": "texte", "slots": {}, "region": "wnam", "context": [], "variants": [], "redirectUrl": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"urls": {}, "slots": [], "config": "texte", "region": "texte", "testId": "texte", "warnings": [], "slotLinks": {}, "statsSecret": "texte", "combinations": 1, "destinations": [], "registeredTo": "texte", "emailTemplate": {}}}

• generate_priors≈ 925 tokens

  Takes YOUR estimate of how each variant will perform and converts it into the prior the model starts from, so a test does not spend its first visitors rediscovering what you already suspect. You supply the guess; this does the arithmetic and the capping. That capping is the point: a prior is expressed as pseudo-observations, and it is deliberately held weak enough that real data overrides it quickly. The response says exactly how many real visitors per variant it takes to wash your guess out, so you can judge whether you have been too confident. Being wrong here costs a little early traffic, not the test. Priors are outside the identity hash, so the test keeps its id, its URLs and any history it already has. Pass `when` to make the belief hold for ONE segment only ("image B is the one for the blue segment"). Without it the belief is about every visitor, which is a different and much stronger claim.

  Paramètres, retour & exemple (5)

  Paramètres

  • test · string · optionnel
    The test: an encoded config, or any LiveVariant URL containing one (serve, click, pixel, manage), or a query-parameter serve URL. Paste whatever you have.
  • when · object · optionnel
    Context this belief is limited to, as dimension key to value (e.g. {"color": "blauw"}). The keys must be dimensions the test declares. Omit it for a belief about every visitor.
  • config · string · optionnel
    Alias for `test`: the same value under the name build_test returns it as (`config`). Pass one or the other.
  • beliefs · array · requis
  • confidence · ? · optionnel
    How much your guess is worth in observations. low=5, medium=15, high=30, or give a number directly. Higher means the test trusts you for longer before the data takes over.

  Exemple d'appel

  {"name": "generate_priors", "arguments": {"beliefs": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"notes": [], "config": "texte", "priors": [], "testId": "texte", "manageUrl": "texte", "washesOutAfter": 1}}

• get_stats≈ 916 tokens

  Fetches a test's results and works out what they mean. Alongside the raw counts it returns the probability that each combination is genuinely best and the expected cost of stopping now and keeping the leader. Use those rather than comparing conversion rates by eye: a variant ahead 2/10 to 1/10 looks twice as good and is very close to a coin flip, and that mistake is the single most common way an A/B test gets called wrong. Multi-slot tests also report per-slot marginals: how each variant did across every combination it appeared in. Needs the stats secret. If you have the manage URL, its #fragment IS the secret and it will be used automatically.

  Paramètres, retour & exemple (3)

  Paramètres

  • test · string · optionnel
    The test: an encoded config, or any LiveVariant URL containing one (serve, click, pixel, manage), or a query-parameter serve URL. Paste whatever you have.
  • config · string · optionnel
    Alias for `test`: the same value under the name build_test returns it as (`config`). Pass one or the other.
  • statsSecret · string · optionnel
    Omit when passing a manage URL that carries it in the fragment.

  Exemple d'appel

  {"name": "get_stats", "arguments": {"test": "texte", "config": "texte", "statsSecret": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"slots": {}, "testId": "texte", "bySignal": {}, "decision": {}, "excluded": {}, "combinations": [], "contextBuckets": 1, "totalAssignments": 1}}

• get_test_status≈ 616 tokens

  Reports what the deployment's registry knows about a test: whether it is claimed into an account (and by which organization), and whether each redirect destination is a verified domain. Unverified destinations work, but visitors see a 'Redirecting you to…' continue screen first. When you see verified: false, tell the user to verify the domain under Settings on the dashboard; the three ways are a DNS TXT record, serving the well-known file, or having the SDK tag with their publishable key live in the site's source. If the test is unclaimed, remind them the manage URL claims it in one click when opened signed in. Requires the test's stats secret, the same as get_stats. A manage URL's #fragment is used automatically.

  Paramètres, retour & exemple (3)

  Paramètres

  • test · string · optionnel
    The test: an encoded config, or any LiveVariant URL containing one (serve, click, pixel, manage), or a query-parameter serve URL. Paste whatever you have.
  • config · string · optionnel
    Alias for `test`: the same value under the name build_test returns it as (`config`). Pass one or the other.
  • statsSecret · string · optionnel
    Omit when passing a manage URL that carries it in the fragment.

  Exemple d'appel

  {"name": "get_test_status", "arguments": {"test": "texte", "config": "texte", "statsSecret": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"org": "texte", "testId": "texte", "claimed": true, "destinations": []}}

• inspect_test≈ 637 tokens

  Decodes a test and describes it: slots, variants, context, and whether it can be served by redirect. Also lints it for the mistakes that only show up once a campaign is out, such as an email test whose context comes from geo (which a mail proxy answers about itself). Use this before sending anything, and to answer 'what is this link?'.

  Paramètres, retour & exemple (2)

  Paramètres

  • test · string · optionnel
    The test: an encoded config, or any LiveVariant URL containing one (serve, click, pixel, manage), or a query-parameter serve URL. Paste whatever you have.
  • config · string · optionnel
    Alias for `test`: the same value under the name build_test returns it as (`config`). Pass one or the other.

  Exemple d'appel

  {"name": "inspect_test", "arguments": {"test": "texte", "config": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "slots": [], "region": "texte", "testId": "texte", "context": [], "findings": [], "combinations": 1, "resultsReadable": true}}

• list_tests≈ 404 tokens

  Lists tests registered to the signed-in account, newest first, with cursor pagination and an optional case-insensitive name filter. Only exists on deployments with accounts, and only answers for an identified caller: unlike every other tool, WHOSE tests these are cannot be expressed as an argument. Each entry carries the encoded config, which inspect_test and get_stats accept directly.

  Paramètres, retour & exemple (3)

  Paramètres

  • q · string · optionnel
    Case-insensitive substring filter on the test name
  • limit · integer · optionnel
  • cursor · string · optionnel
    Opaque cursor from a previous page's nextCursor

  Exemple d'appel

  {"name": "list_tests", "arguments": {"q": "texte", "limit": 1, "cursor": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tests": [], "nextCursor": "texte"}}

• register_test≈ 482 tokens

  Registers a test you built earlier to the organization a publishable key belongs to, so it shows under My tests and its stats are readable from the dashboard without the secret. Use this only when the user provides both the test's stats secret and a publishable key for an organization they administer. The stats secret must match the hash inside the config, and the publishable key identifies the organization to register into. Prefer passing publishableKey to build_test directly: it registers at creation in one step. Keyless tests cannot be registered this way (nothing to prove with); they register through the tag on a verified domain. The organization can remove a listing from its dashboard (the test itself keeps serving).

  Paramètres, retour & exemple (3)

  Paramètres

  • config · string · requis
    The encoded test config (from build_test or any test URL).
  • statsSecret · string · requis
    The test's stats secret, exactly as build_test returned it.
  • publishableKey · string · requis
    A publishable key for the target organization, provided by a user authorized to register tests there.

  Exemple d'appel

  {"name": "register_test", "arguments": {"config": "texte", "statsSecret": "texte", "publishableKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"org": "texte", "testId": "texte", "registered": true}}

• upload_image≈ 494 tokens

  Uploads an image to the deployment's asset store and returns its URL, for use as a variant's `image` (email tests) or `url`. The returned URL is deliberately not fetchable on its own: assets are only served with a short-lived signature that the serve endpoints mint per request, so uploading here does not create free static hosting. Use `previewUrl` (valid for an hour) to check what was stored. Storage is content-addressed: the id is the sha256 of the bytes, so uploading the same image twice is harmless and returns the same URL. Raster images only; SVG is refused because it can carry scripts. Not every deployment enables asset hosting, and this tool says so plainly when yours does not.

  Paramètres, retour & exemple (2)

  Paramètres

  • data · string · requis
    The image bytes, base64-encoded (plain base64, not a data: URL).
  • contentType · string · requis · image/png | image/jpeg | image/gif | image/webp | image/avif
    The image's actual type; the server stores and serves it as this.

  Exemple d'appel

  {"name": "upload_image", "arguments": {"data": "texte", "contentType": "image/png"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "size": 1, "assetId": "texte", "previewUrl": "texte", "contentType": "texte"}}

• variant_brief≈ 441 tokens

  Returns the constraints to write or generate test variants against, for email or web, plus the rules that decide whether a test can be read at all once it runs. The one that matters most: one idea per slot. To vary two elements, give the test two slots and let it learn the combination, rather than bundling both changes into one variant and never learning which half worked. Ask for this before drafting variants, then produce them yourself against what it returns.

  Paramètres, retour & exemple (5)

  Paramètres

  • goal · string · requis
    What the test should improve, e.g. 'more demo bookings'.
  • count · integer · optionnel
  • format · string · requis · image | text | html | url
    What each variant will be.
  • channel · string · requis · email | web
  • audience · string · optionnel
    Who sees it, if that shapes the copy.

  Exemple d'appel

  {"name": "variant_brief", "arguments": {"goal": "texte", "format": "image", "channel": "email"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"goal": "texte", "rules": [], "specs": [], "hosting": "texte", "nextStep": "texte", "variantCount": 1}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://livevariant.com/mcp