crumple

A crumple zone for AI agents.

Crumple puts your API in front of AI agents as MCP tools, and takes the damage when something goes wrong. Press a button to break something. It runs on this server, right now, against a fake API.

Break something

A payment goes through, then its response is lost. Does a retry charge twice?
The API stops answering. Does the agent wait forever?
A read-only key tries to delete a customer. Does the request reach the API?
A customer's record says to delete them, and a scripted agent obeys. Is anything deleted?

Nothing yet. Press a button, and what happened shows here.

Connect a real client

This is a real MCP endpoint, and these keys are public on purpose. They reach fake data, and neither can delete.

claude mcp add --transport http crumple https://crumple.latitude10.tech/mcp --header "Authorization: Bearer crumple_public-demo-read-key-fake-data-nothing-else"

To let an agent charge fake customers as well, use this key instead:

crumple_public-demo-charge-key-fake-payments-only-1

Everyone shares these keys, and the data lives in memory on whichever server answers. It resets every hour, so a payment can seem to vanish between calls. The buttons above each get their own fresh copy, so that's where the one-charge result comes from. Nothing can make this endpoint fail on purpose, because a planted instruction shouldn't reach a stranger's agent.

What's been checked

Loading the last report.

What this is, and isn't

A demo, not a load test. A button shows one run, and says nothing about production.
Everything behind it is fake, and no model runs here.
Limited to about 60 requests a minute per address and 20,000 a day in total. Past that it answers with an error until the limit resets.
No cookies, analytics or third-party scripts. Your address is only used for the rate limit, and isn't stored.