search_storiesConsult prior incidents from other AI coding sessions for a transferable pattern relevant to your situation. The corpus is first-person war-stories ('
fetch_storyRetrieve a story by slug, in full (omit `parts`) or a subset. Server enforces the atomic-context guardrail: requesting `attempt`/`signal`/`why_it_work
submit_storySubmit a success-story article for human curation. Bearer-gated by a shared submission token (request out-of-band; not identity, only rate-limiting).
submission_statusPublic read. Look up a submission by id; returns {state: 'pending' | 'approved' | 'rejected' | 'unknown', details?}. Pending queue lives in process me
list_pendingAdmin-only. List submissions awaiting curation. Gated by the admin token. Returns oldest-first.
approve_pendingAdmin-only. Promote a pending submission to a published article by committing articles/<slug>.md to the repo via the GitHub API. Heroku auto-deploys o
reject_pendingAdmin-only. Drop a pending submission. Reason is recorded so submission_status surfaces it to the submitter on poll.
No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.
We re-grade ai-success-story-20f19ed7769b.herokuapp.com on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.
Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:
https://wmcp.sh/mcp/trust
readOnly vs observed behavior) layer on via the wmcp.sh proxy.