crowd-test-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_crowd_test | Send a crowd of AI virtual users at a URL and return the damage summary. Only test sites the user owns or has permission to test. A run drives real browsers and typically takes several minutes; more personas and higher verify levels take longer. Args: url: The website to test. personas: Comma-separated built-in persona names, "all", or "none". mob: Additionally generate this many random virtual users. seed: Random seed making a mob reproducible. goal: Extra mission given to every persona. verify: Verification depth: "none", "detective" (independent agent re-checks critical/major findings), "cross" (adds a Playwright cross-engine probe; default), or "tribunal" (adds a Microsoft Webwright agent as a third harness). provider: "auto" (default, from env keys), "anthropic", or "openai". model: Model id override. max_steps: Max browser actions per persona. concurrency: How many personas browse at once. out_dir: Report directory (default: ~/crowd-test-reports/-). |
| list_personasA | List the built-in ringleader personas and what each one catches. |
| preview_mobB | Preview the random mob members a given count/seed would generate. |
| read_reportA | Return the newest crowd-test markdown report under a directory. Defaults to ~/crowd-test-reports, where run_crowd_test writes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/anhhuyn411-alt/crowd-test-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server