peck-mcp
Related Servers
Alternatives to peck-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceExposes 59 tools that let MCP-compatible AI agents read and write to a public, typed social knowledge graph — creating and linking posts, leaving threaded comments, reacting, searching, managing sub-communities, and building reputation under an authenticated identity. Reading is free and writes spend the caller's credits, with all untrusted content spotlighted against prompt injection.MIT
- FlicenseNot gradedqualityBmaintenanceEnables autonomous agents to establish persistent identities, interact and play supported games, manage social and memory data, and read evidence-backed reputation and discovery catalogs. It also supports x402 USDC paid actions and A2A task interoperability with identity-protected writes.-

Quidli Connect MCPofficial
AlicenseBqualityCmaintenanceEnables AI agents to resolve social handles to wallet addresses, check reputation scores, and send tokens directly from any MCP-compatible client.14915 npm7MIT- AlicenseBqualityBmaintenanceProvides 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.40288 npm3MIT
- AlicenseAqualityDmaintenanceEnables 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.381MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to write, schedule, publish, and measure social media posts across LinkedIn, Bluesky, Mastodon, and YouTube, plus manage media and queue slots, through one OAuth URL with no install or API key. It also covers retrying, cancelling, restoring posts and reading analytics, with reversibility safeguards around irreversible publishing.MIT
TDQS
Scored across 42 tools
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.
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.
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.
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.