stuntman / providers / plugin catalog

Plugin catalog

45 ready plugins for providers apps call every day, installed one at a time or a whole collection at once.

Stands in for

  • Google reCAPTCHA
  • Cloudflare Turnstile
  • Bank gateway (boletos, mTLS)
  • Orders partner (REST example)
  • Partner portal (session cookie)
  • SERPRO Datavalid
  • GCC consent
  • Soluti BirdID
  • Valid ViDaaS
  • Lacuna REST PKI
  • OSRM
  • Google Maps Platform
  • Nominatim
  • OCR.space
  • ReceitaWS
  • SEFAZ NF-e (SP, homologação)
  • Comtele SMS
  • Stripe
  • Resend
  • OneSignal
  • Microsoft Graph
  • Google Drive
  • Calendly
  • lemlist
  • Azure DevOps
  • New Relic NerdGraph
  • Pix (Banco Central API)
  • Mercado Pago
  • Pagar.me
  • Asaas
  • NFS-e Nacional
  • NFS-e ABRASF
  • Correios
  • Melhor Envio
  • ViaCEP
  • BrasilAPI
  • Twilio
  • PayPal
  • Adyen
  • Shopify
  • Slack
  • HubSpot
  • GitHub
  • Sentry
  • Auth0

Everything Plugin catalog gives you

  1. 01

    Install in one call

    install_plugin adds a plugin to the environment; plugin=empty starts one that records.

  2. 02

    Collections

    Brazil ICP-Brasil, Logistics & fiscal, Payments & notifications, Workplace & dev tools: install_collection adds what is missing.

  3. 03

    Look before installing

    get_catalog_plugin shows routes, pages it draws, synthetic people, situations to provoke, permissions and files.

  4. 04

    Find and filter

    By words, region (Global or Brazil), browser pages or collection; cards say installed here and update available.

  5. 05

    Yours to edit

    An installed plugin is plain YAML: route editor, set_answer, or put_plugin with a version check (409 on conflict).

  6. 06

    Import your own

    import_plugin reads a folder, a .zip or a git URL (path, ref) and checks it; install_import installs it.

  7. 07

    Validated with line numbers

    validate_plugin returns schema and expression errors with line numbers before anything is saved.

  8. 08

    Payments, two ways

    Stripe, PayPal, Adyen, Mercado Pago, Pagar.me, Asaas and Pix: charges, refunds and signed webhooks your app must verify.

  9. 09

    Brazil, end to end

    ICP-Brasil signing, NFS-e Nacional and ABRASF, Correios, Melhor Envio, ViaCEP and BrasilAPI with valid synthetic CPFs, CNPJs and CEPs.

The screens

Each number is a control or a reading on the real screen. Everything you can click there, your agent can do with a tool.

The catalog

The catalog: the Plugin catalog screen in Stuntman
1Region

Filter Global or Brazil, set by the plugin's author.

1 of 5
2A collection

A pack of plugins for one kind of app; add the rest in one call.

2 of 5
3Installed here

Each card says whether this environment has it, and its version.

3 of 5
4What it covers

Routes and the answers you can give, before you install.

4 of 5
5Add to the environment

Installs the plugin YAML; point the app at it or use the real host name.

5 of 5
  1. Region

    Filter Global or Brazil, set by the plugin's author.

  2. A collection

    A pack of plugins for one kind of app; add the rest in one call.

  3. Installed here

    Each card says whether this environment has it, and its version.

  4. What it covers

    Routes and the answers you can give, before you install.

  5. Add to the environment

    Installs the plugin YAML; point the app at it or use the real host name.

An installed plugin: named answers and data

An installed plugin: named answers and data: the Plugin catalog screen in Stuntman
1Named answers

Each situation the provider can answer, with its status, ready to force.

1 of 5
2Body template

Filled from the request and the state, in the provider's own shape.

2 of 5
3Force for the next calls

The same as force_answer: ends by itself after N calls.

3 of 5
4Data the answers read

Synthetic CPFs with their state; set_data replaces or appends rows.

4 of 5
5Used by

The route and decide step that gives this answer.

5 of 5
  1. Named answers

    Each situation the provider can answer, with its status, ready to force.

  2. Body template

    Filled from the request and the state, in the provider's own shape.

  3. Force for the next calls

    The same as force_answer: ends by itself after N calls.

  4. Data the answers read

    Synthetic CPFs with their state; set_data replaces or appends rows.

  5. Used by

    The route and decide step that gives this answer.

Break it on purpose

The failures you need to test, exactly when you ask: from the screen or by a tool call, each one shown on the timeline with who caused it.

  • Token used twice

    reCAPTCHA answers timeout-or-duplicate for a reused token

    send the same token again
  • Bot score

    reCAPTCHA scores 0.1 for a token starting with bot

    a bot… token
  • Turnstile fails

    A token starting with fail fails the check

    a fail… token
  • Card declined

    Stripe declines the PaymentIntent

    pm_card_chargeDeclined
  • Face mismatch

    Datavalid says the selfie is someone else

    force_answer face_mismatch
  • Free tier exhausted

    ReceitaWS answers 429 after 3 calls a minute

    call it a fourth time
  • Expired person certificate

    A cloud certificate that expired yesterday, in every plugin

    issue_person_certificate
  • Push rejected

    ViDaaS push approval rejected or timed out on the phone

    approve_push answer=reject | timeout
  • Signature step fails

    REST PKI start or finish answers 422 or 500

    fail_restpki step=finish
  • Any plugin down

    503, timeout or reset on any installed plugin

    force_answer

Why not the real sandbox

Your AI agent drives it

Claude Code, Codex or any MCP client connects to /mcp (or calls /api over plain HTTP), sets the stand-in up, breaks it on cue and reads what your app did.

you

Set up the payments and notifications providers for this environment and show me what Stripe can provoke.

install_collection{"name": "Payments & notifications"}
→ ok installed stripe, resend, onesignal
get_catalog_plugin{"plugin": "stripe"}
→ ok routes, webhooks, situations: card_declined, missing_amount, 429, 503, timeout

MCP tools

  • list_pluginsThe catalog with collections, filters and what is installed
  • get_catalog_pluginOne plugin before installing it
  • install_pluginInstalls a plugin, or an empty one that records
  • install_collectionInstalls a collection's missing plugins
  • import_pluginReads your plugin from a folder, .zip or git URL
  • install_importInstalls a plugin import_plugin read
  • validate_pluginErrors with line numbers before saving
  • put_pluginReplaces the whole plugin YAML
  • remove_api_serviceRemoves a plugin from the environment

The same over HTTP

  • GET/api/plugins
  • GET/api/catalog/{plugin}
  • POST/api/plugins
  • POST/api/catalog/collections/install
  • POST/api/catalog/imports
  • POST/api/plugins/{service}/validate