io.github.yourtechtribe-labs/koncept-mcp-server

MCPcommunity
v0.2.0-alpha.3io.github.yourtechtribe-labsUnknownUpdated 1mo agonpmGitHub

Query a curated YAML semantic concept graph for codebase invariants and cross-cutting facts.

Semantic concept graph MCP server for codebases — what your code means, not just what it does. Code graphs (Aider repomap, GitNexus, Sourcegraph) capture structural relations: who imports who, who calls who. They miss semantic invariants — the cross-cutting concepts that live in code not related by imports: "Fix B" lives in 7 files but isn't a function or a class "All UI counting workload must…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorio.github.yourtechtribe-labs
LicenseUnknown
Version0.2.0-alpha.3
Sourcemcp-registry
npm@yourtechtribe-labs/koncept-mcp-server
GitHubyourtechtribe-labs/koncept-mcp
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface4 tools · none privileged
Security scan✓ Cleanv0.1.0-alpha.1 · 20d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Semantic concept graph MCP server for codebases — what your code means, not just what it does. Code graphs (Aider repomap, GitNexus, Sourcegraph) capture structural relations: who imports who, who calls who. They miss semantic invariants — the cross-cutting concepts that live in code not related by imports: "Fix B" lives in 7 files but isn't a function or a class "All UI counting workload must exclude manual-override participants" "Sector value strings must match keys exactly" is the curated…

Keywords
mcp