Proxenio MCP Server
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Proxenio MCP Server Show me my professional matches"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Proxenio MCP Server
MCP (Model Context Protocol) server for the Proxenio verified intent network. Enables AI agents running in Claude Desktop, Cursor, VS Code, and other MCP-compatible clients to discover and interact with Proxenio's professional matching engine.
What It Does
This server gives your AI agent four tools:
Tool | What it does |
| Learn about the platform, trust model, and API — no auth required |
| Configure your Proxenio API key for authentication |
| Read your principal's verified professional matches |
| Accept an introduction request, creating a deal |
Your agent inherits the human principal's trust tier. It sees exactly what the principal sees — same matching engine, same rules, same verification gates. No shortcuts.
Related MCP server: MeetMyAgent MCP
Prerequisites
Node.js 18+
A Proxenio account with a verified email and completed profile
An API key generated at proxenio.ai/agents
Installation
npx @proxenio-tech/mcp-serverUsage with Claude Desktop
Add to your Claude Desktop configuration (claude_desktop_config.json):
{
"mcpServers": {
"proxenio": {
"command": "npx",
"args": ["@proxenio-tech/mcp-server"]
}
}
}Then in Claude Desktop, you can say:
"What is Proxenio?"
→ Claude usesproxenio_discoverautomatically
"Connect to Proxenio with this key: prx_YOUR_KEY_HERE_________________"
→ Claude usesproxenio_set_api_key
"Show me my professional matches"
→ Claude usesproxenio_get_matches
"Accept the introduction from Maria Georgiou"
→ Claude usesproxenio_accept_match
Usage with Cursor
Add to your Cursor MCP settings:
{
"proxenio": {
"command": "npx",
"args": ["@proxenio-tech/mcp-server"]
}
}Remote Deployment (HTTP)
For multi-client or cloud deployment:
TRANSPORT=http PORT=3001 node dist/index.jsThe server exposes:
POST /mcp— MCP protocol endpointGET /health— Health check
Tools Reference
proxenio_discover
No authentication required. Returns platform info, trust model, capabilities, and links.
proxenio_set_api_key
Parameter | Type | Required | Description |
| string | Yes | Full API key (36 chars, starts with |
proxenio_get_matches
Parameter | Type | Default | Description |
|
|
| Filter by match quality |
|
|
| Filter by status |
| number (40-100) |
| Minimum match score |
Returns: Principal info, matches with counterparty profiles, trust tiers, scores, and rate limit status.
proxenio_accept_match
Parameter | Type | Required | Description |
| string (UUID) | Yes | Match ID from |
Returns: Confirmation, counterparty details, new deal ID, rate limit status.
Guard rails: Principal must be the receiving party. Cannot accept own requests. Match must be active with a pending intro.
Trust Model
Agents inherit their human principal's trust tier at request time
Trust tiers: 0 (Unverified) → 1 (Starter) → 2 (Active) → 3 (Trusted) → 4 (Proven)
All engine verification gates apply — agents cannot bypass any
Counterparties see transparency badge:
🤖 AI Agent active on behalf of [Name]Only humans can log outcomes and confirm deals
Rate Limits
60 requests/hour per API key
3 keys maximum per user (= 180 requests/hour total)
Rate limit headers included in all responses
Security
API keys are never logged or stored by the MCP server
Keys are validated on format before use (prefix, length)
All communication uses HTTPS
The MCP server acts as a pass-through — no data is cached
Links
Platform: proxenio.ai
Agent Docs: proxenio.ai/agents/docs
Discovery Manifest: .well-known/proxenio.json
OpenAPI Spec: api/agent/openapi.json
License
MIT — Proxenio Technologies Ltd
Available Tools
4 toolsproxenio_accept_matchAccept Proxenio IntroductionA
Accept an introduction request on behalf of the human principal.
This creates a deal between the principal and the counterparty. The principal must be the receiving party (user_b) — agents cannot accept introductions that the principal initiated.
IMPORTANT: This is an action with real consequences. It connects two professionals and creates a deal container. Only accept matches that align with the principal's stated intent.
Requires: API key must be set via proxenio_set_api_key first.
Args:
match_id (string, UUID): The match ID to accept. Get this from proxenio_get_matches results.
Returns: Confirmation with counterparty details, the new deal ID, and rate limit status.
Guard rails enforced by the API:
Principal must be a participant in the match
Principal must be the receiving party (user_b), not the requester
Match must have an active status
An introduction request must exist and be in pending/awaiting_consent state
Agent cannot accept the principal's own outgoing requests
Examples:
Use when: Principal wants to accept a specific pending introduction
Use when: Agent decides a match aligns with principal's intent and should be accepted
Don't use when: You haven't checked the match details first (use proxenio_get_matches)
Don't use when: The match was initiated by the principal (agent can only accept incoming)
Error Handling:
400: Match not in correct state, no intro request exists
403: Principal is not authorized (e.g., they are the requester, not receiver)
404: Match ID not found
429: Rate limit exceeded
Inputs: match_id (required).
proxenio_discoverDiscover Proxenio PlatformARead-onlyIdempotent
Get information about the Proxenio platform and its agent API.
Proxenio is a verified intent network for professional deal-making. AI agents can access their human principal's matches through API keys with inherited trust tiers.
This tool requires no authentication. Use it to understand the platform before connecting.
Returns: Platform description, trust model, available capabilities, authentication method, and rate limits.
Examples:
Use when: "What is Proxenio?" or "How do I connect to Proxenio?"
Use when: Agent needs to understand what Proxenio offers before authenticating
Don't use when: You already know about Proxenio and just need to read matches
Inputs: no named parameters.
proxenio_get_matchesGet Proxenio MatchesARead-onlyIdempotent
Read the principal's verified professional matches from Proxenio.
Returns matches sorted by match score (descending). Each match includes counterparty profile, trust tier, PRO score, intent, verification status, and confirmed outcome count.
Requires: API key must be set via proxenio_set_api_key first.
The agent sees exactly what the human principal sees — same verification gates, same tier gates, same minimum score (40). Matches below 40 are never returned.
Args:
filter_type ('all' | 'top' | 'high' | 'standard'): Filter by match quality tier (default: 'all')
filter_status ('all' | 'pending' | 'accepted'): Filter by match status (default: 'all')
min_score (number, 40-100): Minimum match score threshold (default: 40)
Returns: Principal info, list of matches with full counterparty profiles, trust signals, and rate limit status.
Examples:
Use when: "Show me my matches" or "What professional connections are available?"
Use when: "Find my best matches" -> use filter_type='top'
Use when: "Which introductions are pending?" -> use filter_status='pending'
Don't use when: API key has not been set yet (use proxenio_set_api_key first)
Error Handling:
Returns auth error if API key is invalid or revoked
Returns rate limit error if 60 requests/hour exceeded
Returns empty list if principal has no matches (profile may be incomplete)
Inputs: min_score, filter_type, filter_status.
proxenio_set_api_keySet Proxenio API KeyAIdempotent
Configure the API key for authenticating with Proxenio's agent API.
This must be called before using proxenio_get_matches or proxenio_accept_match.
The API key is generated by a verified human principal at https://www.proxenio.ai/agents. Keys are 36 characters, start with 'prx_', and inherit the principal's trust tier.
Args:
api_key (string): The full API key starting with 'prx_' (36 characters)
Returns: Confirmation that the key was set, or an error if the format is invalid.
Examples:
Use when: Setting up Proxenio access for the first time
Use when: Switching to a different principal's API key
Don't use when: Key is already configured and working
Inputs: api_key (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
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.
All tools follow a consistent 'proxenio_<verb>_<noun>' naming pattern (e.g., proxenio_get_matches, proxenio_accept_match). The convention is uniform and predictable.
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.
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
Related MCP Connectors
The people network your AI agent joins on your behalf — find, match, and meet anyone.
Connect AI agents to Prosyo to query pipeline metrics, search B2B prospects, and manage multichannel LinkedIn and cold email outreach.
Connect AI agents to discover services and coordinate real-world tasks.
Professional network for AI agents. Discover and connect with professionals.
Related MCP Servers
- AlicenseAqualityBmaintenanceYour 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.7146 npm7Apache 2.0
- AlicenseAqualityBmaintenanceHosted 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.1040 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to vet a developer's shipped products, check fixed pricing and availability, and submit project briefs on behalf of users.1MIT
- AlicenseAqualityBmaintenanceEnables 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.21Apache 2.0