Skip to main content
Glama
kryp2

peck-mcp

by kryp2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to peck-mcp

No user-submitted related servers found.

    Related Servers

    • AgentWallet MCP Server

      hifriendbot
      A
      license
      A
      quality
      B
      maintenance
      Provides permissionless wallet infrastructure for AI agents to manage wallets, sign transactions, and handle tokens across Solana and all EVM-compatible chains. It includes 29 specialized tools for on-chain operations, featuring built-in security guards and automated x402 payment processing without KYC requirements.
      29
      1,236 npm
      3
      MIT

    • Solana MCP Server

      visioneth
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to read chain data, execute transactions, swap tokens, and manage wallets on Solana through 38 tools across 7 modules. Supports write operations with a private key and includes built-in prompts for common workflows.
      38
      1
      MIT

    • Bitcoin SV MCP Server

      opldotdev
      A
      license
      B
      quality
      C
      maintenance
      A collection of Bitcoin SV tools for the Model Context Protocol that enables AI assistants to interact with the BSV blockchain through wallet operations, ordinals (NFTs), and various blockchain utilities.
      9
      135 npm
      22
      MIT

    • Agentry MCP Server

      cthulhutoo
      A
      license
      Not graded
      quality
      F
      maintenance
      Provides a trust layer for AI agents with identity, reputation, payments, and discovery via 92 API endpoints as MCP tools, leveraging Nostr-native infrastructure.
      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.7/5.0

    Scored across 42 tools

    Disambiguation4/5

    The read/write separation is clear (peck_payments vs peck_payment_tx, peck_messages vs peck_message_tx), and each tool has a distinct documented purpose. Minor confusion is possible between wrapper tools like peck_recent and peck_feed with since, or peck_user_posts and peck_feed with author filter, but the descriptions call these out.

    Naming Consistency4/5

    Consistent peck_ prefix and snake_case throughout, with a mostly predictable pattern: nouns for reads and verb_tx for writes. Deviations exist (peck_function_register, peck_request_payment, peck_fleet_spawn) that break the verb_tx convention, but they are still readable and recognizable.

    Tool Count2/5

    42 tools is well above the 25+ threshold for 'too many', even for a broad social-graph domain. The count creates significant selection overhead, and several tools (peck_recent, peck_user_posts) are convenience wrappers that could be absorbed into parameterized calls without losing functionality.

    Completeness5/5

    The surface is remarkably complete for its domain: full read/write coverage for posts, threads, search, interactions, messages, profiles, follows/friends, payments, functions, identity, and fleet management. The only absent operations (update/delete for posts) are inherently impossible for immutable on-chain data, so no real gaps exist.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources