JP Bids MCP MCP server
Checked 2026-09-07. Alive: yes. Handshake: unknown.
Category: legal-compliance. API and field schema.
Facts
| id | sugukurukabe--koko-call-mcp |
| name | JP Bids MCP |
| registry_name | io.github.sugukurukabe/jp-bids |
| repo_url | https://github.com/sugukurukabe/koko-call-mcp |
| endpoint_url | https://mcp.bid-jp.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-07T18:59:36Z |
| handshake_protocol_version | not available |
| handshake_auth_hint | http:400 |
| handshake_auth_discoverable | not available |
| handshake_failure_layer | http |
| handshake_latency_ms | 297 |
| handshake_tools_state | not available |
| handshake_tool_count | not available |
| maintenance_status | active |
| last_commit_at | 2026-08-29T16:37:02Z |
| category | legal-compliance |
| license_spdx | Apache-2.0 |
How to install or connect
Connect your MCP client to https://mcp.bid-jp.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.