Skip to main content
Glama
Abacore-net

acn-preflight-mcp

by Abacore-net
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to acn-preflight-mcp

No user-submitted related servers found.

    Related Servers

    • verdix by verdixapi

      verdixofficial

      verdixapi
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to check an EVM address on Base for risk (safe, caution, danger) before sending funds, with reasons, paid per call via x402 from the user's own wallet.
      6
      265 npm
      MIT

    • x402-tools

      vera-agent-dev
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to pay per call for live package-safety and GitHub merge-readiness trust signals via the x402 protocol.
      3
      MIT

    • OceanAlt AML

      OceanAlt
      A
      license
      Not graded
      quality
      F
      maintenance
      Crypto compliance tools for AI-agent payments: screen any address for sanctions, frozen-stablecoin and hacker/mixer exposure across 8+ chains, trace fund taint, and get an allow/review/decline decision before settlement. Free keyless address checks; deeper endpoints are x402-payable.
      297 npm
      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

    B3.4/5.0

    Scored across 3 tools

    Disambiguation3/5

    payment_preflight is clearly distinct, but repo_contribution_readiness and bounty_reality_check both target pre-contribution GitHub checks and could be confused. The descriptions clarify that one is about repository health and the other about bounty/issue evidence, but the boundary is somewhat subtle.

    Naming Consistency4/5

    All names use lowercase snake_case noun phrases that lead with the domain (repo, payment, bounty). They are readable and consistent in style, though they mix suffixes like _readiness, _preflight, and _reality_check rather than following a single verb_noun pattern.

    Tool Count4/5

    Three tools is minimal but reasonable for a focused preflight server. Each tool covers a distinct preflight scenario and none feels redundant, though the surface is on the small side.

    Completeness4/5

    For a preflight-focused server, the three core scenarios (repository, payment, bounty/issue) are covered and give an agent the checks needed before acting. There are minor gaps, such as no generic environment or dependency preflight, but they do not create dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources