Skip to main content
Glama
davidnichols-ops

aafp-commons

by davidnichols-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to aafp-commons

No user-submitted related servers found.

    Related Servers

    • Living Stack Community

      equinoxaifinance-rgb
      A
      license
      A
      quality
      B
      maintenance
      Free seven-tool proof loop for MCP agents: scoped sessions, bounded authorization, typed outcomes, evidence-bound claims, and tamper-evident local closure. Upgrade to Complete Local for durable memory, recovery, signed traces, release verification, and multi-agent workflows.
      7
      Apache 2.0

    • Witness

      MaximilianoColoma
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides evidence-oriented MCP service for cryptographically identified agents, bounded public contracts, privacy-preserving records, and append-only audit.
      Apache 2.0

    • Living Stack MCP — Retired

      equinoxaifinance-rgb
      A
      license
      A
      quality
      B
      maintenance
      Retired snapshot of the former 15-tool Apache-2.0 beta. Use Living Stack Community for the free seven-tool proof edition; Complete Local is the paid runtime with memory, recovery, signed traces, release verification, and multi-agent workflows.
      14
      Apache 2.0

    • claimbase

      4-R-C-4-N-4
      A
      license
      A
      quality
      B
      maintenance
      Provides a compiled knowledge substrate, extracting atomic claims from an append-only capture log and querying a bitemporal claim graph over MCP. Read-only by default, with opt-in writes for trusted sources.
      4
      MIT

    • cairn

      veridian69
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables self-hosted, provenance-aware shared memory with scoped access, attributed observations, correction history, disagreement tracking, and durable idempotent writes for humans and AI agents via REST and MCP.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 7 tools

    Disambiguation4/5

    The read tools are separated by scope: world reads the whole signed world, query searches by packet ID or namespace, and get retrieves one content-addressed packet. Conflicts and resolutions are clearly distinct read endpoints, though query and get could still cause minor selection hesitation.

    Naming Consistency3/5

    All tools share the commons_ prefix, which establishes a strong family identity. However, suffixes mix nouns like world, conflicts, and resolutions with verbs like query, get, and propose, so the set is readable but not a uniform verb_noun convention.

    Tool Count5/5

    Seven tools is well-scoped for a signed-packet commons governance domain. Each tool has a distinct role without redundant operations.

    Completeness3/5

    Core read, query, propose, and conflict/resolution read operations are covered. However, prerequisites such as commons init, evidence management, and constitution setup or updates have no MCP-visible tools, leaving meaningful gaps in the write/propose workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources