OneTool MCP MCP server
Checked 2026-09-08. Alive: yes. Handshake: not available.
Category: ai-ml. API and field schema.
Facts
| id | beycom--onetool-mcp |
| name | OneTool MCP |
| registry_name | io.github.beycom/onetool-mcp |
| repo_url | https://github.com/beycom/onetool-mcp |
| endpoint_url | not available |
| transport | unknown |
| alive | yes |
| liveness_reason | not available |
| check_reachable | yes |
| check_recent_commit | yes |
| check_installable | yes |
| handshake_status | not available |
| handshake_checked_at | not available |
| handshake_protocol_version | not available |
| handshake_auth_hint | not available |
| handshake_auth_discoverable | not available |
| handshake_failure_layer | not available |
| handshake_latency_ms | not available |
| handshake_tools_state | not available |
| handshake_tool_count | not available |
| maintenance_status | active |
| last_commit_at | 2026-09-01T08:38:01Z |
| category | ai-ml |
| license_spdx | GPL-3.0 |
How to install or connect
Connect using the published unknown transport; installation metadata is available through the API.
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.