Klisten FailBox
kr.co.klisten.apiPublished by api.klisten.co.krOfficial publisherv0.1.0Updated Oct 24, 2026
Persist failure simulations. No external fault injection or transfers. Customer key required.
The publisher's own server: Klisten ToolGuard
Overview
Klisten FailBox is a remote MCP server that lets an assistant persist failure simulations, using a product-scoped customer key for access.
- What you can do
- Persist failure simulations so they can be kept and reused across sessions, according to the registry description. The manifest lists no individual tools, so the exact operations are not documented. It performs no external fault injection and no transfers.
- When to use it
- Consider it when you need an assistant to record and keep failure simulations for later reference. It is not intended for injecting faults into external systems or for moving funds or data.
- Requirements
- A remote streamable HTTP endpoint at api.klisten.co.kr. OAuth authentication is required, supplied as an Authorization header carrying a product-scoped customer key. No packages or environment variables are declared.
Installation
In SourceWeft
- Open Klisten FailBox in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/kr.co.klisten.api%2Ffailbox/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"klisten-failbox": {
"type": "http",
"url": "https://api.klisten.co.kr/mcp/failbox"
}
}
}Tools
0Version history
1- v0.1.0LatestOct 12, 2026
Score
56% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
Other Klisten integrations
Klisten ToolGuard
kr.co.klisten.apiOfficial publisher
Lets an assistant look up ToolGuard paid gate decisions and attestation records.
Klisten ToolRank
kr.co.klisten.apiOfficial publisher
Lets an assistant search the Klisten tool catalog through a remote endpoint, using a customer API key.
Klisten SchemaShield
kr.co.klisten.apiOfficial publisher
Lets an assistant store and compare organization JSON snapshots through a remote, key-authenticated endpoint.
Klisten MeterMCP
kr.co.klisten.apiOfficial publisher
Remote MCP endpoint that lets an assistant read your organization's Klisten usage records using a customer API key.
Klisten DeadlineEngine
kr.co.klisten.apiOfficial publisher
Remote Klisten endpoint that lets an assistant compute explicit durations, authenticated with a product-scoped customer API key.