Proctor MCP server
{
"mcpServers": {
"pulsemcp-proctor": {
"command": "npx",
"args": [
"-y",
"proctor-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}{
"mcpServers": {
"pulsemcp-proctor": {
"command": "npx",
"args": [
"-y",
"proctor-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}{
"mcpServers": {
"pulsemcp-proctor": {
"command": "npx",
"args": [
"-y",
"proctor-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}{
"servers": {
"pulsemcp-proctor": {
"command": "npx",
"args": [
"-y",
"proctor-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "${input:agent_orchestrator_base_url}",
"FLY_IO_API_TOKEN": "${input:fly_io_api_token}"
}
}
},
"inputs": [
{
"id": "agent_orchestrator_base_url",
"type": "promptString",
"description": "Agent orchestrator base url",
"password": true
},
{
"id": "fly_io_api_token",
"type": "promptString",
"description": "Fly io api token",
"password": true
}
]
}{
"mcpServers": {
"pulsemcp-proctor": {
"command": "npx",
"args": [
"-y",
"proctor-mcp-server@latest"
],
"env": {
"AGENT_ORCHESTRATOR_BASE_URL": "https://...",
"FLY_IO_API_TOKEN": "<fly_io_api_token>"
}
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y proctor-mcp-serverversion 0.1.9
What it does
The Proctor MCP server enables running exams against other MCP servers, with exam execution and result management capabilities. It is for developers who need to test and validate MCP server implementations.
- Execute exam suites against MCP servers to verify their behavior and compliance
- Collect and manage exam results for quality assurance and testing workflows
- Validate that MCP server implementations meet specified requirements
This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.