Participation request: MCP Verify archive log (staging)
Hello Witness Network maintainers, I would like to add a log to the witness network. Origin line: mcpverify.ai/archive/v1 Public key: mcpverify.ai/archive/v1+f5d9c8d0+AZ0GwtwS941FiviqZwM4j/UKN/YiUO3rZawJimXMIfMc Checkpoint URL: https://mcpverify.ai/proof/checkpoint.txt Public key URL: https://mcpverify.ai/proof/log.pub Add-checkpoint rate: at most 24 per day, and in practice far less. Log list: staging/log-list-10qps-4klogs.1 Operator: MCPVerify Labs Contact: contact@mcpverify.ai Expected lifetime: indefinite; the origin line is frozen and the archive is append-only by design. Purpose. The log is the append-only record behind MCP Verify, an archive of Model Context Protocol server reliability measurements. It commits one leaf per daily snapshot, in insertion order, as an RFC 6962 tree. Checkpoints are C2SP tlog-checkpoint format, signed with Ed25519 under signed-note type byte 0x01. The key name is the same string as the origin line, so the log-list entry can omit its `origin` line. Rate. Snapshots are captured daily and unattended, but checkpoints are signed by a human, at most about once a week. The figure above is a ceiling rather than an expected rate: it allows for a second signing in a day, the documented zero-size bootstrap request alongside the real submission, one retry, and headroom for a manual debugging session. Steady-state load is a couple of requests a week. What has been exercised. I have run the tlog-witness protocol end to end against a witness of my own before writing to you: a real signed checkpoint of this log was submitted, cosigned, and the cosignature verified per tlog-cosignature. Each documented response condition was exercised individually, including the zero-size bootstrap and its 409 reply. No third-party witness has been contacted and none has cosigned this log. I would like the staging list rather than testing: this is a real log with real usage and I am happy to dogfood staging. Happy to adjust the rate, or to take a different list, if either would suit the network better. Thank you, MCPVerify Labs
participants (1)
-
contact