Teamfight Tactics MCP Server MCP server
Checked 2026-09-07. Alive: no. Handshake: unknown.
Category: other. API and field schema.
Facts
| id | registry--com.mr-bridge--tft-mcp-server |
| name | Teamfight Tactics MCP Server |
| registry_name | com.mr-bridge/tft-mcp-server |
| repo_url | not available |
| endpoint_url | https://mrbridge--tft-mcp-server.apify.actor/mcp |
| transport | streamable-http |
| alive | no |
| liveness_reason | stale |
| check_reachable | yes |
| check_recent_commit | no |
| check_installable | yes |
| handshake_status | unknown |
| handshake_checked_at | 2026-09-07T18:28:39Z |
| handshake_protocol_version | not available |
| handshake_auth_hint | http:401 |
| handshake_auth_discoverable | not available |
| handshake_failure_layer | jsonrpc |
| handshake_latency_ms | 2281 |
| handshake_tools_state | not available |
| handshake_tool_count | not available |
| maintenance_status | unknown |
| last_commit_at | not available |
| category | other |
| license_spdx | not available |
How to install or connect
Connect your MCP client to https://mrbridge--tft-mcp-server.apify.actor/mcp.
What the checks mean
alive combines the applicable repository, package, and endpoint checks. A null result is not verifiable, not a failure. The MCP handshake is a separate structural probe and is not a security audit. Read the methodology.