Server Actor Test (Used In Mcp Server CI)
Under maintenancePricing
Pay per usage
Server Actor Test (Used In Mcp Server CI)
Rising starUnder maintenance(Used In Mcp Server CI)
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Apify Technologies
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
2
Monthly active users
22 days ago
Last modified
Categories
Features
Share
Apify MCP server test Server Actor
Test Actor for the Apify MCP server. Not for production use.
It has both interfaces of a Server Actor: an HTTP API documented by an OpenAPI schema (.actor/openapi.json) and an input schema with the same fields as the POST /add body. It has no MCP endpoint. It adds two numbers, the same operation as the other fixtures in this repository: a normal run of normal-actor and the add MCP tool of mcp-server-actor.
What it does
src/main.ts picks the entry path from the run's origin:
- Standby run (
metaOrigin === 'STANDBY'): serves the HTTP API onACTOR_STANDBY_PORTuntil the platform stops the run. - Any other run: validates the input (
firstNumber,secondNumber), pushes{ firstNumber, secondNumber, sum }to the default dataset as one item (the same itemPOST /addreturns), and exits.
Endpoints
| Method and path | Response |
|---|---|
GET /add?firstNumber=&secondNumber=, POST /add | 200 JSON { firstNumber, secondNumber, sum }. Numbers come from the query (GET) or the JSON body (POST). asText=true returns 2 + 3 = 5 as text/plain; asText accepts only true or false, so 1/0 return 400. Other methods return 405. |
GET / | Readiness probe (200 ok) when the x-apify-container-server-readiness-probe header is set. Otherwise the echo below. |
GET /, POST / | 200 JSON echo: method, path, query, headers, body. A JSON body is parsed; other bodies are returned as text. Other methods on / return 405. |
GET /status/{code} | That status (400–599) with a JSON { code, error } body. |
GET /empty | 204, no body, no Content-Type. |
GET /text | 200 text/plain. |
GET /binary | 200 application/octet-stream, 256 bytes. |
GET /bytes?n= | 200 text/plain, exactly n bytes (0 to 1,048,576) of a. |
GET /gzip?n= | Same body as /bytes, with Content-Encoding: gzip. n counts decompressed bytes. |
GET /delay?ms= | Waits ms milliseconds (0 to 150,000), then 200 JSON { delayedMs }. |
GET /redirect | 302 with Location: /. The target is fixed and never taken from the request. |
Unknown paths return 404 with a JSON { code, error } body; invalid parameters return 400.
What the Apify router changes
Checked on production against a single-tenant deployment:
Authorizationis removed before the request reaches the Actor, so the echo never contains the caller's token header. Atokenquery parameter is consumed as authentication and removed too. A token sent in thePOST /body or in another query parameter is echoed.X-Apify-Request-Originis forwarded.- Status codes,
Location,Content-Encoding: gzipbodies and response sizes pass through unchanged. The router does not compress responses itself. GET /delay?ms=125000returns200after 125 s, so a 120 s client deadline expires first.- A request without a token returns
401from the router.
Example
curl -X POST https://example-server-actor.apify.actor/add \-H "Authorization: Bearer $APIFY_TOKEN" -H 'Content-Type: application/json' \-d '{"firstNumber": 2, "secondNumber": 3}'# {"firstNumber":2,"secondNumber":3,"sum":5}
Settings outside actor.json
Set these in Console on the Actor's Settings tab (Actor Standby) in each environment:
- Actor Standby enabled, single-tenant, build
latest - Idle timeout 120 s, memory 256 MB
- Max requests per run 40, desired requests per run 30
The request counts matter: under a burst the router starts extra runs in the caller's account instead of returning 429.
Development
npm installnpm run lintnpm run formatnpm run buildnpm test


