compuute-scan-api
https://scan.compuute.seMCP-specific static security scanner for agents. Scan any public GitHub MCP-server repo and get severity counts, score, top findings, and a triage disclaimer. 37 L1 rules across TS/JS, Python, Go, Rust, C#, Java, Kotlin. Threat-intel response cadence: new rules added within one week of published CVE classes (see compuute-scan v0.6.2's L1-038 for the Ox Security npx-argument-injection vector).
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 487ms · p95 552msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 8/8/2026, 12:00:00 AM | 100% | 1 | 397ms |
| 8/9/2026, 12:00:00 AM | 100% | 1 | 392ms |
| 8/10/2026, 12:00:00 AM | 100% | 1 | 430ms |
| 8/11/2026, 12:00:00 AM | 100% | 1 | 444ms |
| 8/12/2026, 12:00:00 AM | 100% | 1 | 407ms |
| 8/13/2026, 12:00:00 AM | 100% | 1 | 545ms |
| 8/14/2026, 12:00:00 AM | 100% | 1 | 531ms |
| 8/15/2026, 12:00:00 AM | 100% | 1 | 448ms |
| 8/16/2026, 12:00:00 AM | 100% | 1 | 387ms |
| 8/17/2026, 12:00:00 AM | 100% | 1 | 413ms |
| 8/18/2026, 12:00:00 AM | 100% | 1 | 479ms |
| 8/19/2026, 12:00:00 AM | 100% | 20 | 452ms |
| 8/20/2026, 12:00:00 AM | 100% | 21 | 428ms |
| 8/21/2026, 12:00:00 AM | 100% | 22 | 468ms |
| 8/22/2026, 12:00:00 AM | 100% | 22 | 448ms |
| 8/23/2026, 12:00:00 AM | 100% | 21 | 457ms |
| 8/24/2026, 12:00:00 AM | 100% | 20 | 496ms |
| 8/25/2026, 12:00:00 AM | 100% | 16 | 464ms |
| 8/26/2026, 12:00:00 AM | 100% | 10 | 406ms |
| 8/27/2026, 12:00:00 AM | 100% | 13 | 417ms |
| 8/28/2026, 12:00:00 AM | 100% | 21 | 507ms |
| 8/29/2026, 12:00:00 AM | 100% | 21 | 504ms |
| 8/30/2026, 12:00:00 AM | 100% | 21 | 444ms |
| 8/31/2026, 12:00:00 AM | 100% | 20 | 462ms |
| 9/1/2026, 12:00:00 AM | 100% | 21 | 501ms |
| 9/2/2026, 12:00:00 AM | 100% | 21 | 482ms |
| 9/3/2026, 12:00:00 AM | 100% | 21 | 504ms |
| 9/4/2026, 12:00:00 AM | 100% | 20 | 442ms |
| 9/5/2026, 12:00:00 AM | 100% | 21 | 441ms |
| 9/6/2026, 12:00:00 AM | 100% | 14 | 498ms |
- Availability
- 100
- Latency
- 93
- Security
- 100
- Transparency
- 36
- Activity
- not yet measured
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- —
- Networks
- —
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- —
- Domain registered
- —
- Hosting network
- RLWY-HIKARI-01
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.