Skip to main content
Glama
Sign In
M5Devs

legacy-mcps

by M5Devs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to legacy-mcps

No user-submitted related servers found.

    Related Servers

    • SourceForge MCP Server

      Fixitdaz
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to manage SourceForge projects, browse and upload release artifacts via SFTP/FRS, and fetch download statistics and project metadata.
      MIT

    • tralha

      Lusqinha
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to manage buckets and files, upload binaries through single-use URLs, create and revoke public links, preview images, and search indexed markdown notes.
      AGPL 3.0

    • sftp-mcp

      cordfuse
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides a browsable, mutable SFTP filesystem for AI agents, supporting file operations like listing, uploading, downloading, moving, and deleting.
      MIT

    • ftp-mcp

      kemalabuteliyte
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to perform FTP/FTPS/SFTP file operations including upload, download, sync, and directory management with multi-server support.
      36
      35 npm
      7
      MIT

    • VPS MCP Server

      HarjjotSinghh
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to connect to and control a Virtual Private Server via SSH. It provides a comprehensive suite of tools for remote file system operations, session management, and shell command execution.
      10
      5 npm
      2
      ISC
    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

    B3.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: one performs discovery queries, the other retrieves metadata for a known identifier. There is no overlap in purpose or expected arguments.

    Naming Consistency4/5

    Both names use the ia_ prefix and snake_case verb_noun structure (search_items, get_item_metadata), which is predictable. Minor inconsistency in noun phrasing (plural 'items' vs. singular 'item_metadata') keeps it from perfect.

    Tool Count3/5

    Two tools is thin even for a focused read-only archive.org integration; the natural next steps (download/fetch content, browse collections) are absent. Each tool does earn its place, but the surface feels minimal.

    Completeness3/5

    Search plus metadata retrieval covers the basic discovery flow, but there is no way to fetch item content/files, list collections, or paginate/refine results beyond the raw query. Agents needing actual archive content hit a dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources