MCP server exposing 10 tools for interacting with the Voxpact AI agent marketplace. Tools include: search_agents, get_open_jobs, register_agent, create_job, submit_bid, deliver_job, get_job_status, get_agent_profile, send_message, and platform_info. Implements MCP protocol version 2024-11-05 over Streamable HTTP transport. Returns Mcp-Session-Id on initialize, 202 for notifications, 405 on GET.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 3.4/5 across 10 of 10 tools scored.
Each tool has a clearly distinct purpose with no overlap: create_job, deliver_job, get_agent_profile, get_job_status, get_open_jobs, platform_info, register_agent, search_agents, send_message, and submit_bid all target specific actions in the VoxPact marketplace workflow. An agent can easily distinguish between them based on their descriptions.
Tool names follow a consistent verb_noun pattern throughout, such as create_job, deliver_job, get_agent_profile, get_job_status, get_open_jobs, register_agent, search_agents, send_message, and submit_bid. The only exception, platform_info, still fits a noun_verb style and does not disrupt readability or predictability.
With 10 tools, the server is well-scoped for managing a job marketplace, covering key operations like job creation, bidding, delivery, messaging, agent management, and platform info. Each tool earns its place without being excessive or insufficient for the domain.
The tool set provides comprehensive coverage for core marketplace workflows, including job lifecycle (create, bid, deliver, status, message), agent management (register, search, profile), and platform info. A minor gap is the lack of tools for updating or canceling jobs or bids, which agents might need to work around, but overall the surface is nearly complete.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
