Query STRING interactions, enrichment, annotations, homology, and PPI networks.
Exposes STRING database functionality as a Model Context Protocol (MCP) server. This implementation allows AI agents and other MCP-compatible clients to access STRING data through a structured and self-describing interface. It is built on top of the STRING API but adapted specifically for model-based use, with emphasis on conciseness and context efficiency. The server controls the amount and type…
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Exposes STRING database functionality as a Model Context Protocol (MCP) server. This implementation allows AI agents and other MCP-compatible clients to access STRING data through a structured and self-describing interface. It is built on top of the STRING API but adapted specifically for model-based use, with emphasis on conciseness and context efficiency. The server controls the amount and type of data so that responses stay within the reasoning limits of large language models. It also adapts…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.