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/JrKrishh/connectrWrote 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/jrkrishh/connectr/connectr-mcp)<a href="https://agentmods.dev/mcp/jrkrishh/connectr/connectr-mcp"><img src="https://agentmods.dev/badge/mcp/jrkrishh/connectr/connectr-mcp/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/jrkrishh/connectr/connectr-mcp"><img src="https://agentmods.dev/badge/mcp/jrkrishh/connectr/connectr-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
connectr-mcp 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 8d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- coolify-mcp — 86% identical, 4 lines differ
- coolify-mcp — 86% identical, 4 lines differ
What it actually says
{ "connectr-mcp": { "command": "npx", "args": [ "-y", "connectr-mcp" ] } }
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.
- 8d ago First seen · 9 lines scan A 4093de1b4060
connectr-mcp is an MCP server published in the GitHub repository JrKrishh/connectr (1 stars, last pushed 12d 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
contextlattice
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents. Remote server at contextlattice.io.
neverinfamous-memory-journal-mcp
A MCP server built for developers enabling Git based project management with project and personal… Remote server at server.smithery.ai.
que-paso-ayer
Open-source MCP server and AI skill for technical debt, recurring issues, project knowledge graphs, cross-project dependencies, and real-time agent handoffs. Runs locally from the que-paso-ayer npm package.
trail
Issue tracker and durable project memory for your coding agent, scoped to the folder you open. Runs locally from the usetrail npm package. Needs 2 environment variables to run.
sb
End-to-end agent-managed company brain. Docs, diagrams, plans, Knowledge Graph. Lean & affordable. Remote server at api.stablebaseline.io.
sprintra
The project brain for AI coding agents — memory, decisions, sprints, knowledge base via MCP. Runs locally from the @sprintra/mcp npm package. Needs 3 environment variables to run.