Agentpool
Related Servers
Alternatives to Agentpool
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceOne local memory every coding agent on your machine shares — Claude Code, Cursor, Claude Desktop, OpenCode. Answers from past sessions, commits, CLAUDE.md/AGENTS.md and ADRs with the exact source, and withholds work another agent has claimed so two agents don't rewrite the same thing.4381 PyPI1MIT
- AlicenseAqualityCmaintenancePersistent shared memory for AI coding agents. Stores facts as entity/key/value triples with hybrid semantic search, task checkpoints, and conflict resolution — shared across Claude Code, Codex CLI, and GitHub Copilot.16235 npm5AGPL 3.0
- AlicenseNot gradedqualityAmaintenanceA local-first memory for AI coding agents. AgentRecall turns the feedback and failures you run into while coding into reusable rules, then serves the right ones back — on the command line or directly to Claude Code over MCP. Everything stays on your machine: no cloud sync, no web UI, no API keys.9MIT
- AlicenseAqualityAmaintenanceSelf-hosted coding agent that runs Claude Code or Codex in your own infrastructure and works from Slack. Exposes codebase investigation, file edits, branch and PR creation, allowlisted command execution, CI status and an audit log as MCP tools, keeping every credential behind the tool layer instead of handing it to the model.1210 npm2MIT
- AlicenseNot gradedqualityAmaintenanceLocal-first memory for your AI agent. One SQLite file you own — offline, no API key. Plugs straight into Claude Code.Apache 2.0
- AlicenseAqualityAmaintenanceDurable, local-first memory for AI coding agents over MCP — zero-dependency (pure Python + SQLite/FTS5), curated and semantically de-duped. Works with Claude Code, Codex and any MCP host, and you own the data as plain rows.621AGPL 3.0
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: configuration management, threat reporting, and scanning specific targets (documents, input, memory, output, tool calls, tool definitions). No overlap or ambiguity.
All tools follow a consistent snake_case naming pattern with clear verb_noun structure: get_config, get_threat_report, update_config, and scan_* for all scanning tools. No mixing of conventions.
9 tools is well-scoped for a security scanning server; each tool addresses a distinct security concern without redundancy, covering configuration, reporting, and all major scan types.
The tool set comprehensively covers the domain of agent security: configuration management, threat reporting, and scanning for document poisoning, prompt injection, memory attacks, output leakage, tool call exploitation, and hidden payloads in tool definitions. No obvious gaps.