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/maplehilllabs/mcp-slack-listsInstalling this writes the configuration, not the program: `python` runs a file from the repository, so clone it first and make the path in the command match where you put it.
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/maplehilllabs/mcp-slack-lists/slack-lists)<a href="https://agentmods.dev/mcp/maplehilllabs/mcp-slack-lists/slack-lists"><img src="https://agentmods.dev/badge/mcp/maplehilllabs/mcp-slack-lists/slack-lists/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/maplehilllabs/mcp-slack-lists/slack-lists"><img src="https://agentmods.dev/badge/mcp/maplehilllabs/mcp-slack-lists/slack-lists.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
slack-lists 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 2mo 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
1 near-identical copy found in the catalogue:
- slack-lists — 100% identical, 0 lines differ
What it actually says
{
"slack-lists": {
"command": "python",
"args": [
"/path/to/slack-lists-mcp-server/src/slack_lists_server.py"
],
"env": {
"SLACK_BOT_TOKEN": "xoxb-your-bot-token-here"
}
}
}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.
- 2mo ago First seen · 11 lines scan A 9b78e7c2c86f
slack-lists is an MCP server published in the GitHub repository maplehilllabs/mcp-slack-lists (8 stars, last pushed 1y 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
mindwtr
Task and project automation for local and self-hosted Mindwtr Cloud data; read-only by default. Runs locally from the mindwtr-mcp npm package. Needs 3 environment variables to run.
delega
Task management API for AI agents. Create, delegate, and track tasks via MCP. Runs locally from the @delega-dev/mcp npm package. Needs 2 environment variables to run.
task-manager
MCP server "task-manager", hosted remotely at localhost, as configured in DrSkippy/task.md-utilities.
tasqr-mcp
Tasqr MCP server — task state management for AI agents. Runs locally from the tasqr-mcp Python package.
tasqr-mcp
Tasqr MCP server — task state management for AI agents. Runs locally from the tasqr-mcp npm package.
mcp
Read and run a user's task board: tasks, schedules, projects, and weekly/monthly/yearly goals. Remote server at app.dooit.so.