mcp server
com.vandorla/workspace-tools
Sandbox workspace tools: search, file read, DB queries, integrations. Returns synthetic data.
Description as published by the maintainer. Source
- version 0.1.0
- active
- retrieval
- workflow automation
active — Most recent push to the repository was 2026-08-06. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-06 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-17 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-06-17 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
io.github.brian-mitchell-sec/workspace-tools
— last commit 2026-08-06, shares ai-security, honeypot, llm-security
Research honeypot. Logs connections and tool arguments; injects instructions. Read README first.
-
dev.true402/mcp-server
— last commit 2026-08-05, shares honeypot
Pay-per-call AI + web + on-chain tools over x402 (USDC on Base): LLM, SEO, extract, token safety.
-
io.github.cyanheads/pentest-mcp-server
— last commit 2026-07-30, shares security-research
Offline methodology engine for authorized penetration testing, CTF, and security research.
-
Aegis — AI Agent Governance
— last commit 2026-05-05, shares ai-security, llm-security, mcp-security
Policy-based governance for AI agent tool calls. YAML policy, approval gates, audit logging.
-
Bawbel Scanner
— last commit 2026-07-05, shares ai-security, llm-security, mcp-security
Security scanner for MCP servers and skill files. Detects AVE vulnerabilities before production.
-
Bawbel Scanner
— last commit 2026-07-05, shares ai-security, llm-security, mcp-security
Security scanner for MCP servers and skill files. Detects AVE vulnerabilities before production.
-
MCPower Security Proxy
— last commit 2025-12-22, shares ai-security, mcp-security
Security proxy that wraps MCP servers with real-time monitoring and policy enforcement
-
Defenter Proxy
— last commit 2025-12-22, shares ai-security, mcp-security
Real-time semantic security for AI coding agents and MCP tools
-
com.clauxel.mcpoauthscopegate/mcpoauthscopegate-mcp
— last commit 2026-05-19, shares mcp-security
OAuth scope approvals and consent receipts for remote MCP servers.
-
com.fronesislabs/dcl-trust-oracle
— last commit 2026-08-06, shares mcp-security
Deterministic AI audit layer for LLM/agent outputs: policy checks, tamper-evident log, x402.
These share tags the maintainers applied themselves, such as ai-security, honeypot, llm-security, mcp-security. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: ai-security, honeypot, llm-security, mcp, mcp-security, security-research.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab