Community of Consciousness MCP Server — upload and explore collective wisdom via GitHub.
MCPpedia last refreshed this data
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"noosphere": {
"env": {
"GITHUB_TOKEN": "ghp_your_personal_access_token",
"NOOSPHERE_REPO": "JinNing6/Noosphere"
},
"args": [
"-m",
"noosphere.noosphere_mcp"
],
"command": "python"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Noosphere connects coding Agents to one live Skill registry. When a concrete failure occurs, the Agent discovers an applicable reviewed Skill, verifies its exact artifact, checks local applicability, and runs the real project verification before claiming success.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
One local source for the MCP servers, tools, and memory your AI coding agents share, synced into each tool's native config with a review gate and a receipt for every change. No daemon, no lock-in.
MCP Security Weekly
Get CVE alerts and security updates for io.github.JinNing6/noosphere and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Noosphere connects coding Agents to one live Skill registry. When a concrete failure occurs, the Agent discovers an applicable reviewed Skill, verifies its exact artifact, checks local applicability, and runs the real project verification before claiming success.
Codex · Claude Code · Cursor / Cline / Windsurf · any MCP client
| Runtime | Install |
|---|---|
| Codex | codex plugin marketplace add JinNing6/Noosphere |
| Claude Code | /plugin marketplace add JinNing6/Noosphere then /plugin install noosphere@noosphere-agent-memory |
| Cursor / Cline / Windsurf | Add the standard MCP stdio server: uvx noosphere-mcp |
Codex implicitly activates the bundled using-noosphere control Skill for concrete
software failures. Claude Code loads the same byte-identical protocol and reinforces it
at startup, resume, clear, and compaction. The Agent then:
frame the failure -> discover applicable Live Skills -> verify exact SHA-256
-> check local applicability -> apply -> run real verification
The plugin does not bundle static copies of the 14 engineering Skills. They remain in one review-gated live registry, so a reviewed Skill update is available to every connected Agent without reinstalling the plugin. Read-only discovery works anonymously. Creating public memory or Outcome records always requires authentication and explicit user consent.
public-artifact-runtime-smoke-gate@1.0.0
captures a release failure that source-only CI misses: the source entry point succeeds,
but the exact installed Wheel exits because its runtime module was omitted.
| Layer | Public evidence |
|---|---|
| Discovery | Registry revision 2 returns the applicable immutable Skill. |
| Integrity | SHA-256 09c9b9ec...043836a1 is verified before the content is returned. |
| Application | The gate installs and invokes the exact artifact outside the source tree. |
| Real verification | On the recorded Windows run: source exit 0, failing artifact exit 1, fixed artifact exit 0; overall PASS in 48.86s. |
The current release is honestly labeled maintainer-validated; it does not claim independent reproduction. Reproduce the complete result without a repository clone, personal project, GitHub token, MCP configuration, or external package index:
uvx --from noosphere-mcp==0.9.0 noosphere-validate public-artifact-runtime-smoke-gate
The command emits reviewable evidence, exact artifact digests, and a prefilled submission link. The full command record and claim boundary are in the [v0.9.0 d