com.codician/growmos
PYPI · GROWMOS · SCANNED SEP 23
Living knowledge graph for your repo: query with citations, remember/link facts, fact-check claims.
Available components
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 setuptools.build_meta 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 & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 36 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 549 tokens (~45/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage68
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 4% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.codician/growmos MCP server?
com.codician/growmos runs locally as a PyPI package, launched with uvx growmos. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · growmos
claude mcp add com-codician-growmos -- uvx growmos
{
"mcpServers": {
"com-codician-growmos": {
"command": "uvx",
"args": [
"growmos"
]
}
}
} {
"servers": {
"com-codician-growmos": {
"command": "uvx",
"args": [
"growmos"
]
}
}
} codex mcp add com-codician-growmos -- uvx growmos
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-codician-growmos": {
"type": "local",
"command": [
"uvx",
"growmos"
],
"enabled": true
}
}
} openclaw mcp add com-codician-growmos --command uvx --arg growmos
mcp_servers:
com-codician-growmos:
command: "uvx"
args: ["growmos"] {
"McpServers": {
"com-codician-growmos": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"growmos"
]
}
}
} assistant mcp add com-codician-growmos -t stdio -c uvx -a growmos
{
"mcpServers": {
"com-codician-growmos": {
"command": "uvx",
"args": [
"growmos"
]
}
}
} 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.
- 23 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 22 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 21 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
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 23 Sept 2026 · Analysed pypi/growmos@0.1.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
growmos_apply ~92
Apply a completed packet. kind = extraction|resolution|profile; payload = the JSON object; plus source/chunk, type, or entity as printed in the packet.
| Name | Type | Req | Description |
|---|---|---|---|
| chunk | integer | – | – |
| entity | string | – | – |
| kind | string | yes | – |
| partial | boolean | – | – |
| payload | object | yes | – |
| source | string | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
growmos_check ~41
Fact-check claims (as 'A --[pred]--> B' lines or free text) against graph edges with provenance.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
growmos_context ~35
Compact brief of the repository knowledge graph: hubs, health, pending work, latest journal. Call at the start of a session.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
growmos_entity ~32
Show one entity: description, profile, edges with provenance, sources, aliases.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
growmos_journal ~37
Append a note to the shared journal (what changed and why).
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
growmos_link ~54
Record a typed relation A --[predicate]--> B (short verb phrase predicates).
| Name | Type | Req | Description |
|---|---|---|---|
| predicate | string | yes | – |
| provenance | string | – | – |
| source | string | yes | – |
| target | string | yes | – |
No output schema declared.
No examples provided.
growmos_next ~58
Get the next task packet (extraction/resolution/profile/gold/review) to grow the graph. Produce the JSON it asks for, then call growmos_apply. force=true ignores the daily extraction cap.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | – |
No output schema declared.
No examples provided.
growmos_query ~64
Ask a multi-hop question; returns the k-hop subgraph (triples with edge ids and provenance) to answer from. Answer only from it and cite edge ids.
| Name | Type | Req | Description |
|---|---|---|---|
| hops | integer | – | – |
| question | string | yes | – |
| seeds | array | – | – |
No output schema declared.
No examples provided.
growmos_remember ~77
Record a durable node (component, decision, concept, person…) with a grounded one-sentence description.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| name | string | yes | – |
| source | string | – | provenance label, e.g. session:2026-08-17 or a file path |
| type | string | yes | – |
No output schema declared.
No examples provided.
growmos_sample ~20
Random node for human review (the daily comprehension check).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
growmos_search ~24
Find entities by name/alias substring.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
growmos_status ~15
Graph statistics and health signals.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the com.codician/growmos MCP server?
com.codician/growmos is an MCP server listed in the public MCP registry as com.codician/growmos. Living knowledge graph for your repo: query with citations, remember/link facts, fact-check claims. This page covers its PyPI package (growmos).
Is the com.codician/growmos MCP server safe to use?
com.codician/growmos scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 September 2026. 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 com.codician/growmos MCP server expose?
com.codician/growmos exposes 12 tools: growmos_context, growmos_query, growmos_entity, growmos_search, growmos_remember, and 7 more. Their descriptions and schemas cost roughly 549 tokens of context every time the server is loaded.
Is the com.codician/growmos MCP server still maintained?
com.codician/growmos is still listed as active in the MCP registry. We last reached this channel on 23 September 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 com.codician/growmos MCP server under?
com.codician/growmos declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.