Is the Supp Suppscience MCP server down?

mcp-registry/science.supp/suppscience · v1.2.0

As of 2026-10-24 21:37 UTC, the Supp Suppscience MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

Evidence-graded analyses of 511 supplements: claims, doses, safety, PubMed references (en/pt-BR)

claude mcp add --transport http supp-suppscience-mcp-server https://supp.science/mcp

{
  "mcpServers": {
    "supp-suppscience-mcp-server": {
      "type": "http",
      "url": "https://supp.science/mcp"
    }
  }
}

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

Agent-readiness: B (85/100)

What to fix (2)

Auto-fix: 6 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%2Fscience.supp%2Fsuppscience/fixes

{
  "name": "get_guide",
  "description": "Get one comparison guide by slug, with the compared options, per-option verdicts, and purchase links.",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "Guide slug, e.g. \"magnesium-forms\" (find it via list_guides)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_supplement",
  "description": "Get the full evidence analysis for one supplement by slug: per-claim evidence grades, studied dose, safety, interactions, FAQ, PubMed references, purchase link (buyUrl), and the citable pageUrl (translated fields under \"pt\", \"es\", \"de\", \"fr\").",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "Supplement slug, e.g. \"creatine\" (find it via search_supplements)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_training",
  "description": "Get one training topic by slug: overall and per-claim grades, how to apply it (sets, reps, rest), technique for exercises, who should be careful, FAQ, PubMed references, the supplements from this catalog that help with its goals, and the citable pageUrl (translations under \"pt\", \"es\", \"de\", \"fr\").",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "Training slug, e.g. \"training-volume\" (find it via search_training)"
      }
    }
  },
  "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/science.supp/suppscience"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/science.supp/suppscience"}) 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 (~775 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• search_training ~199 tokens
• get_training ~146 tokens
• search_supplements ~132 tokens
• get_supplement ~131 tokens
• get_guide ~86 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%2Fscience.supp%2Fsuppscience.svg)](https://glimind.com/server/mcp-registry%2Fscience.supp%2Fsuppscience?ref=badge)

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

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fscience.supp%2Fsuppscience.svg
   :target: https://glimind.com/server/mcp-registry%2Fscience.supp%2Fsuppscience?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:c50bdcd282e4d02f…, first seen 2026-10-17, included at leaf 86 of 61,561. Version history · verify what your client received.

Tools (6)

• get_guide
• get_supplement
• get_training
• list_guides
• search_supplements
• search_training

Compare: most reliable knowledge servers · most reliable retrieval 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 Supp Suppscience MCP server down right now?

As of 2026-10-24 21:37 UTC, the Supp Suppscience MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Supp Suppscience MCP server provide?

Supp Suppscience MCP server advertises 6 tools, including get_guide, get_supplement, get_training, list_guides, search_supplements.

How do I install Supp Suppscience MCP server?

Point your MCP client at this streamable-http endpoint: https://supp.science/mcp

Is the Supp Suppscience MCP server safe to connect to an AI agent?

Glimind scanned all 6 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 Supp Suppscience 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.