Skip to main content
Glama
Sign In
NinFenz Content Gate

NinFenz Content Gate

by Monyeah777
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to NinFenz Content Gate

No user-submitted related servers found.

    Related Servers

    • Agent中国通

      FRANhss
      A
      license
      A
      quality
      D
      maintenance
      这是一个面向中文圈的MCP服务器，将中国互联网常用能力（如地图、快递、RSS、B站等）封装为标准MCP工具，方便AI Agent安全调用。
      13
      2
      MIT

    • content-contracts-mcp-server

      MauricioPerera
      A
      license
      A
      quality
      D
      maintenance
      MCP server exposing content contract validators (SEO.md, PRODUCTHUNT.md, LINKEDIN.md) as tools so AI agents can verify generated content against concrete rules without maintaining linters. It provides linting and JSON-LD export tools with config and content passed as parameters, not file paths.
      4
      MIT

    • Havens Commons Connector

      travishavens
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that enables AI apps to list, search, and read a set of publicly published guides hosted as Google Docs, without authentication. It exposes list_guides, search_guides, and get_guide tools from a Cloudflare Worker endpoint, caching guide text for about an hour.
      MIT

    • Sumi Docs MCP

      starSumi
      A
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server that exposes the curated Sumi Docs corpus through four tools, enabling agents to query documentation content programmatically.
      1
      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.9/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct resource type and action (list/read/search), and descriptions explicitly state what each tool should not be used for, preventing misselection. The only minor overlap is between registry_search and spec_list for protocols, but the descriptions clearly delineate authoritative catalog vs search.

    Naming Consistency5/5

    All 12 tools follow a consistent snake_case noun_verb pattern (e.g., pattern_read, pipeline_list, asset_read), with no mixing of conventions. The outlier knowledge_order_read still follows the same pattern.

    Tool Count5/5

    12 tools is well-scoped for a content access server covering multiple resource types (patterns, pipelines, assets, modules, library, registry, specs). Each tool earns its place as a list/read/search operation for a distinct resource.

    Completeness4/5

    The read-only surface covers list/read for patterns, pipelines, assets, modules (via registry_search empty query), library entries, and knowledge order. Minor gaps exist: no spec_read for protocol package bodies, and library_search can surface document titles without a corresponding generic document read tool.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources