Is the Nhoverte Biocosm MCP server down?

mcp-registry/io.github.nhoverte/biocosm · v3.4.4

As of 2026-10-22 01:53 UTC, the Nhoverte Biocosm MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 13 outages in 90 days, with a median recovery of 8 minutes.

Biotech intelligence for AI agents: drugs, targets, diagnostics, PoS estimates, and writeups.

claude mcp add --transport http nhoverte-biocosm-mcp-server https://biocosm-mcp.fly.dev/mcp

{
  "mcpServers": {
    "nhoverte-biocosm-mcp-server": {
      "type": "http",
      "url": "https://biocosm-mcp.fly.dev/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (88/100)

What to fix (2)

Auto-fix: 13 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.nhoverte%2Fbiocosm/fixes

{
  "name": "find_by_phase",
  "description": "List drugs/diagnostics at a specific clinical phase.",
  "inputSchema": {
    "type": "object",
    "required": [
      "phase"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "default": 100,
        "description": "Maximum results (default 100, max 500)"
      },
      "phase": {
        "type": "string",
        "description": "One of \"approved\", \"on_market\", \"phase3\", \"phase2\", \"phase1\",\n   \"in_development\", \"cleared\", \"ldt\", \"ruo\""
      },
      "node_type": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null,
        "description": "Optional filter — \"drug\", \"pipeline\", \"diagnostic\", \"target\""
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "find_by_target",
  "description": "Find all drugs that target a specific gene/protein.",
  "inputSchema": {
    "type": "object",
    "required": [
      "target_gene"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "default": 50,
        "description": "Maximum results (default 50, max 200)"
      },
      "target_gene": {
        "type": "string",
        "description": "Gene symbol or target name (e.g. \"EGFR\", \"KRAS\", \"PD-1\")"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "find_related",
  "description": "Find nodes connected to a given node. Three relationship types are\nderived on-the-fly:\n  - \"drug_target\": for a drug, the targets it hits (and vice versa for a\n                   target node, the drugs that hit it)\n  - \"same_company\": drugs sharing a company with this node\n  - \"same_target_class\": drugs with the same mechanism_class",
  "inputSchema": {
    "type": "object",
    "required": [
      "node_id"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "default": 30,
        "description": "Maximum results per link type (default 30)"
      },
      "node_id": {
        "type": "string",
        "description": "Source node identifier"
      },
      "link_type": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null,
        "description": "Optional filter — one of \"drug_target\", \"same_target_class\",\n       \"same_company\". If None, returns all three groups."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.nhoverte/biocosm"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.nhoverte/biocosm"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~1,726 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.78% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• find_related ~241 tokens
• search_nodes ~213 tokens
• get_node ~208 tokens
• find_by_phase ~170 tokens
• get_pos_score ~127 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.nhoverte%2Fbiocosm.svg)](https://glimind.com/server/mcp-registry%2Fio.github.nhoverte%2Fbiocosm?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.nhoverte%2Fbiocosm?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.nhoverte%2Fbiocosm.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.nhoverte%2Fbiocosm.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.nhoverte%2Fbiocosm?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:43ec78b58e1b0deb…, first seen 2026-10-17, included at leaf 12116 of 42,790. Version history · verify what your client received.

Tools (13)

• find_by_phase
• find_by_target
• find_related
• get_company_portfolio
• get_coverage
• get_node
• get_node_freshness
• get_pos_score
• get_staleness_report
• get_stats
• get_writeup
• list_by_therapeutic_area
• search_nodes

Compare: most reliable knowledge servers · most reliable data servers · most reliable ml servers · most reliable search servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Nhoverte Biocosm MCP server down right now?

As of 2026-10-22 01:53 UTC, the Nhoverte Biocosm MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 13 outages in 90 days, with a median recovery of 8 minutes.

How many tools does Nhoverte Biocosm MCP server provide?

Nhoverte Biocosm MCP server advertises 13 tools, including find_by_phase, find_by_target, find_related, get_company_portfolio, get_coverage.

How do I install Nhoverte Biocosm MCP server?

Point your MCP client at this streamable-http endpoint: https://biocosm-mcp.fly.dev/mcp

Is the Nhoverte Biocosm MCP server safe to connect to an AI agent?

Glimind scanned all 13 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Nhoverte Biocosm MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.