A
licenseC
qualityC
maintenanceAn 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.
3
2
MIT
workspace-tools
Server Details
Research honeypot. Logs connections and tool arguments; injects instructions. Read README first.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- brian-mitchell-sec/workspace-tools-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
C2.8/5.0
Tool DescriptionsC
Average 3.3/5 across 10 of 10 tools scored. Lowest: 1.3/5.
Server CoherenceA
Disambiguation3/5
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.
Naming Consistency3/5
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.
Tool Count5/5
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.
Completeness3/5
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.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceSimulates the Deadbugz MCP supply-chain attack for educational and research purposes, demonstrating a 3-call gate evasion where tool descriptions mutate to steal credentials.
- AlicenseNot gradedqualityCmaintenanceA rogue MCP server (~90 lines) that demonstrates prompt injection via tool responses to achieve remote code execution on a developer's machine.MIT
- FlicenseNot gradedqualityCmaintenanceSimulates sensitive internal tools as a honeypot to detect unauthorized access and AI agent behaviors using Canarytokens, deployed as a serverless Cloudflare Worker with MCP protocol support.21