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
- 01
Install in one call
install_plugin adds a plugin to the environment; plugin=empty starts one that records.
- 02
Collections
Brazil ICP-Brasil, Logistics & fiscal, Payments & notifications, Workplace & dev tools: install_collection adds what is missing.
- 03
Look before installing
get_catalog_plugin shows routes, pages it draws, synthetic people, situations to provoke, permissions and files.
- 04
Find and filter
By words, region (Global or Brazil), browser pages or collection; cards say installed here and update available.
- 05
Yours to edit
An installed plugin is plain YAML: route editor, set_answer, or put_plugin with a version check (409 on conflict).
- 06
Import your own
import_plugin reads a folder, a .zip or a git URL (path, ref) and checks it; install_import installs it.
- 07
Validated with line numbers
validate_plugin returns schema and expression errors with line numbers before anything is saved.
- 08
Payments, two ways
Stripe, PayPal, Adyen, Mercado Pago, Pagar.me, Asaas and Pix: charges, refunds and signed webhooks your app must verify.
- 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

Filter Global or Brazil, set by the plugin's author.
A pack of plugins for one kind of app; add the rest in one call.
Each card says whether this environment has it, and its version.
Routes and the answers you can give, before you install.
Installs the plugin YAML; point the app at it or use the real host name.
- Region
Filter Global or Brazil, set by the plugin's author.
- A collection
A pack of plugins for one kind of app; add the rest in one call.
- Installed here
Each card says whether this environment has it, and its version.
- What it covers
Routes and the answers you can give, before you install.
- 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

Each situation the provider can answer, with its status, ready to force.
Filled from the request and the state, in the provider's own shape.
The same as force_answer: ends by itself after N calls.
Synthetic CPFs with their state; set_data replaces or appends rows.
The route and decide step that gives this answer.
- Named answers
Each situation the provider can answer, with its status, ready to force.
- Body template
Filled from the request and the state, in the provider's own shape.
- Force for the next calls
The same as force_answer: ends by itself after N calls.
- Data the answers read
Synthetic CPFs with their state; set_data replaces or appends rows.
- 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 twicereCAPTCHA answers timeout-or-duplicate for a reused token
send the same token againBot scorereCAPTCHA scores 0.1 for a token starting with bot
a bot… tokenTurnstile failsA token starting with fail fails the check
a fail… tokenCard declinedStripe declines the PaymentIntent
pm_card_chargeDeclinedFace mismatchDatavalid says the selfie is someone else
force_answer face_mismatchFree tier exhaustedReceitaWS answers 429 after 3 calls a minute
call it a fourth timeExpired person certificateA cloud certificate that expired yesterday, in every plugin
issue_person_certificatePush rejectedViDaaS push approval rejected or timed out on the phone
approve_push answer=reject | timeoutSignature step failsREST PKI start or finish answers 422 or 500
fail_restpki step=finishAny plugin down503, timeout or reset on any installed plugin
force_answer
Why not the real sandbox
Written once, by someone
A person who knows the provider writes the plugin; everyone else installs it in one call.
Situations named
Each plugin lists what it can answer and provoke, named for what it means.
Synthetic data built in
People, CPFs, CNPJs and accounts at acme and globex; never a real person.
Safe by default
A plugin cannot reach the network or the disk unless it declares it; pages are fields, not scripts.
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.
Set up the payments and notifications providers for this environment and show me what Stripe can provoke.
MCP tools
list_pluginsThe catalog with collections, filters and what is installedget_catalog_pluginOne plugin before installing itinstall_pluginInstalls a plugin, or an empty one that recordsinstall_collectionInstalls a collection's missing pluginsimport_pluginReads your plugin from a folder, .zip or git URLinstall_importInstalls a plugin import_plugin readvalidate_pluginErrors with line numbers before savingput_pluginReplaces the whole plugin YAMLremove_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
- The catalog lives in engine/plugins/ in the repository; contributions must pass validate_plugin and use synthetic data.