Skip to main content
Glama
greyisworking

Web3 Content MCP Server

by greyisworking
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to Web3 Content MCP Server

No user-submitted related servers found.

    Related Servers

    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

    C2.7/5.0

    Scored across 25 tools

    Disambiguation2/5

    Multiple tools have unclear boundaries: get_article vs article_get, get_articles vs article_list, and search_content vs article_search appear to serve the same purpose. While some tools (token prices, watchlist) are distinct, the overlapping pairs create significant misselection risk.

    Naming Consistency2/5

    Naming is inconsistent, mixing verb-first (get_article) and noun-first (article_create) patterns, along with preposition-based verbs (add_to_watchlist). No uniform convention exists across the set, making it hard to predict tool names.

    Tool Count3/5

    At 25 tools, the count is at the upper end of 'heavy' and many tools duplicate functionality (e.g., get_articles vs article_list). The set could be streamlined to ~15-18 tools without losing capability, making the current count feel slightly inflated.

    Completeness4/5

    The server covers article CRUD reasonably well (article_create/get/list/update/search/export) and includes content storage, RSS management, and token prices. However, there is no update operation for stored content items and no remove_from_watchlist, leaving minor lifecycle gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources