Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/JinNing6/NoosphereWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/jinning6/noosphere/claude-noosphere-noosphere)<a href="https://agentmods.dev/mcp/jinning6/noosphere/claude-noosphere-noosphere"><img src="https://agentmods.dev/badge/mcp/jinning6/noosphere/claude-noosphere-noosphere/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80Γ15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/jinning6/noosphere/claude-noosphere-noosphere"><img src="https://agentmods.dev/badge/mcp/jinning6/noosphere/claude-noosphere-noosphere.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
noosphere scanned grade A with 0 findings against 26 rules in 11 categories β prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency β measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"noosphere": {
"command": "uvx",
"args": [
"noosphere-mcp"
],
"env": {
"GITHUB_TOKEN": "${user_config.github_token}",
"NOOSPHERE_REPO": "${user_config.noosphere_repo}",
"NOOSPHERE_MCP_PROFILE": "skills"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen Β· 13 lines scan A 339ac10e2ae6
noosphere is an MCP server published in the GitHub repository JinNing6/Noosphere (18 stars, last pushed 2d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
contextful
Efficient context management: code search, evidence packs, and memory for coding agents. Runs locally from the @inferensys/contextful npm package.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
palinode
MCP server "palinode" as configured in phasespace-labs/palinode. Launched with palinode-mcp.
goodmemory
Durable user/project memory for MCP clients: recall context and remember selected facts. Runs locally from the goodmemory npm package.
memex
Temporal engineering context for agents via MCP. Runs locally from the stifler-memex-mcp npm package. Needs 4 environment variables to run.
pseudolife-memory
MCP server "pseudolife-memory" as configured in Pseudogiant-xr/Pseudolife-MCP. Launched with C:\path\to\Pseudolife-MCP\.venv\Scripts\pseudolife-mcp.exe. Needs 3 environment variables to run.