MCP.Market

Proctor MCP server

by pulsemcp.com·com.pulsemcp/proctor·v0.1.9·80 stars
No reviews yet

MCP server for running Proctor exams against MCP servers with exam execution and result management.

A85/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
Growing

80 stars

Reviews

Write one

Nobody has reviewed Proctor yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Proctor tools (6, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • cancel_examwrite action

    Cancel a running Proctor exam. Stops an exam that is currently executing on a Fly machine. This is useful when you need to abort a test that is taking too long or encountering issues. **Returns:** - Result object indicating the cancellation status **Use cases:** - Stop a stuck or slow exam - Cancel a test started with wrong parameters - Free up resources for other tests - Gracefully terminate a ru

  • destroy_machinewrite action

    Delete a Fly.io machine. Permanently removes a Fly machine that was used for Proctor exam execution. Use this to clean up machines that are no longer needed. **Returns:** - success: boolean indicating if the machine was deleted **Use cases:** - Clean up machines after exam completion - Remove stuck or failed machines - Free up resources - Remove machines that are no longer needed **Warning:** - Th

  • get_machines

    List active Fly.io machines used for Proctor exams. Returns information about currently running or recently active Fly machines that are being used for exam execution. **Returns:** - machines: Array of machine objects with id, state, region, and other metadata **Use cases:** - Monitor active exam execution infrastructure - Find machines to clean up or cancel - Debug issues with running exams - Che

  • get_proctor_metadata

    Get available runtimes and exams for Proctor testing. Returns the list of available runtime environments (Docker images) and exam types. **Returns:** - runtimes: Array of runtime configurations with id, name, and Docker image - exams: Array of exam types with id, name, and description **Use cases:** - Discover available runtime environments - Find the correct exam ID for a specific test type - Che

  • my-mcp-server

    A helpful MCP server

  • run_examwrite action

    Execute a Proctor exam against an MCP server. Runs the specified exam using the provided runtime and MCP configuration. The exam tests the MCP server's functionality and returns detailed results. **Returns:** - Streaming logs showing exam progress - Final result with status and detailed test outcomes **Use cases:** - Test an MCP server's initialization and tool listing - Verify authentication mech

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan35 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 27 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Proctor compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 70% of 48,255 servers
Tools
6
the typical server has 7
Tools that change things
50%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
80
more than 95% of 28,688 servers

What its tools let an agent do: 3 read · 2 delete · 1 run or deploy

Install Proctor in Claude Code, Cursor or VS Code

Runs npx -y proctor-mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add proctor -- npx -y proctor-mcp-server
Add to Cursor

What the publisher says

From the Proctor repository's README, as published. We do not edit it. Read it on GitHub

PulseMCP's MCP Servers

We build reliable servers thoughtfully designed for MCP Client-powered workflows.

Design principles

You can have confidence that any Pulse-branded MCP server was built with these north stars in mind:

  1. Purpose-built. LLM-powered MCP clients offer uniquely new user interaction patterns that necessitate a different layer of abstraction than the REST API's from a pre-AI era. We thoughtfully scope drawing lines like building a new server, versus incorporating a new feature in another server. Or deciding where one slew of REST API endpoints might be better packaged as a single Tool call. And more.
  2. Easy set up. Many MCP servers die before ever getting a chance to be used. We offer guides and a frustration-free experience to get going with our MCP servers inside your favorite MCP clients.
  3. Time savings. By minimizing the number of tool chain steps or conversational turns you need to accomplish a task, our MCP servers will save you (and your agents) time waiting for a task to be completed.
  4. Inference cost savings. By minimizing the number of tokens you need to consume to a accomplish a task, our MCP servers will save you on your LLM inference bills.
  5. Reliability. You should have confidence that you can deploy our servers in a production application serving mass market consumers or business clients.
  6. Future-proof. We sit on the bleeding edge of the MCP specification, working to push the ecosystem forward. As such, you can be sure that if you commit to baking our server into your workflow, it will self-improve over time to take advantage of the latest and greatest MCP features.

Servers Available

Productionized Servers

These are PulseMCP-branded servers that we intend to maintain indefinitely as our own offerings.

The MCP Registry column controls whether the server is published to the official MCP Registry (com.pulsemcp/) by the publish-mcp-registry.yml workflow.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Proctor: common questions

Is Proctor MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the Proctor safety report
How do I install Proctor?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Proctor need an API key?
Yes. The registry entry asks for PROCTOR_API_KEY.
Is Proctor maintained?
The last commit was 66 days ago (2026-08-30). The latest release is v0.1.9.
How does Proctor compare with other MCP servers?
safety score 85/100 (higher than 70% of 48,255 servers); tools 6 (the typical server has 7); tools that change things 50% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from pulsemcp.com →