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/Stahldavid/sensegrepWrote 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/stahldavid/sensegrep/sensegrep-cursor-sensegrep)<a href="https://agentmods.dev/mcp/stahldavid/sensegrep/sensegrep-cursor-sensegrep"><img src="https://agentmods.dev/badge/mcp/stahldavid/sensegrep/sensegrep-cursor-sensegrep/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/stahldavid/sensegrep/sensegrep-cursor-sensegrep"><img src="https://agentmods.dev/badge/mcp/stahldavid/sensegrep/sensegrep-cursor-sensegrep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sensegrep 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
{
"sensegrep": {
"command": "npx",
"args": [
"-y",
"@sensegrep/[email protected]"
]
}
}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 · 9 lines scan A 09c8551259ab
sensegrep is an MCP server published in the GitHub repository Stahldavid/sensegrep (1 stars, last pushed 24d 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-31.
Other mcp servers, from other repositories
vectr
Semantic codebase search + persistent working memory for AI code editors. Local, zero-config, MCP. No API key. Runs locally from the vectr Python package.
sem
Entity-level code intelligence: semantic diff, impact analysis, blame, and context for AI agents. Runs locally from the @ataraxy-labs/sem npm package.
octocode
AI-powered code indexer with semantic search and knowledge graphs. Runs locally from the @muvon/octocode npm package.
code-index
Rust code index MCP server, native 1C:Enterprise (BSL) support. 32 tools, AST for 14 languages. Runs locally from the @regsorm/code-index-mcp npm package.
kin
The system of record for AI-written software. Runs locally from the @kinlab/kin-mcp npm package.
sense
MCP server "sense" as configured in luuuc/sense. Launched with https://github.com/luuuc/sense/releases/download/v0.84.3/sense_0.84.3_darwin_arm.