Remote MCP · Endpoint
build.naru/contract-compass MCP server
No. build.naru/contract-compass answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://contract.naru.build/mcp
The last check completed an MCP handshake.
- Registry name
- build.naru/contract-compass
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 737 ms
- Tools exposed
- 11 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Korean public procurement law: rule-engine rulings, statutes search, live court precedents
- Website
- https://contract.naru.build/
- Listing
- From the official MCP registry (deprecated).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 737 ms |
| 1 day ago | Handshake completed | 706 ms |
| 2 days ago | Handshake completed | 730 ms |
| 3 days ago | Handshake completed | 769 ms |
| 4 days ago | Handshake completed | 705 ms |
| 5 days ago | Handshake completed | 755 ms |
| 7 days ago | Handshake completed | 1.52 s |
| 10 days ago | Handshake completed | 726 ms |
| 12 days ago | Handshake completed | 744 ms |
| 15 days ago | Handshake completed | 981 ms |
| 17 days ago | Handshake completed | 299 ms |
| 19 days ago | Handshake completed | 726 ms |
| 21 days ago | Handshake completed | 696 ms |
| 23 days ago | Handshake completed | 295 ms |
| 25 days ago | Handshake completed | 270 ms |
| 26 days ago | Handshake completed | 703 ms |
| 28 days ago | Handshake completed | 731 ms |
| 29 days ago | Handshake completed | 290 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with build.naru/contract-compass and makes no claim about it beyond what these checks measured.