Docs
twiceshy speaks MCP. Wire your agent to it once and every session after that checks the corpus of validated dead-ends before it retries something that has already failed for someone else.
Quickstart
First, get a free alpha token — it takes 5 seconds and is shown once.
Claude Code
claude mcp add -t http twiceshy https://api.twiceshy.dev \
--header "Authorization: Bearer YOUR_TOKEN"
Cursor
{
"mcpServers": {
"twiceshy": {
"url": "https://api.twiceshy.dev",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}
Any MCP client
Endpoint https://api.twiceshy.dev, header Authorization: Bearer YOUR_TOKEN. Any client that speaks streamable-HTTP MCP works — Windsurf, VS Code, or your own.
What your agent gets
A record looks like this — served in milliseconds, before your agent burns a retry on something already known to fail:
SQLite FTS5 MATCH treats user input as query syntax — dots, dashes and quotes error out or change semantics
The trap: passing raw text to MATCH errors on punctuation or silently changes meaning.
The escape: quote every token — quoted strings are always plain terms.
- the trap, in plain words
- the escape that actually worked
- validated before it can ever reach your agent
Every card carries four fields: the trap (what goes wrong and why), the escape (the fix that actually worked), provenance (where it came from), and a trust level (how it earned its way into the corpus). Nothing is served without all four.
How records are validated
Records land quarantined. A deterministic consistency gate checks structure and internal contradictions. Then two AI judges from different model vendors must independently approve the record — agreement across vendors, not just a second opinion from the same lab. Approved records sit in a human veto window before they ever reach an agent. Rejected records stay quarantined permanently — they are never retried into the served corpus. The corpus grows nightly; nothing reaches you unvalidated.
Tokens, quotas & limits
| Limit | Value |
|---|---|
| Calls per day | 1,000 |
| Calls per minute | 60 |
| Token visibility | shown once, at signup |
| Abuse handling | token revoked; request a new one |
Lost your token, or need a new one? Sign up again — each signup issues a fresh token.
FAQ
Is my code sent anywhere?
Only your queries — the text your agent sends when it asks for help. Nothing is stored from pull calls beyond telemetry. See the terms & data policy.
Does it work with my agent?
Any MCP client — Claude Code, Cursor, Windsurf, VS Code, or a custom one you wrote yourself.
What does it cost?
Free while in alpha. Self-hosting the AGPL-3.0 code is free, forever, regardless of what the hosted service charges later.
Can I contribute my own traps?
The write path opens later in the alpha. For now the corpus grows from validated internal sessions.
Who builds this?
A small team that got tired of watching agents repeat the same dead-ends and decided to write them down.