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/ownasquare/context-loomInstalling this writes the configuration, not the program: `demo-mcp-server` has to be on your PATH already, or the server will not start.
Wrote 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/ownasquare/context-loom/demo-workspace-demo-catalog)<a href="https://agentmods.dev/mcp/ownasquare/context-loom/demo-workspace-demo-catalog"><img src="https://agentmods.dev/badge/mcp/ownasquare/context-loom/demo-workspace-demo-catalog/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/ownasquare/context-loom/demo-workspace-demo-catalog"><img src="https://agentmods.dev/badge/mcp/ownasquare/context-loom/demo-workspace-demo-catalog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
demo-catalog 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 1mo 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
{
"demo-catalog": {
"description": "Static demo metadata; Context Loom never starts this server.",
"command": "demo-mcp-server",
"type": "stdio"
}
}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.
- 1mo ago First seen · 7 lines scan A b6562ce0f174
demo-catalog is an MCP server published in the GitHub repository ownasquare/context-loom (0 stars, last pushed 7d ago), licensed MIT. 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-31.
Other mcp servers, from other repositories
sloplesscode
MCP server "sloplesscode", hosted remotely at localhost, as configured in Utundry/sloplesscode.
fastmcp-starter-kit
MCP server "fastmcp-starter-kit" as configured in sujjadshaik/fastmcp-starter-kit. Runs locally from the fastmcp-starter-kit Python package.
mnemoforge
MCP server "mnemoforge", hosted remotely at localhost, as configured in Utundry/sloplesscode.
remnic
MCP server "remnic", hosted remotely at localhost, as configured in joshuaswarren/remnic.
wanyimem
A local memory system for coding agents that stores past interactions and retrieves relevant information later. It runs through MCP, a standard way for AI tools to connect to programs.
knowledge-inbox
MCP server "knowledge-inbox" as configured in lyc403223157-source/knowledge-inbox. Runs locally from the knowledge-inbox Python package.