Skip to main content
Glama
lucaslubi

fidacy-mcp

by lucaslubi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to fidacy-mcp

No user-submitted related servers found.

    Related Servers

    • Cerberus

      lz-123123
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a three-layer payment firewall for AI agents, enabling identity verification, risk screening, and execution authorization with on-chain policy enforcement for secure and auditable transactions.
      99 npm
      2
      MIT

    • pop-pay

      100xPercent
      A
      license
      Not graded
      quality
      D
      maintenance
      Stop AI agents leaking your card or making hallucinated purchases. No SaaS, No login, Fully local. A runtime security layer that protects AI agents during online purchases. It sits between the agent and payment forms
      187 npm
      1
      MIT

    • wwall

      axdvdv
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to propose wallet payments while a local, human-authored policy decides whether each transaction is approved, requires human confirmation, or is refused, and records every decision in a signed, append-only ledger.
      -

    • drift

      mrpkk
      A
      license
      Not graded
      quality
      B
      maintenance
      Continuous mandate enforcement for AI agents: block an action a signed mandate does not permit — amount, payee, audience, expiry — and name the rule that fired. Verdicts are Ed25519-signed and verify offline.
      Apache 2.0
    • emilia-mcp-server by emiliaprotocol

      emilia-mcp-serverofficial

      emiliaprotocol
      A
      license
      A
      quality
      A
      maintenance
      The accountability layer for AI agents — a named human's signed yes before an agent does anything irreversible (payment, record change, deploy), then an offline-verifiable Trust Receipt. Apache-2.0, formally verified.
      3
      600
      Apache 2.0

    • Openterms-mcp

      jstibal
      A
      license
      A
      quality
      C
      maintenance
      Cryptographic proof of consent for AI agents. Sign before you act. Policy engine enforces spending caps, action whitelists, and escalation rules. Independently verifiable by anyone.
      10
      2
      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

    A4.2/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., request_payment vs assess_action vs anchor_artifact), but the read-only audit/reporting tools (spend_summary, list_decisions, explain_decision) overlap somewhat. Descriptions help differentiate them, but an agent could still mis-select between spend_summary and list_decisions.

    Naming Consistency4/5

    The dominant pattern is verb_noun (request_payment, verify_mandate, get_audit_proof, etc.). However, 'sentinel_alerts' is a noun phrase and 'upgrade' is a bare verb, breaking the otherwise consistent style.

    Tool Count5/5

    12 tools is well within the optimal 3-15 range. Each tool targets a specific aspect of the payment authorization, audit, artifact proofing, or account lifecycle, and none feel redundant or superfluous.

    Completeness4/5

    The main workflows are covered: payment authorization with mandates, audit trails, decision explanations, alerts, artifact anchoring/checking, and account upgrade/email registration. Slight gaps like no way to list all anchored artifacts or revoke an anchor are minor and likely beyond the server's intended scope.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources