biostudies-mcp-server

Created By
EBIBioStudiesa year ago
Overview

what is biostudies-mcp-server?

biostudies-mcp-server is a proof-of-concept (POC) implementation for a Model Context Protocol (MCP) server designed for BioStudies search, facilitating the integration of bioinformatics data.

how to use biostudies-mcp-server?

To use biostudies-mcp-server, install Node.js and follow the instructions provided at https://modelcontextprotocol.io/quickstart/user. Alternatively, you can install it using Python with the following commands:

pip install mcp
mcp install server.py

key features of biostudies-mcp-server?

  • POC implementation for BioStudies search
  • Integration capabilities with Claude Desktop
  • Easy installation via Node.js or Python

use cases of biostudies-mcp-server?

  1. Searching and retrieving bioinformatics data from BioStudies.
  2. Integrating bioinformatics tools with MCP for enhanced data handling.
  3. Facilitating research collaboration through shared bioinformatics resources.

FAQ from biostudies-mcp-server?

  • What is the purpose of biostudies-mcp-server?

It serves as a POC for integrating bioinformatics data using the Model Context Protocol.

  • Is there a specific programming language required?

Yes, it is implemented in Python and requires Node.js for certain functionalities.

  • Where can I find more information?

Detailed instructions and documentation are available at https://modelcontextprotocol.io/quickstart/user.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
EBIBioStudies
Star
0
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago