Skip to main content
Glama
Proxenio MCP Server

Proxenio MCP Server

Official
by proxenio

Related Servers

Alternatives to Proxenio MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      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
      468 npm
      7
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Hosted MCP for MeetMyAgent: set up and manage a business AI agent that answers customer questions on your website and dedicated page. Connect at https://meetmyagent.io/mcp with OAuth. The old npm client is retired.
      10
      35 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to use an existing browser session to read profiles and companies, search jobs and people, and manage messages and connection requests on LinkedIn.
      21
      Apache 2.0
    • 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to work a self-hosted X (Twitter) networking pipeline over streamable HTTP, including searching and inspecting people, listing follow/unfollow events, moving contacts between pipeline stages, tagging, adding notes, fetching tweets, running LLM analyses, and triggering or polling sync jobs. Long-running paid operations return a job handle that can be polled for results.
      MIT

    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

    ActivityNo data
    ResponsivenessOutdated data