Deadchannel vs Stripe AI
A side-by-side look at the Deadchannel and Stripe AI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Deadchannel for finance & fintech work as a local process; choose Stripe AI for finance & fintech over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Deadchannel when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
Choose Stripe AI when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 41/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 1,966 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Deadchannel | View Stripe AI |
Tools & capabilities
Deadchannel tools
No tool names declared yet. Check the project README from the listing page.
Stripe AI tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Deadchannel
{
"mcpServers": {
"deadchannel": {
"command": "npx",
"args": [
"-y",
"hosaka-mcp"
]
}
}
}
Stripe AI
{
"mcpServers": {
"mcp-146": {
"url": "https://mcp.stripe.com"
}
}
}
Frequently asked questions
Deadchannel is categorized under Finance & Fintech and uses a local stdio subprocess. Stripe AI belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick Deadchannel for finance & fintech work and Stripe AI for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Deadchannel has no declared pricing — check the project's own site. Stripe AI has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add deadchannel and mcp-146 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Deadchannel has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Stripe AI has 49/100 (Fair) with 5 views, 0 installs and 1,966 GitHub stars.