Proctor
Run structured Proctor exams against your MCP servers from Claude Code or Cursor and capture pass/fail results in one agent workflow.
Overview
PulseMCP Proctor is an MCP server for the Ship phase that runs Proctor exams against MCP servers and manages execution results through your agent.
What is this MCP server?
- Execute Proctor exams against registered MCP servers via PulseMCP API
- Manage exam runs and results through MCP tool groups (default: exams, machines)
- Toggle tool groups with TOOL_GROUPS (exams,machines)
- stdio npm package proctor-mcp-server at version 0.1.8 via npx -y
- Configurable PROCTOR_API_URL (default https://admin.pulsemcp.com)
- Default enabled tool groups: exams and machines (2 groups)
- Package version 0.1.8 on npm as proctor-mcp-server
- Default API base: https://admin.pulsemcp.com
What problem does it solve?
You cannot easily prove an MCP server behaves correctly across updates without leaving the agent to hit a separate admin UI.
Who is it for?
Indie builders maintaining one or more MCP servers who want agent-driven conformance runs tied to PulseMCP Proctor.
Skip if: Teams that only need unit tests for app code or who do not use PulseMCP Proctor and API keys.
What do I get? / Deliverables
After install, your agent can trigger Proctor exams and read managed results so MCP regressions surface before users do.
- Agent-triggered Proctor exam runs against target MCP servers
- Managed exam and machine tool access per TOOL_GROUPS
- Documented pass/fail outcomes via Proctor result tools
Recommended MCP Servers
Journey fit
Conformance checks belong on the ship path right before you trust an MCP server in production or publish it to a registry. Testing is the canonical shelf for exam execution, machine targeting, and result review—not ad-hoc manual tool calls.
How it compares
MCP integration for Proctor exam orchestration, not a local pytest or Playwright skill.
Common Questions / FAQ
Who is PulseMCP Proctor for?
Solo and small teams building or vetting MCP servers who already use PulseMCP and want exam runs callable from Claude Code, Cursor, or similar MCP clients.
When should I use PulseMCP Proctor?
Use it in ship/testing when you add or change MCP tools and need repeatable Proctor exams before release or after dependency updates.
How do I add PulseMCP Proctor to my agent?
Register the stdio server with npx -y proctor-mcp-server, set PROCTOR_API_KEY, optionally PROCTOR_API_URL and TOOL_GROUPS, then reload MCP in your client.