Skip to main content
Glama
Mangomunchr

FARPY

by Mangomunchr
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

Related Servers

Alternatives to FARPY

No user-submitted related servers found.

    Related Servers

    • HyperFrames Render MCP

      clauxel
      F
      license
      Not graded
      quality
      D
      maintenance
      Paid remote MCP for rendering hyperframe videos with structured receipts and audit logs. Enables rendering, status checking, artifact fetching, and receipt export.
      -

    • ComputeLedger MCP Server

      RudrenduPaul
      A
      license
      A
      quality
      A
      maintenance
      Provides cryptographically signed, tamper-evident compute usage receipts via a Model Context Protocol server, exposing tools to record usage, verify receipts, list the ledger, and verify ledger integrity without requiring any account, API key, or single cloud provider.
      4
      12 npm
      Apache 2.0

    • Singularis

      oov1317
      F
      license
      B
      quality
      A
      maintenance
      Enables agents to run heavy computation—heat-equation solves, matrix exponentials, linear algebra, FFTs, compression, and arbitrary dispatched workloads—on their own machine while routing jobs through an automatic chooser and returning verifiable result digests with CPU-seconds and credit accounting.
      19
      -

    • @sequesign/mcp

      Sequesign
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to create cryptographically verifiable receipts of their delegated work, with capabilities for multi-party approval and offline verification.
      11
      60 npm
      Apache 2.0

    • ThetaCog MCP

      wiber
      A
      license
      B
      quality
      B
      maintenance
      This server enables decidable, hardware-attested semantic verification of AI outputs using on-chip ballistic walks, providing reproducible receipts that can be recomputed byte-for-byte.
      12
      345 npm
      1
      MIT
    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

    A3.6/5.0

    Scored across 6 tools

    Disambiguation3/5

    Most tools are distinct, but inspect and quote both create quote-like objects and both explicitly do not spend, making their boundary fuzzy. Status, download, start, and receipt are clearly separated.

    Naming Consistency3/5

    Names are simple, lowercase, and single-word, but they mix imperative verbs (inspect, start, download) with noun-style actions (status, receipt). There is no consistent verb_noun pattern, though the names remain readable.

    Tool Count5/5

    Six tools is well-scoped for the quote-to-receipt rendering workflow. Each tool represents a meaningful stage in the process without redundant or unnecessary surface area.

    Completeness4/5

    The core lifecycle is covered: inspect, quote, start, status, download, and receipt. Minor gaps exist such as no explicit cancel/refund flow and upload is only referenced via upload_id, but agents can work around these for typical jobs.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources