Skip to main content
Glama
Sign In
Veyline MCP Server

Veyline MCP Server

by Payloadhq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Veyline MCP Server

No user-submitted related servers found.

    Related Servers

    • MandatePay

      muhammadashir0
      A
      license
      A
      quality
      D
      maintenance
      Enables agents to request payment authorization against signed human mandates, enforcing policy-as-code limits and returning a decision (authorize, challenge, or deny) without moving funds.
      1
      1
      Apache 2.0

    • gvnr

      instruxi-io
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables MCP clients to ask permission before an agent acts, returning allow, deny, or ask_human with receipts, and to monitor agent spend, limits, and recent decisions.
      57 npm
      Functional Source , Version 1.1, ALv2 Future

    • Cani

      dmytro-portianka-ddddd
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an MCP client to ask whether a purchase is affordable and receive an auditable, deterministic YES/NO verdict backed by an append-only ledger, and to attempt a real governed checkout that returns a structured decline without creating a PayPal order when the answer is NO. It surfaces committed-payment headroom and essential-lane exceptions so agents can gate spending before money moves.
      6 npm
      MIT

    • haia-trace-mcp

      0x0shephard
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to list and read their own Haia Trace Operation Receipts, explain outcomes, and run an advisory pre-payment check that can allow, block, or route decisions to a human reviewer; agents can then read the review status but cannot approve or reject it themselves.
      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 3 tools

    Disambiguation4/5

    The three tools are mostly distinct: status reads entitlement/tier, usage reads quota consumption, and preflight requests a signed payment authorization. Status vs. usage overlap somewhat (both are read-only org-state reads about the same domain), but the descriptions make the boundary clear enough to select correctly.

    Naming Consistency5/5

    All tools follow the same predictable pattern: a shared veyline_ prefix with a single snake_case scope noun (status, usage, preflight). No mixed conventions or stylistic outliers.

    Tool Count4/5

    Three tools is on the thin side but defensible for a narrow read-only entitlement/usage plus preflight surface. Each tool earns its place with no redundancy.

    Completeness3/5

    The surface covers reads (entitlement, usage) and preflight authorization, but there is no tool to check preflight status, revoke/cancel a preflight, or submit/settle the actual payment path, leaving a lifecycle dead end after preflight. Agents must complete payment execution elsewhere.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources