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

Coalent

PYPI · COALENT · SCANNED AUG 5

Fresh, attributed facts from your sources — cached, and invalidated the moment a source changes.

Available components

pypi · coalent 36
36 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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency32
Schema Quality & AI Usability0
  • Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
  • Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
  • Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
  • Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

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.

pypi · coalent

# add to Claude Code
claude mcp add nisarg-pujara-vectorlink-coalent -- uvx coalent
# add to Codex CLI
codex mcp add nisarg-pujara-vectorlink-coalent -- uvx coalent
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nisarg-pujara-vectorlink-coalent": {
      "type": "local",
      "command": [
        "uvx",
        "coalent"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nisarg-pujara-vectorlink-coalent --command uvx --arg coalent
# ~/.hermes/config.yaml
mcp_servers:
  nisarg-pujara-vectorlink-coalent:
    command: "uvx"
    args: ["coalent"]
// mcp.json
{
  "mcpServers": {
    "nisarg-pujara-vectorlink-coalent": {
      "command": "uvx",
      "args": [
        "coalent"
      ]
    }
  }
}
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.

  • 5 Aug 26 36

    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 5 Aug 2026 · Analysed pypi/[email protected]

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build
Dependencies 0 packages
Packages resolved 0
Tree resolution Complete
MCP tools

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.

Tools for package channels are captured by running the package in an isolated sandbox. This package has not been through a sandbox run yet.