Failsafe MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Failsafe MCP Serverrun health checks on all providers"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Failsafe MCP Server
Credential resilience for AI agents.
Your agent runs on 50+ credentials. Failsafe makes sure they never break.
🔑 Store credentials with AES-256 encryption
🏥 Monitor health with automatic provider-specific checks
🔀 Failover to backup credentials when primary fails
⏰ Warn before credentials expire
🔌 MCP native — works with Claude Code, Cursor, LangChain, and any MCP client
Quick Start
With Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"failsafe": {
"command": "npx",
"args": ["-y", "failsafe-mcp-server"]
}
}
}With Claude Code
claude mcp add failsafe -- npx -y failsafe-mcp-serverManual
npm install -g failsafe-mcp-server
failsafe-mcp-serverRelated MCP server: API Locker
What It Does
Store a credential
> failsafe_store provider:"openai" key:"sk-abc123" backup_key:"sk-xyz789"
✓ Credential stored for openai. Backup configured.Get a credential (with auto-failover)
> failsafe_get provider:"openai"
{
"key": "sk-abc123",
"source": "primary",
"status": "healthy"
}If the primary key is unhealthy, Failsafe automatically returns the backup:
> failsafe_get provider:"openai"
{
"key": "sk-xyz789",
"source": "backup",
"warnings": ["Primary credential is unhealthy. Using backup."]
}List all credentials
> failsafe_list
{
"summary": { "total": 4, "healthy": 3, "unhealthy": 1, "expired": 0 },
"credentials": [
{ "provider": "openai", "status": "healthy", "has_backup": true },
{ "provider": "anthropic", "status": "healthy", "has_backup": false },
{ "provider": "github", "status": "unhealthy", "has_backup": true },
{ "provider": "stripe", "status": "healthy", "has_backup": false }
]
}Run health checks
> failsafe_health
{
"summary": { "total": 4, "healthy": 3, "unhealthy": 1 },
"results": [
{ "provider": "openai", "status": "healthy", "latency_ms": 245 },
{ "provider": "anthropic", "status": "healthy", "latency_ms": 189 },
{ "provider": "github", "status": "unhealthy", "response_code": 401 },
{ "provider": "stripe", "status": "healthy", "latency_ms": 312 }
]
}Supported Providers
Built-in health checks for:
Provider | Health Check Endpoint |
OpenAI |
|
Anthropic |
|
GitHub |
|
Stripe |
|
Any other provider works with a custom health_check_url:
> failsafe_store provider:"my-saas" key:"token_abc" health_check_url:"https://api.my-saas.com/health"Security
All credentials encrypted with AES-256-GCM at rest
Master key auto-generated and stored in
~/.failsafe/master.key(mode 0600)Or set
FAILSAFE_MASTER_KEYenvironment variable100% local — credentials never leave your machine
No telemetry, no network calls except health checks to your own providers
How Failover Works
Agent requests credential for "openai"
↓
Failsafe checks primary key status
↓
├─ Healthy? → return primary key
├─ Unhealthy/Expired? → check for backup
│ ├─ Backup exists? → return backup key + warning
│ └─ No backup? → return primary key + warningData Storage
All data stored locally in ~/.failsafe/:
~/.failsafe/
├── master.key # Encryption key (auto-generated)
└── credentials.json # Encrypted credential storeRoadmap
Store / Get / List / Remove credentials
AES-256-GCM encryption
Health checks (OpenAI, Anthropic, GitHub, Stripe + custom)
Automatic failover (primary → backup)
Expiration warnings
Background health monitoring (cron)
Multi-key rotation / load balancing
Webhook notifications (Slack, Telegram)
Failsafe Cloud (hosted dashboard + team management)
License
MIT
Links
Website: failsafe.world
Twitter: @climber_sun
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityCmaintenanceSelf-hosted credential store and API proxy for AI agents. One Bearer token, all your services. Handles OAuth refresh, encrypted storage, audit logging, and per-agent permissioning.Last updated32MIT
- Alicense-qualityDmaintenanceEncrypted credential vault with a 21-tool MCP server. Store and manage LLM API keys, service API keys, and OAuth credentials — then let your AI agent list, reveal, rotate, rename, pause, and proxy calls through them.Last updatedMIT
- Alicense-qualityBmaintenanceSecure credential management for AI agents — encrypted storage, auto-refresh, and rate limiting via a single MCP call. Supports OpenAI, Anthropic, Stripe, GitHub, Brave Search, Kalshi, Coinbase, plus generic API key and OAuth2 for any service.Last updated43MIT
- Alicense-qualityBmaintenanceLocal, encrypted credential vault for AI agents that enables secure multi-account management across services like Supabase, GitHub, Vercel, and Stripe, allowing seamless account switching without restarting the chat client.Last updated392MIT
Related MCP Connectors
Encrypted secret store and rotation for autonomous agent credentials
Free self-serve Agent Passports for AI agents: signed, portable, offline-verifiable credentials.
Agent payments, API key vaulting, and governed mandates. Agents spend within user-defined limits.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sunglc/failsafe-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server