Skip to main content
Glama
zhurong2020

pyobfus-mcp

by zhurong2020
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to pyobfus-mcp

No user-submitted related servers found.

    Related Servers

    • MCP Python Toolbox

      gianlucamazza
      A
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol server that enables AI assistants like Claude to perform Python development tasks through file operations, code analysis, project management, and safe code execution.
      9
      MIT

    • MCP Tools

      ZbigniewTomanek
      A
      license
      Not graded
      quality
      D
      maintenance
      A custom Model Context Protocol server that gives Claude Desktop and other LLMs access to file system operations and command execution capabilities through standardized tool interfaces.
      23
      Apache 2.0

    • OpenAI Agents MCP Server

      lroolle
      F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables Claude users to access specialized OpenAI agents (web search, file search, computer actions) and a multi-agent orchestrator through the MCP protocol.
      4
      10
      -

    • @kazuph/mcp-fetch

      kazuph
      A
      license
      A
      quality
      C
      maintenance
      Model Context Protocol server for fetching web content and processing images. This allows Claude Desktop (or any MCP client) to fetch web content and handle images appropriately.
      1
      445 npm
      41
      MIT

    • @pawells/mcp-memory

      PhillipAWells
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Model Context Protocol server for semantic memory and knowledge management with Claude Code.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target distinct stages of the obfuscation lifecycle (scan, config, protect, ship, debug), but three tools — check_obfuscation_risks, recommend_tier, and protect_project — all perform project scans, and list_presets vs explain_preset sit close together, creating mild boundary ambiguity.

    Naming Consistency5/5

    Every tool follows a clean verb_noun snake_case pattern (start_pro_trial, list_presets, protect_project, check_delivery, unmap_stack_trace), with no mixed conventions or vague verbs.

    Tool Count5/5

    Nine tools is well-scoped for a Python obfuscation server, with each tool earning its place across the protect-scan-config-verify-ship-debug workflow without redundancy.

    Completeness4/5

    The lifecycle is well covered end-to-end: risk scanning, config generation, protection, delivery checks, stack-trace unmapping, and tier recommendation. Minor gaps exist around Pro license activation (only trial-start guidance) and a standalone obfuscate-without-verify path.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources