Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.nickjlamb/opengate-mcp

NPM · @PHARMATOOLS/OPENGATE-MCP · SCANNED AUG 3

Check whether an AI answer is grounded in its context — deterministic, no LLM judge.

+30 this week 75 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to nickjlamb/opengate). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 27 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 232 tokens (~232/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @pharmatools/opengate-mcp

# add to Claude Code
claude mcp add nickjlamb-opengate-mcp -- npx -y @pharmatools/opengate-mcp
# add to Codex CLI
codex mcp add nickjlamb-opengate-mcp -- npx -y @pharmatools/opengate-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nickjlamb-opengate-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pharmatools/opengate-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nickjlamb-opengate-mcp --command npx --arg -y --arg @pharmatools/opengate-mcp
# ~/.hermes/config.yaml
mcp_servers:
  nickjlamb-opengate-mcp:
    command: "npx"
    args: ["-y", "@pharmatools/opengate-mcp"]
// mcp.json
{
  "mcpServers": {
    "nickjlamb-opengate-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pharmatools/opengate-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +70
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Provenance: unverified → pass security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • The attested source repository moved: nickjlamb/opengate security
    • Security disclosure: fail → unverified functional
    • Schema quality: unverified → excellent functional
    • Tool coverage: unverified → 100 functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Licence: MIT functional
  • 1 Aug 26 −15
    • Tool coverage: 100 → unverified functional
  • 31 Jul 26 −4
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 −21
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 45

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@pharmatools/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

Source repo:
nickjlamb/opengate
Certificate issuer:
https://token.actions.githubusercontent.com
Certificate SAN:
https://github.com/nickjlamb/opengate/.github/workflows/mcpb-pack.yaml@refs/tags/opengate-mcp-0.1.4
Rekor log index:
2084694535
Predicate type:
https://slsa.dev/provenance/v1
Subject digest:
sha512:ca5a04e95c7a5ccb6b83b5bfb80fc3d30850cf8560ce6596c7fc4bda70ab331195d6ee9a998b496bf4dbe4adc92d8e189e7ddc2fd7357a16a177271b0
Discovery method:
attestation_endpoint
Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 1 exposed · ~232 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
check_grounding ~232

Check whether an answer is grounded in the provided context. Deterministic (no LLM judge): verifies that required facts appear in the answer, that every number in the answer traces to the context, and — for questions the context cannot answer — that the answer abstains instead of fabricating. Use this to self-check RAG / document-QA / retrieval answers before returning them.

NameTypeReqDescription
allowed_new_numbersarrayNumbers the answer may introduce that are not in the context (e.g. from the question).
answerstringyesThe answer to check.
contextyesThe retrieved context the answer must be grounded in (a string, or an array of passages).
expected_factsarrayFacts a correct answer must contain (e.g. "30 days", "no restocking fee"). Each must appear in the answer.
must_abstainbooleanSet true when the context does NOT contain the answer: the answer must then decline rather than fabricate.
questionstringThe original question (optional; lets numbers from the question count as grounded).

No output schema declared.

No examples provided.