UniProt MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is UniProt MCP Server?

The UniProt MCP Server is a Model Context Protocol (MCP) server that provides access to UniProt protein information, allowing AI assistants to fetch protein function and sequence information directly from UniProt.

how to use UniProt MCP Server?

To use the UniProt MCP Server, clone the repository, install the required dependencies, and configure it in your Claude Desktop application. You can then query protein information using UniProt accession numbers.

key features of UniProt MCP Server?

  • Retrieve protein information by UniProt accession number
  • Batch retrieval of multiple proteins
  • Caching for improved performance (24-hour TTL)
  • Detailed error handling and logging
  • Information provided includes protein name, function description, full sequence, sequence length, and organism.

use cases of UniProt MCP Server?

  1. Fetching detailed information about specific proteins for research purposes.
  2. Comparing multiple proteins' information for analysis.
  3. Integrating protein data into AI applications for enhanced functionality.

FAQ from UniProt MCP Server?

  • Can I retrieve information for multiple proteins at once?

Yes! The server supports batch retrieval of protein information.

  • What programming language is required to run the server?

You need Python 3.10 or higher to run the UniProt MCP Server.

  • Is there any caching mechanism in place?

Yes, the server implements caching with a 24-hour time-to-live (TTL) for improved performance.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago