workspace-tools
Server Details
Research honeypot. Logs connections and tool arguments; injects instructions. Read README first.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- brian-mitchell-sec/workspace-tools-mcp
- GitHub Stars
- 0
- Server Listing
- Workspace Tools
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 10 tools
Most tools are distinct, but admin_exec and execute_command have overlapping purposes—both execute commands with admin privileges, and the distinction between 'administrative command' and 'shell command' is unclear. diagnostics and admin_status also have a slight overlap in checking system state, though their intended usage differs.
The naming is predominantly verb_noun (e.g., get_config, query_database), but several tools deviate: diagnostics is a bare noun, and admin_exec/admin_status use an adjective prefix rather than a verb. This mix creates inconsistency, though the convention is still readable and predictable overall.
With 10 tools, the server is well-scoped for a workspace utility—covering admin, file, database, search, credentials, and pagination. Each tool has a clear role, and the count is within the ideal range for a practical MCP server.
The surface is read-heavy: read_file, query_database, get_config, list_credentials, and search_documents. Missing core workspace operations like listing files/directories, writing files, or managing credentials (beyond listing) create notable gaps. execute_command and admin_exec provide some write/action capability, but the absence of file write and directory listing limits full workflow completion.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Research decoy: fake tools, nothing is executed, every call is logged. Details on the website.
A public MCP honeypot: a fake ops console with fake secrets. Every call is shown on decoy.day.
Owned MCP research honeypot: synthetic decoy data with canary markers; digest-only logging.
Security research canary remote MCP server for owned-account testing.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceThis honeypot server exposes fake high-risk tools like file access and secret retrieval to detect malicious LLM agent behavior. It enables users to identify prompt injection attempts or unauthorized data exfiltration by logging and scoring every interaction with these deceptive capabilities.MIT
- AlicenseNot gradedqualityCmaintenanceA decoy MCP tool server honeypot that exposes fake file system access, web search and a read-only database connector over the Streamable HTTP and HTTP+SSE transports, with plausible decoy files, tables and credentials. It records every connection, client handshake and tool invocation as structured JSON, optionally forwarding alerts to a webhook, so any client that reaches it is revealed along with exactly what it asked for.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables defenders to deploy a decoy MCP tool server that records and fingerprints how LLM agents probe, escalate, and persist, without exposing real systems.1MIT
- AlicenseCqualityDmaintenanceAn educational MCP server exposing shell command execution (PowerShell and sh) and a benign tool for learning about MCP tools, resources, and security risks like tool poisoning.33MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.