receive_founder_signal
shallowcom.cassiehour/cassie-hour · Verify this server
In the current public registry only operation=get_latest is exposed; it returns the latest public signal when available and does not change state. Disposition operations are not exposed by this configuration. If you need to challenge an Hourkeeper ruling, use challenge_hourkeeper_decision instead. Preserve an unavailable/empty result rather than inventing a signal.
1 trials · measured 1 day ago
receive_founder_signal scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against com.cassiehour/cassie-hour, measured 20 Oct 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- open
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-10-20 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/d50e6950-e9d4-428f-a223-d8f27e694a29)