Runnable examples for PNTR: free *.pntr.dev subdomains with DNS management, catch-all test email, webhook capture, an API, CLI, and MCP integration.
These examples are deliberately small. Each one identifies the boundary it tests and the production behavior it does not replace.
| Example | What it demonstrates | Offline verification |
|---|---|---|
| Stripe webhook + Express | Inspect a Stripe sandbox delivery with PNTR, then verify the signature in an Express handler | Generates a signed fixture locally and tests valid, invalid, and missing signatures |
| Playwright email/OTP | Give each test a unique address, poll the PNTR email API, and submit a labeled OTP | Uses a local fake PNTR API; no browser or live credentials required |
| MCP prompts | Bounded prompts for creating capture endpoints and reading test email | Prompts name the allowed actions and protect against untrusted captured content |
git clone https://github.com/oddunits/pntr-examples.git
cd pntr-examples
cd stripe-webhook-express
npm install
npm testEach example has its own dependencies and README. Installing one example does not install the others.
- Use Stripe sandboxes and synthetic users.
- Copy
.env.exampleto.envlocally, but never commit.env. - Treat captured webhook bodies and email content as untrusted input.
- A PNTR capture endpoint acknowledges and stores a request. Its
200response does not prove that your application processed the event. - Keep Stripe signature verification on the unmodified request body.
- Use a unique test recipient and a bounded polling timeout in CI.
- Do not put production credentials, customer data, or real verification codes in fixtures or AI prompts.