Skip to main content
Glama
AffixIO

Affixio MCP

Official

Related Servers

Alternatives to Affixio MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to sign and verify actions with ML-DSA-65 digital signatures, providing tamper-proof receipts that can be verified offline without any secrets.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides tools to sign and verify post-quantum attestations of AI agent actions (mint, trajectory, coherence) using ML-DSA-65 signatures, with offline verification always free.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to run side-effecting actions like tool calls, file writes, and payments only when each exact set of arguments is covered by a signed, scoped, single-use permit verified server-side, with high-risk actions requiring human sign-off and every allow/deny recorded in a tamper-evident hash-chained ledger.
      3
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to sign action records locally, publish them to a public log, and retrieve tamper-evident proofs that anyone can verify offline.
      411 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to verify proposed actions through federated adversarial consensus among multiple LLMs, providing Ed25519-signed attestations to prevent hallucinations, unverified counterparties, and compliance risks before execution.
      1
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      Enables local spend caps and Ed25519-signed provenance receipts for AI agent tool calls, allowing any MCP host to gate model usage and independently verify signed decisions without sending prompts or content.
      6
      0
      -

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct stage in the attestation workflow: gating a tool call, recording an action, and verifying an attestation. There is no ambiguity between them, as the verb and noun clearly separate purposes.

    Naming Consistency5/5

    All three tool names follow a consistent verb_noun pattern: gate_tool_call, attest_action, verify_action. This makes the naming predictable and easy to reason about.

    Tool Count5/5

    With only three tools, the server is tightly scoped to its attestation/gating purpose without unnecessary bloat. Each tool serves a necessary role in the workflow.

    Completeness5/5

    The tool set covers the full lifecycle of attestation: gating a call, creating an attestation, and verifying it. No obvious gaps exist for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues