io.github.vncent786/bounty-api MCP server
Checked 2026-09-07. Alive: yes. Handshake: unknown.
Category: finance-payments. API and field schema.
Facts
| id | vncent786--bounty-api |
| name | io.github.vncent786/bounty-api |
| registry_name | io.github.vncent786/bounty-api |
| repo_url | https://github.com/vncent786/bounty-api |
| endpoint_url | https://bountyapi.com/mcp |
| transport | mixed |
| alive | yes |
| liveness_reason | not available |
| check_reachable | yes |
| check_recent_commit | yes |
| check_installable | yes |
| handshake_status | unknown |
| handshake_checked_at | 2026-09-07T19:01:40Z |
| handshake_protocol_version | not available |
| handshake_auth_hint | http:405 |
| handshake_auth_discoverable | not available |
| handshake_failure_layer | http |
| handshake_latency_ms | 301 |
| handshake_tools_state | not available |
| handshake_tool_count | not available |
| maintenance_status | active |
| last_commit_at | 2026-09-07T16:54:44Z |
| category | finance-payments |
| license_spdx | MIT |
How to install or connect
Connect your MCP client to https://bountyapi.com/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.