io.github.ejentum/self-inspect-mcp MCP server
Checked 2026-09-07. Alive: yes. Handshake: verified.
Category: ai-ml. API and field schema.
Facts
| id | ejentum--self-inspect-mcp |
| name | io.github.ejentum/self-inspect-mcp |
| registry_name | io.github.ejentum/self-inspect-mcp |
| repo_url | https://github.com/ejentum/self-inspect-mcp |
| endpoint_url | https://api.ejentum.com/self-inspect-mcp |
| transport | mixed |
| alive | yes |
| liveness_reason | not available |
| check_reachable | yes |
| check_recent_commit | yes |
| check_installable | yes |
| handshake_status | verified |
| handshake_checked_at | 2026-09-07T18:04:14Z |
| handshake_protocol_version | 2025-06-18 |
| handshake_auth_hint | not available |
| handshake_auth_discoverable | not available |
| handshake_failure_layer | none |
| handshake_latency_ms | 2797 |
| handshake_tools_state | listed |
| handshake_tool_count | 1 |
| maintenance_status | slow |
| last_commit_at | 2026-06-13T07:39:43Z |
| category | ai-ml |
| license_spdx | MIT |
How to install or connect
Connect your MCP client to https://api.ejentum.com/self-inspect-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.