Skip to content

MyMCP 0.2.0: public-host cutover

Latest
Latest

Choose a tag to compare

View all tags
@flyset flyset released this 26 Jul 13:22
mymcp-v0.2.0
c2852bc

MyMCP 0.2.0: public-host cutover

MyMCP public host

MyMCP/mymcp 0.2.0 establishes MyMCP as the public host: the endpoint and
server marker, FastAPI application, Python distribution and package, canonical
repository, and tracked OpenCode connection and agent use MyMCP/mymcp.

The canonical repository is https://github.com/flyset/MyMCP. The former
repository URL redirects to it.

Compatibility preserved

  • Routes and MCP protocol remain unchanged: /mcp, /health, /version, and
    host-owned list_tools.
  • Mnemosyne remains bundled plugin mnemosyne at version 0.1.0.
  • All memory_* Tool names, schemas, ordering, results, errors, and mutation
    gates remain compatible.
  • MNEMOSYNE_*, ~/.mnemosyne, memory storage, record formats and paths,
    content-free logging, and explicit consent semantics remain preserved.
  • The tracked OpenCode policy remains deny-first: mymcp_* is denied, exactly
    four read-only Tools are allowed, and the five exact mutation Tools require
    ask.

Verification evidence

  • Candidate commit: be7b7c6.
  • Automated verification: 1,139 tests in the full suite and two packaging tests
    passed.
  • Wheel SHA-256:
    531cc9a603d16399b12650fd09d3bc76f43b4d5d1b15fed0377a6197c820e3e7.
  • Repository verification confirmed the canonical origin, history, tag state,
    and release placeholder; the former repository URL redirects to the canonical
    repository.
  • The tracked and ignored OpenCode migration is complete, with Claude
    configuration excluded.
  • The normal MyMCP endpoint and final client reconnect were verified.
  • Isolated operational checks passed: one exact mutation call was approved once,
    and one rejected mutation made no Tool call. Neither check created or changed
    the isolated memory root.

Release tag

Annotated tag mymcp-v0.2.0 targets verified source commit c2852bc.

Deferred work

Native external plugin installation, activation, and isolation; lifecycle
publication; and client-neutral gateway governance remain deferred. No claim is
made that those capabilities are implemented or released.

Assets 3
Loading