Ncbi Eutils
Server Details
NCBI E-utilities — federated Entrez search/fetch (PubMed/Gene/Nucleotide/…)
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-ncbi-eutils
- 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 across 20 of 20 tools scored. Lowest: 2.1/5.
The tool set mixes NCBI Entrez utilities with a large suite of Pipeworx data tools, Polymarket betting tools, and memory management tools. Many tools have overlapping purposes (e.g., 'ask_pipeworx', 'entity_profile', 'compare_entities', and 'validate_claim' all handle company data), making it difficult for an agent to select the correct tool. The presence of 'discover_tools' indicates the server itself acknowledges the confusion.
Tool names follow no consistent pattern. NCBI tools retain their original names ('esearch', 'efetch'), while others mix styles: verb_noun ('discover_tools', 'resolve_entity'), noun phrases ('entity_profile', 'recent_changes'), and single verbs ('forget', 'recall', 'remember'). The naming conventions are chaotic and unpredictable.
At 20 tools, the count is within a reasonable range but feels excessive given the server's lack of focus. It combines tools from at least three distinct domains (NCBI biology, Pipeworx data analytics, Polymarket betting) plus memory management, which strains coherence. A more focused server with 5-10 tools per domain would be more appropriate.
For a server purportedly about NCBI Eutils, it oddly includes many Pipeworx and Polymarket tools while omitting fundamental NCBI operations like database-specific searches or retrieval of full records with standard formats. The Pipeworx tools cover financial and company data well but lack coverage for other domains mentioned in 'ask_pipeworx' (e.g., weather, sports). The overall surface is unbalanced and incomplete relative to any single stated purpose.
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!