Skip to main content
Glama
gatefareio

gatefareio/mcp-server

Official
by gatefareio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to gatefareio/mcp-server

No user-submitted related servers found.

    Related Servers

    • oom-x402-mcp by OrdersOfMagnitudeLLC

      oom-x402-mcpofficial

      OrdersOfMagnitudeLLC
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server exposing 1,000+ pay-per-call API endpoints across agent infrastructure (memory, coordination, secrets, verification), data, compute, finance, weather, geography, and reference categories — payments via x402 protocol in USDC on Base.
      -
    • halowerk-mcp by halowerk

      halowerk-mcpofficial

      halowerk
      A
      license
      A
      quality
      C
      maintenance
      Provides access to 70 paid APIs as MCP tools with per-call and session budgets, paying via x402/USDC on Base without requiring an account or login. Includes a built-in allowlist of hosts and safe defaults to prevent unintended payments.
      14
      43 npm
      MIT

    • x402-api

      fernsugi
      A
      license
      A
      quality
      C
      maintenance
      Eight crypto and DeFi data tools for AI agents: prices, gas, one ParaSwap route quote, GoPlus token security and top-holder samples, DefiLlama yields, Hyperliquid/dYdX funding, and observed wallet balances. Inspect prices free; pay 0.001–0.008 USDC per call on Base through x402. No API key or subscription.
      8
      214 npm
      MIT

    • webbersites-x402-mcp

      webberdesign
      A
      license
      Not graded
      quality
      F
      maintenance
      Pay-per-call MCP server for WebberSites x402 Data API, offering 45 tools for AI agents: web scraping, document extraction, SEO audits, linting, crypto data, and more, with payment via USDC on Base.
      41 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

    A4.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: search, details, categories, suggestions, reporting, reputation, and sample responses. Even get_api and sample_response are well-separated by their descriptions.

    Naming Consistency4/5

    Most tools follow the verb_noun pattern (search_apis, get_api, list_categories, report_abuse), but suggest and publisher_reputation deviate (bare verb, noun_noun). Overall snake_case and gatefare prefix maintain readability.

    Tool Count5/5

    Seven tools is ideal for this domain, covering discovery, inspection, reputation, and feedback without bloat or redundancy.

    Completeness5/5

    The surface fully covers the API catalog workflow: search, suggest, categories, detailed lookups, publisher trust evaluation, sample response verification, and abuse reporting—no obvious dead ends or missing critical operations.

    Maintenance

    ActivityInactive
    ResponsivenessSlow

    Resources