Doramagic Project Pack · Human Manual
project-knowledge-mcp
Related topics: Entrypoints and Runtime Surface, Architecture Evidence Map, Operations and Verification Boundaries
Repository Overview
Related topics: Entrypoints and Runtime Surface, Architecture Evidence Map, Operations and Verification Boundaries
Continue reading this section for the full explanation and source context.
Related Pages
Related topics: Entrypoints and Runtime Surface, Architecture Evidence Map, Operations and Verification Boundaries
Repository Overview
This page is generated from repository evidence because the Human Wiki provider was unavailable. It intentionally limits itself to README and file-tree facts.
README Evidence
Project Knowledge MCP Server
  
A cross-project knowledge graph for the Model Context Protocol (MCP). Map features across mobile, backend, and admin codebases so your AI agent has full-stack context when testing, writing code, debugging, or adding features.
Source: https://github.com/punic-pillars/project-knowledge-mcp / Human Manual
Entrypoints and Runtime Surface
Related topics: Repository Overview, Architecture Evidence Map, Operations and Verification Boundaries
Continue reading this section for the full explanation and source context.
Related Pages
Related topics: Repository Overview, Architecture Evidence Map, Operations and Verification Boundaries
Entrypoints and Runtime Surface
The files below are the highest-signal candidates for how the project is installed, started, configured, or embedded. Treat this as an evidence map, not an inferred API contract.
| File | Evidence role | Size |
|---|---|---|
README.md | README/product and usage evidence | 16151 bytes |
package.json | package/runtime metadata | 1099 bytes |
src/config.ts | implementation surface | 5896 bytes |
src/index.ts | implementation surface | 3187 bytes |
src/tools.ts | implementation surface | 21360 bytes |
src/types.ts | implementation surface | 4058 bytes |
src/handlers/architecture.ts | implementation surface | 6431 bytes |
src/handlers/context.ts | implementation surface | 8894 bytes |
src/handlers/dispatch.ts | implementation surface | 3141 bytes |
src/handlers/feature.ts | implementation surface | 4260 bytes |
src/handlers/health.ts | implementation surface | 5354 bytes |
src/handlers/index.ts | implementation surface | 286 bytes |
Source: README.md:1-120
Source: https://github.com/punic-pillars/project-knowledge-mcp / Human Manual
Architecture Evidence Map
Related topics: Repository Overview, Entrypoints and Runtime Surface, Operations and Verification Boundaries
Continue reading this section for the full explanation and source context.
Related Pages
Related topics: Repository Overview, Entrypoints and Runtime Surface, Operations and Verification Boundaries
Architecture Evidence Map
This section maps source paths into likely architectural areas based on repository layout only. Claims that require execution are intentionally not made here.
.:README.md,package.jsonsrc:src/config.ts,src/index.ts,src/tools.ts,src/types.ts,src/handlers/architecture.ts,src/handlers/context.ts
Source: package.json:1-120
Source: https://github.com/punic-pillars/project-knowledge-mcp / Human Manual
Operations and Verification Boundaries
Related topics: Repository Overview, Entrypoints and Runtime Surface, Architecture Evidence Map
Continue reading this section for the full explanation and source context.
Related Pages
Related topics: Repository Overview, Entrypoints and Runtime Surface, Architecture Evidence Map
Operations and Verification Boundaries
Operational guidance is limited to files that are present in the repository. Before using this project in an agent workflow, verify install, quickstart, and runtime behavior in a sandbox.
- Documentation signal:
README.md - Runtime/package signal:
package.json - Source inspection signal:
src/config.ts - Source inspection signal:
src/index.ts - Source inspection signal:
src/tools.ts - Source inspection signal:
src/types.ts - Source inspection signal:
src/handlers/architecture.ts - Source inspection signal:
src/handlers/context.ts - Source inspection signal:
src/handlers/dispatch.ts - Source inspection signal:
src/handlers/feature.ts
Source: src/config.ts:1-120
Source: https://github.com/punic-pillars/project-knowledge-mcp / Human Manual
Doramagic Pitfall Log
Source-linked risks stay visible on the manual page so the preview does not read like a recommendation.
The project should not be treated as fully validated until this signal is reviewed.
Users cannot judge support quality until recent activity, releases, and issue response are checked.
The project may affect permissions, credentials, data exposure, or host boundaries.
The project may affect permissions, credentials, data exposure, or host boundaries.
Doramagic Pitfall Log
Doramagic extracted 6 source-linked risk signals. Review them before installing or handing real data to the project.
1. Capability assumption: README/documentation is current enough for a first validation pass.
- Severity: medium
- Finding: README/documentation is current enough for a first validation pass.
- User impact: The project should not be treated as fully validated until this signal is reviewed.
- Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
- Evidence: capability.assumptions | mcp_registry:io.github.batook22/project-knowledge-mcp:1.0.6 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.batook22%2Fproject-knowledge-mcp/versions/1.0.6 | README/documentation is current enough for a first validation pass.
2. Maintenance risk: Maintainer activity is unknown
- Severity: medium
- Finding: Maintenance risk is backed by a source signal: Maintainer activity is unknown. Treat it as a review item until the current version is checked.
- User impact: Users cannot judge support quality until recent activity, releases, and issue response are checked.
- Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
- Evidence: evidence.maintainer_signals | mcp_registry:io.github.batook22/project-knowledge-mcp:1.0.6 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.batook22%2Fproject-knowledge-mcp/versions/1.0.6 | last_activity_observed missing
3. Security or permission risk: no_demo
- Severity: medium
- Finding: no_demo
- User impact: The project may affect permissions, credentials, data exposure, or host boundaries.
- Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
- Evidence: downstream_validation.risk_items | mcp_registry:io.github.batook22/project-knowledge-mcp:1.0.6 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.batook22%2Fproject-knowledge-mcp/versions/1.0.6 | no_demo; severity=medium
4. Security or permission risk: no_demo
- Severity: medium
- Finding: no_demo
- User impact: The project may affect permissions, credentials, data exposure, or host boundaries.
- Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
- Evidence: risks.scoring_risks | mcp_registry:io.github.batook22/project-knowledge-mcp:1.0.6 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.batook22%2Fproject-knowledge-mcp/versions/1.0.6 | no_demo; severity=medium
5. Maintenance risk: issue_or_pr_quality=unknown
- Severity: low
- Finding: issue_or_pr_quality=unknown。
- User impact: Users cannot judge support quality until recent activity, releases, and issue response are checked.
- Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
- Evidence: evidence.maintainer_signals | mcp_registry:io.github.batook22/project-knowledge-mcp:1.0.6 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.batook22%2Fproject-knowledge-mcp/versions/1.0.6 | issue_or_pr_quality=unknown
6. Maintenance risk: release_recency=unknown
- Severity: low
- Finding: release_recency=unknown。
- User impact: Users cannot judge support quality until recent activity, releases, and issue response are checked.
- Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
- Evidence: evidence.maintainer_signals | mcp_registry:io.github.batook22/project-knowledge-mcp:1.0.6 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.batook22%2Fproject-knowledge-mcp/versions/1.0.6 | release_recency=unknown
Source: Doramagic discovery, validation, and Project Pack records
Community Discussion Evidence
These external discussion links are review inputs, not standalone proof that the project is production-ready.
Count of project-level external discussion links exposed on this manual page.
Open the linked issues or discussions before treating the pack as ready for your environment.
Community Discussion Evidence
Doramagic exposes project-level community discussion separately from official documentation. Review these links before using project-knowledge-mcp with real data or production workflows.
- README/documentation is current enough for a first validation pass. - GitHub / issue
Source: Project Pack community evidence and pitfall evidence