MemAuthority

Install

Works with Claude Desktop. Read the repository before you give any tool access to your data.

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

4 read · 11 write · 0 delete · 1 not yet classified

Secrets

None asked for

Install scripts

Not scanned yet

Runs as

Downloaded binary

Tools (16)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• memory_append_progress

  Append a dated typed progress entry through the durable Authority transaction without replacing existing progress history.

• memory_archive_project

  Archive one MemAuthority project in current-HEAD lifecycle metadata while preserving its Authority history.

• memory_create_project

  Create a new active MemAuthority project with a program-owned canonical handoff scaffold; no Vault template file is required.

• memory_mark_verified

  Record protected local or runtime verification state through the controlled mutation path after the required evidence has actually been checked.

• memory_migrate_lifecycle

  Perform the one-time legacy MemAuthority lifecycle migration through the transaction kernel; this is a migration operation, not normal project editing.

• memory_project_runtime

  Use this to read stored declarative runtime location, environment, repository, supervisor, check, and boundary metadata for a project. It does not execute checks, inspect the MemAuthority service itself, or prove current live deployment health.

• memory_read

  Use this to read a known handoff, rules, progress, or pitfalls memory resource by URI, optionally by heading or line range. Prefer it directly when the resource URI is already known; it does not read runtime resources. Returns resource-wide sections with exact mutation headings, allowed_operations, protected status and dedicated tools at the returned revision, plus section_creation_hint. Eligible handoff reads also return checklist_items for top-level todos under the optional exact heading 已知问题 / 待办. An empty list means no recorded checklist items, not proof that no work remains.

• memory_record_pitfall

  Idempotently append a typed reusable pitfall entry to project memory without replacing existing pitfalls.

• memory_record_runtime_observation

  Idempotently record a typed runtime conflict or completed fallback as control evidence without mutating project Authority.

• memory_restore_project

  Restore one archived MemAuthority project to active lifecycle state through the controlled mutation path.

• memory_route

  Use this when the target MemAuthority project id is uncertain and you have a project name, alias, or repository identity. It resolves exact NFC-normalized, Unicode-casefolded registered project ids or aliases; do not use it when the project id or resource URI is already known.

• memory_search

  Use this to locate relevant indexed sections inside a known project when the exact memory resource or section is unknown. It returns up to 50 coordinate-like hits for selective reading, not final proof or complete context; truncated=true means additional matches exist. It does not resolve uncertain project identity.

• memory_status

  Use this to inspect the MemAuthority service and Authority workspace itself: Git head, owned snapshot, projection, write gate, fencing, journal, and recovery state. It does not report a project's deployment location or live production service health.

• memory_update_handoff

  Use this for direct replacement of existing ordinary handoff sections with resource CAS. Keep current implementation, confirmed decisions and pending work distinct; progress is execution history and rules are long-term constraints. Copy exact headings from memory_read.sections. Missing sections are not created: use memory_update_sections insert. 核验记录 is protected: use memory_mark_verified. Prefer memory_update_sections for append/insert/delete operations, checklist item changes, or edits outside handoff. Successful relevant state maintenance does not require duplicating content in every role.

• memory_update_runtime

  Description is built at runtime.

Signals

Stars

6

Forks

0

Open issues

0

Last commit

Sep 8, 2026 (1 month ago)

Last release

Sep 8, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.iasi777/memauthority

Version

1.3.2

Auth

No auth

Packages

mcpb https://github.com/iasi777/memauthority/releases/download/v1.3.2/memauthority-1.3.2-win-x64.mcpbmcpb https://github.com/iasi777/memauthority/releases/download/v1.3.2/memauthority-1.3.2-win-arm64.mcpbmcpb https://github.com/iasi777/memauthority/releases/download/v1.3.2/memauthority-1.3.2-linux-x64.mcpbmcpb https://github.com/iasi777/memauthority/releases/download/v1.3.2/memauthority-1.3.2-linux-arm64.mcpbmcpb https://github.com/iasi777/memauthority/releases/download/v1.3.2/memauthority-1.3.2-osx-x64.mcpbmcpb https://github.com/iasi777/memauthority/releases/download/v1.3.2/memauthority-1.3.2-osx-arm64.mcpb

License

Apache-2.0

Repository

github.com/iasi777/memauthority

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql