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.
npx agentmods add mcp/jessn-dev/agentic-scope/agenticscopegit clone --depth 1 https://github.com/jessn-dev/agentic-scopeGrade A, and why
agenticscope 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 yesterday.
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
{ "agenticscope": { "command": "npx", "args": [ "-y", "agenticscope" ] } }
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.
- yesterday First seen · 9 lines scan A 1955b02cba39
agenticscope is an MCP server published in the GitHub repository jessn-dev/agentic-scope (2 stars, last pushed 2mo 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
memory
Gives the agent a persistent knowledge graph it can write facts to and recall across sessions. Runs locally from the @modelcontextprotocol/server-memory npm package.
redmine-mcp-server
MCP server that lets AI assistants manage Redmine issues, projects, wikis, and time tracking. Runs locally from the redmine-mcp-server Python package. Needs 12 environment variables to run.
clio-compression
MCP server "clio-compression" as configured in iowarp/clio-kit. Launched with clio-kit mcp-server compression.
clio-paraview
MCP server "clio-paraview" as configured in iowarp/clio-kit. Launched with clio-kit mcp-server paraview.
clio-scientific-catalog
MCP server "clio-scientific-catalog" as configured in iowarp/clio-kit. Launched with clio-kit mcp-server scientific-catalog.
clio-arxiv
MCP server "clio-arxiv" as configured in iowarp/clio-kit. Launched with clio-kit mcp-server arxiv.