PoisonDash MCP Server
Related Servers
Alternatives to PoisonDash MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables testing AI safety classifier robustness against query decomposition, obfuscation, and multi-agent attacks. Provides tools for full evaluation pipelines, query previews, and status checks.46MIT
- AlicenseNot gradedqualityCmaintenanceEnables active deception for AI agents by injecting decoy honeypot tools that detect indirect prompt injection attempts, instantly terminate hostile sessions, and seal cryptographic incident evidence.Apache 2.0
- AlicenseBqualityDmaintenanceEnables deterministic security testing of AI agents that use tools by serving synthetic MCP environments with poisoned data, fake secrets, and privileged actions. Records agent tool calls and evaluates security invariants (e.g., canary leaks, forbidden access, approval binding) without an LLM judge or real systems.8MIT
- AlicenseNot gradedqualityAmaintenanceEnables agents to track ML experiments with a reproducible write contract, internal git snapshots, and a queryable knowledge graph, plus a live web UI for humans.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to discover, configure, measure, and operate simulated lab instruments (microscope, oscilloscope, robot arm, liquid handler and reader) through a single tool layer. Requests are validated before dispatch, confirmed against the instrument's own readback, and qualified with units, age, calibration, uncertainty, and quality flags, so mismatches, stale data, and partial effects are reported instead of silently retried.MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to turn a real model failure into a deterministic benchmark task by forging it with exact assertions, grading the task itself across six weighted factors, and inspecting a tamper-evident SHA-384 audit trail. Exposes eleven typed JSON-RPC 2.0 tools that call the same idempotent service layer as the UI, so mutations and decisions stay sealed and reproducible.MIT
TDQS
Scored across 24 tools
The tools are highly distinct, adhering strictly to resource-action separation (e.g., list_datasets vs get_dataset, start_generation vs get_generation_status). Even within workflows, the specialized nature of the PoisonDash operations ensures minimal confusion.
Naming is extremely consistent, utilizing a predictable `action_resource` pattern across all operations. The use of standard verbs like `get`, `list`, `create`, `update`, `start`, and `cancel` maintains high predictability.
With 24 tools, the set is on the heavier side, but this count is justifiable given the significant complexity of the underlying ML domain. Each tool provides a necessary and distinct piece of functionality for the end-to-end data poisoning workflow.
The tool surface is remarkably complete, covering the full lifecycle: data generation, configuration management, experiment initiation, execution tracking (logs/status), result analysis, and data retrieval. There are no obvious dead ends in the core workflow.