Skip to main content
Glama
GTCC777

PulseNetwork MCP

by GTCC777
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to PulseNetwork MCP

No user-submitted related servers found.

    Related Servers

    • Grey Ridge x402 MCP

      rezearcher
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to access crypto prices, DeFi yields, Polymarket data, Base chain info, and security scans with pay-per-call via USDC on Base mainnet.
      MIT

    • Spraay x402 MCP Server

      plagtech
      A
      license
      B
      quality
      D
      maintenance
      Connects AI agents to the Base network for onchain data, batch USDC payments, and access to over 200 AI models. It utilizes the x402 protocol to enable pay-per-request functionality using USDC without requiring traditional API keys or accounts.
      100
      27 npm
      4
      MIT

    • Genesis402

      FTHTrading
      A
      license
      A
      quality
      A
      maintenance
      Pay-per-call data and tools for AI agents over x402, by UnyKorn. 360 endpoints: DeFi and market data, multi-chain wallet reads, wallet and token risk signals, SEC filings, web and domain intel, and AI text tools. Settled per call in USDC on Base ($0.001-$0.25). No API keys or subscriptions; unpaid calls return the exact quote first.
      2
      14
      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/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: discovering endpoints, executing paid calls, checking wallet balance, viewing spend reports, and inspecting guardrails. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    All tools share the 'pulse_' prefix, creating a recognizable pattern, but the suffixes mix verbs (call, discover) and nouns (report, guardrail, balance). The inconsistency is minor and does not impede comprehension.

    Tool Count5/5

    With 5 tools, the set is well-scoped for its purpose: a paid API gateway needs discovery, execution, balance, reporting, and safety checks. Every tool earns its place.

    Completeness5/5

    The toolset covers the full user workflow: discover an endpoint, check price and balance, call it, monitor spend via report, and verify caps. The deliberate absence of a guardrail-raising tool is a security feature, not a gap.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources