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.

KG-SSOT

PYPI · KG-SSOT · 2 COMPONENTS

Company-brain knowledge graphs: confirmed claims cite sources, and decisions get revisited

Available components

mcpb · kg-ssot-4.43.0.mcpb 58 pypi · kg-ssot 87
+18 this week 87 Trust /100

Last scanned (6 hours ago)

Scores higher than 89% of PyPI servers

Category Memory and Knowledge

Trust breakdown (7 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 → Why this is hard to 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 build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 7 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to marciocar/kg-ssot). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 259 tokens (~129/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 4 Nov 26 +15
    • Stability: 0.53 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 4.40.2 → 4.43.0 functional
    • Package version: 4.40.2 → 4.42.0 functional
    • Package version: 4.40.2 → 4.41.0 functional
  • 3 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 4.40.1 → 4.40.2 functional
  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 0
    • Package version: 4.39.1 → 4.40.1 functional
    • Package version: 4.39.1 → 4.40.0 functional
  • 29 Oct 26 +1
    • Malware scan: unverified → pass ▲ security
    • Package version: 4.38.0 → 4.39.1 functional
    • Package version: 4.38.0 → 4.39.0 functional
  • 28 Oct 26 0
    • Package version: 4.35.0 → 4.38.0 functional
    • Package version: 4.35.0 → 4.37.0 functional
    • Package version: 4.35.0 → 4.36.0 functional
  • 27 Oct 26 +1
    • Package version: 4.30.0 → 4.35.0 functional
    • Package version: 4.30.0 → 4.34.0 functional
    • Package version: 4.30.0 → 4.33.0 functional
    • Package version: 4.30.0 → 4.32.0 functional
    • Package version: 4.30.0 → 4.31.1 functional
    • Package version: 4.30.0 → 4.31.0 functional
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 4 Nov 2026 · Analysed pypi/kg-ssot@4.43.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo marciocar/kg-ssot
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/marciocar/kg-ssot/.github/workflows/release.yml@refs/tags/kg-ssot-v4.43.0
Rekor log index 3691908261
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:36b135dc7003e5b5e0c7b019c0b542b27be1f3a218ce2393e86124faeeb01a8b

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 7 packages
Packages resolved 7
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~227 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
kg_schema_help ~52

The current contract for writing a graph that passes: the full MUST and SHOULD schemas, a minimal example that passes, the integrity rules and the fix for the most common codes. Call it before writing the first graph.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

kg_validate ~175

Judges a .kg.yaml graph (or .kg.json, with format json) against the current KG-SSOT contract without writing. Returns verdict PASS or FAIL and, per occurrence, code (stable), place, path, line, message and hint (the fix). Fix by the hints and judge again before writing.

NameTypeReqDescription
format––the text format: yaml (.kg.yaml, the default) or json (.kg.json, in the contract's JSON profile); with name, the default comes from the extension
limitinteger–occurrences returned (default 50)
namestring–the name the graph would have in the store (verifies the external end as if it were there)
textstringyesthe whole document: YAML in a .kg.yaml, JSON in a .kg.json

No output schema declared.

No examples provided.

Install

How do I install the KG-SSOT MCP server?

KG-SSOT runs locally as a PyPI package, launched with uvx kg-ssot. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · kg-ssot

# add to Claude Code
claude mcp add marciocar-kg-ssot -- uvx kg-ssot
Common questions

What is the KG-SSOT MCP server?

KG-SSOT is an MCP server listed in the public MCP registry as io.github.marciocar/kg-ssot. Company-brain knowledge graphs: confirmed claims cite sources, and decisions get revisited. This page covers its PyPI package (kg-ssot).

Is the KG-SSOT MCP server safe to use?

KG-SSOT scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the KG-SSOT MCP server expose?

KG-SSOT exposes 2 tools: kg_validate, kg_schema_help. Their descriptions and schemas cost roughly 227 tokens of context every time the server is loaded.

Is the KG-SSOT MCP server still maintained?

KG-SSOT is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the KG-SSOT MCP server under?

KG-SSOT declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.