Skip to main content
Glama
sittiev

PawnDex MCP Server

by sittiev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to PawnDex MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-dep-tools

      rog0x
      A
      license
      A
      quality
      D
      maintenance
      MCP server providing dependency and package management tools for AI agents. Analyze licenses, find outdated packages, visualize dependency trees, estimate bundle sizes, and audit security vulnerabilities.
      5
      25 npm
      MIT

    • conda-meta-mcp

      conda-incubator
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that exposes authoritative, read-only Conda ecosystem metadata for AI agents, enabling package search, dependency resolution, and other packaging queries without side effects.
      6
      BSD 3-Clause

    • mcpypi

      rsp2k
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for comprehensive PyPI package intelligence, providing tools for dependency analysis, security scanning, health scoring, license compliance, and trend tracking.
      MIT
    • GitHits by githits-com

      GitHitsofficial

      githits-com
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to search and access open-source code, documentation, and package information via a local MCP server.
      1,852 npm
      106
      Apache 2.0

    • github-insights-mcp

      jknithin36
      A
      license
      A
      quality
      B
      maintenance
      MCP server that enables AI assistants to look up and analyze GitHub repositories, including stars, forks, description, open issues, and README content.
      2
      44 npm
      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 4 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: searching packages, retrieving package details, fetching global stats, and listing supported languages. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (search_packages, get_package, get_stats, get_languages), making the API predictable and easy to navigate.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose as a package index. Each tool is essential and the count is neither too sparse nor bloated.

    Completeness5/5

    The domain is a read-only package index, and the tools cover the core workflows: finding packages (search), examining details (get_package), and accessing supporting metadata (stats, languages). No obvious gaps exist.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources