Pride
Server Details
EBI PRIDE Archive MCP — proteomics (mass-spectrometry) data repository.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-pride
- GitHub Stars
- 0
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.
Tool Definition Quality
Average 4.5/5 across 31 of 32 tools scored. Lowest: 3.8/5.
Most tools have clearly distinct purposes with detailed descriptions. Some overlap exists between ask_pipeworx, ask_pipeworx_grounded, and deep_research, but the descriptions successfully differentiate them. The proteomics tools stand apart from the rest, reducing confusion.
All tool names follow a consistent lowercase_with_underscores pattern with descriptive verbs (ask_pipeworx, compare_entities, resolve_entity). No mixing of conventions or vague names like 'process' or 'help'. The naming is predictable and clear.
32 tools is on the high side, and the server appears to aggregate multiple domains (pipeworx data, Polymarket betting, proteomics, memory). This breadth makes the set feel bloated. A more focused server might have 15-20 tools. However, each tool seems justified within its subdomain.
The data query and betting tools are comprehensive (CRUD for queries, arbitrage detection, monitoring), but the proteomics subset is incomplete (only search and get, no upload/update). The server's broad scope means some areas are covered well while others are shallow.
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.
Discussions
No comments yet. Be the first to start the discussion!