Jet Tracker MCP server

Checked 2026-09-07. Alive: no. Handshake: gated.

Category: other. API and field schema.

Facts
idregistry--br.com.jettracker--jet-tracker
nameJet Tracker
registry_namebr.com.jettracker/jet-tracker
repo_urlnot available
endpoint_urlhttps://jettracker.com.br/api/mcp
transportstreamable-http
aliveno
liveness_reasonstale
check_reachableyes
check_recent_commitno
check_installableyes
handshake_statusgated
handshake_checked_at2026-09-07T18:16:08Z
handshake_protocol_versionnot available
handshake_auth_hintBearer realm="jettracker", error="invalid_token", error_description="Sign in via OAuth or use Authorization: Bearer <jtpk_...>", resource_metadata="https://jettracker.com.br/.well-known/oauth-protected-resource/api/mcp", scope="mcp"
handshake_auth_discoverableresource_metadata
handshake_failure_layernone
handshake_latency_ms2186
handshake_tools_statenot available
handshake_tool_countnot available
maintenance_statusunknown
last_commit_atnot available
categoryother
license_spdxnot available
How to install or connect

Connect your MCP client to https://jettracker.com.br/api/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.