STEMEvidence & freshness
STEM compatibility and verification evidence
See which STEM host workflows have been tested, which have documented setup, the recorded dates, and the limits of that evidence.
Documentation reviewed . Host verification dates are listed separately.
Documentation reviewed on . A documentation review is not a new runtime test. The workflow dates below summarize existing maintainer verification records; the examples elsewhere in these docs are synthetic exercises, not additional test results.
| Client | Status | Recorded host test | Evidence scope and limits |
|---|---|---|---|
| ChatGPT | tested workflow | 2026-10-24 | Published ChatGPT web connector: OAuth, current memory permission, an explicitly approved synthetic save, same-chat recall, fresh-chat recall and cross-client recall. No claim about mobile clients, refresh rotation or automatic saving on every turn. |
| Claude | tested workflow | 2026-10-25 | Existing Claude remote connector: Current memory permission, an explicitly approved synthetic save, same-chat recall, fresh-chat recall and cross-client recall. One existing host connection was exercised. Claude Code, mobile clients and every historical registration were not separately tested. |
| Gemini | tested workflow | 2026-10-25 | Existing Gemini custom app using Flash: Current memory permission, an explicitly approved synthetic save, same-chat recall, fresh-chat recall and cross-client recall. Other model choices did not all complete the workflow. Per-write host approval may apply. Mobile behavior and refresh rotation were not verified. |
| Cursor | documented setup | No host test recorded | Cursor: Setup documentation reviewed; no completed STEM host workflow is asserted. Remote HTTP and OAuth setup follows Cursor documentation; verify your connection with a tool call. |
| Muse / Muse Code | documented setup | No host test recorded | Muse / Muse Code: Setup documentation reviewed; no completed STEM host workflow is asserted. Muse consumer MCP compatibility is unverified. Muse Code has a separate documented setup. |
| Grok / Grok Bot | documented setup | No host test recorded | Grok / Grok Bot: Setup documentation reviewed; no completed STEM host workflow is asserted. Grok chat documents custom MCP connectors. Grok Bot compatibility must be checked separately. |
| Other MCP clients | documented setup | No host test recorded | Other MCP clients: Setup documentation reviewed; no completed STEM host workflow is asserted. Use a client with remote Streamable HTTP and OAuth with dynamic client registration. |
What the labels mean
Tested workflow means the described connection completed an authorized save and later recall. It is evidence for that surface and time, not certification of every plan, model, device or future release. Documented setup means configuration instructions are available; the configuration alone does not prove a successful connection.
The Muse / Muse Code card describes documented Muse Code setup. Muse consumer compatibility remains unverified. Grok chat's documented connector does not establish Grok Bot compatibility.
Verify your own connection
Run the harmless save-and-recall check. Keep the successful tool result and the actual returned memory ID, then confirm recall in a fresh conversation or another connected host. If you report an issue, include the client/version, date and non-sensitive error text; do not send tokens, private memories or sign-in codes.
The capability manifest carries the same dates and scope. The developer checks separately evaluate protocol behavior; synthetic local checks do not establish live model quality or host compatibility.
← Back to the agent hub · Machine-readable tool schemas