Eval Engine API MCP Server

by invertedhoologan Your server? Claim it

answering

Eval Engine API is answering right now. Last checked 4 min ago.

Pay-per-call AI evaluation MCP server. Score LLM outputs against benchmark rubrics via Workers AI.

Uptime history 91 days of history · worst day 0%

91 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

140 ms

Response time

average over 24h

authentication required

Access

streamable-http

Eval Engine API does not always answer

Over the last week it answered 95.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add eval-engine-mcp --transport http https://eval.zuluworksai.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://eval.zuluworksai.com/mcp

~/.codex/config.toml

[mcp_servers.eval-engine-mcp]
url = "https://eval.zuluworksai.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "eval-engine-mcp": {
      "url": "https://eval.zuluworksai.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "eval-engine-mcp": {
      "type": "http",
      "url": "https://eval.zuluworksai.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://eval.zuluworksai.com/mcp	streamable-http	needs auth	155 ms	4 min ago

Alternatives to Eval Engine API

same job, measured the same way

Toolroute

by grossiweb

Route AI agent tasks to the best MCP server and LLM, scored on 132+ real benchmark executions.

3 396 installs/wk local only

MCP Scorecard MCP

by csoai-org

Score any MCP server against a 100-point production-readiness rubric (static AST + PyPI +...

100 installs/wk local only

JSON Repair MCP

by grupoanesthy-spec

Repairs malformed JSON from LLM output, validated against a schema. Paid per call via Stripe.

37 installs/wk local only

AI Eval

by lazymac2x

Cloudflare Workers MCP server: ai-eval

3 tools answering

operant-mcp

by saagpatel

Read-only MCP server for the OPERANT AI operating-agent calibration benchmark.

41 installs/wk 5 tools answering

Agent Workflow Engine

by lazymac2x

Cloudflare Workers MCP server: agent-workflow-engine

5 tools answering

LLM Output Quality Monitor

by lazymac2x

Cloudflare Workers MCP server: llm-output-quality-monitor

5 tools answering

Donovanh

by donovanh

MCP server for Lightning Tools — pay-per-call AI tools via Bitcoin Lightning

61 installs/wk local only

Eval Engine API — questions

Answers built from our own checks of this server.

Why is there no tool list for Eval Engine API?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Eval Engine API working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 140 ms. The bar chart above shows every period we have measured.

How do I connect Eval Engine API?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does Eval Engine API need an API key?

Yes. Every time we knock, Eval Engine API answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Eval Engine API?

It answers our handshake in 140 ms on average, which is faster than 86% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.