Skip to main content
Glama
proxenio

Proxenio MCP Server

Official
by proxenio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Proxenio MCP Server

No user-submitted related servers found.

    Related Servers

    • mingle-mcp

      aeoess
      A
      license
      A
      quality
      A
      maintenance
      Your AI finds the right people for you. Agent-to-agent networking via MCP. Publish what you need, match against other agents, both humans approve before connecting. Ed25519 signed, hosted API.
      7
      77 npm
      7
      Apache 2.0

    • LinkedIn MCP Server

      VasquezRivero92
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to manage LinkedIn profiles, posts, connections, skills, education, certifications, and other professional data through the LinkedIn API.
      19
      MIT

    • m3x-mcp-server

      Brano80
      A
      license
      Not graded
      quality
      D
      maintenance
      Connect any AI agent to M3X — the private pool matching protocol for agent-to-agent deal flow. Agents post structured intents, M3X semantically matches them, and identity is only revealed after both sides accept the handshake.
      MIT

    • Workix MCP

      facetoplace
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to search a shared catalog of projects, roles, orders, participants, and mentors, create and update listings or profiles, draft proposals, and search and apply across external freelance and job platforms while keeping platform credentials local.
      13
      -
    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.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct, non-overlapping role: discover platform info, set authentication, retrieve matches, and accept a match. The separation is clear and descriptions reinforce the intended use.

    Naming Consistency5/5

    All tools follow a consistent 'proxenio_<verb>_<noun>' naming pattern (e.g., proxenio_get_matches, proxenio_accept_match). The convention is uniform and predictable.

    Tool Count5/5

    With only 4 tools, the server is tightly scoped and each tool earns its place. This is ideal for the platform's narrow purpose of discovering, authenticating, and processing matches.

    Completeness4/5

    The core lifecycle is covered: discover, authenticate, list matches, and accept. A 'reject' or 'decline' action is absent, but the primary use case of accepting appropriate introductions is fully supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources