Skip to main content
Glama
mrpkk

nidhipati

by mrpkk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to nidhipati

No user-submitted related servers found.

    Related Servers

    • open-mandate

      RayanSDDS
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to inspect, check, and audit signed offline spending authorizations, and to issue hash-chained receipts for each action taken against them. Enforces per-transaction, total, expiry, merchant, and human-approval constraints, returning allow, needs_human, or deny with the specific failing constraint.
      Apache 2.0

    • mesa-mcp

      BenyFridY
      A
      license
      A
      quality
      B
      maintenance
      Enables agents to query a read-only ledger of machine payments, exposing tools for spending totals, purchases with event chains, verdicts, payer passports, and fiscal reporting data.
      7
      MIT

    • cedulon

      dogrucanemek-alt
      A
      license
      A
      quality
      B
      maintenance
      Policy-gated agent spend with signed receipts and rail-extract audit: a fail-closed gate issues a COSE receipt for every allowed payment, and the audit reconciles those receipts against a rail extract so a settlement with no receipt is named rather than assumed. It settles on a mock rail, holding no wallet and signing no transaction.
      5
      1
      Apache 2.0

    • mitracore

      mrpkk
      A
      license
      Not graded
      quality
      B
      maintenance
      Trust layer for agent work: verify the artifact an AI agent produced, meter what the run actually cost, and keep the agent inside its mandate. Signed receipts verify offline. 20 checks/day free, then 0.005 USDC per call or $49 per environment per month. Locales: en, hi.
      MIT

    • exchange-truth

      tonyderide
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to independently audit a trading bot's exchange account read-only, cross-checking raw exchange positions and orders against bot beliefs to surface missing or undersized stop losses, ghost trades, duplicate or orphaned orders, and size mismatches, with a hash-sealed attestation record for disputes and post-mortems. It never places, edits, or cancels orders, and reports a critical failure rather than a false clean result when the exchange cannot be read.
      MIT
    • vantic-mcp by vanticlabs

      vantic-mcpofficial

      vanticlabs
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP hosts to verify agent spending mandates and receipts, providing stateless tools for authorization, chain verification, credential verification, and DID resolution.
      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.1/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools target clearly distinct financial verification tasks: reserve NAV, resolver-source validation, receipt checking, invoice reconciliation, and spend auditing. The main possible confusion is between reserve_report and resolve_report because both share the _report suffix and sound like generic reporting tools, though their descriptions clarify the domains.

    Naming Consistency4/5

    The set mostly follows a snake_case verb_noun or action_object pattern: resolve_report, verify_receipt, reconcile_books, audit_spend. reserve_report is slightly less action-oriented, but the overall convention remains readable and predictable.

    Tool Count5/5

    Five tools is well-scoped for a focused financial verification and audit server. Each tool covers a distinct check rather than padding the surface with redundant operations.

    Completeness4/5

    The surface covers reserve backing, source resolution, receipt proof, invoice reconciliation, and spend auditing, forming a coherent verification lifecycle. Minor gaps may exist around ancillary lookup or evidence-retrieval operations, but the core domain is well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources