testing-local-server

Validate CIVITAE/SIGNOMY local server health, state, security headers, routing, provisioning, MCP, and WebSocket behavior.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/SunrisesIllNeverSee/agent-universe --skill testing-local-server
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-local-server
Source: https://github.com/SunrisesIllNeverSee/agent-universe/tree/main/.agents/skills/testing-local-server
Command: npx skills add https://github.com/SunrisesIllNeverSee/agent-universe --skill testing-local-server

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken local environments by giving you a concrete checklist to confirm that the CIVITAE/SIGNOMY server boots correctly and that key HTTP, MCP, and WebSocket behaviors work as expected before you trust CI or deploy.

Core Features & Use Cases

  • Start and validate the server locally: Run the server in dev mode and confirm expected startup conditions with no import errors or tracebacks.
  • Verify critical routes and JSON behaviors: Check health state, server posture/state endpoints, landing page security headers, and marketplace redirect behavior.
  • Test operational integrations: Validate the MCP JSON-RPC bridge and confirm WebSocket connectivity remains stable.
  • Use cases: Dependency upgrades, routing changes, middleware behavior changes, MCP bridge changes, or WebSocket functionality regressions.

Quick Start

Start the server locally in dev mode and run the endpoint checks to confirm /health, /api/state, / security headers, /kassa redirect, /api/provision/signup, /mcp, and the /ws WebSocket upgrade all behave as expected.

Frequently Asked Questions about testing-local-server

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate local server functionality before running CI?

You can verify local server functionality by booting the server in dev mode and checking health, state, security headers, routing redirects, provisioning, MCP JSON-RPC, and WebSocket endpoints to catch runtime regressions before CI.

How does testing a local MCP JSON-RPC bridge work?

Testing a local MCP JSON-RPC bridge works by sending requests with correct Accept headers to the /mcp endpoint and asserting deterministic JSON responses to confirm the bridge behavior functions without import errors.

What security headers and routing redirects should I check during local testing?

During local testing you should check landing page security headers and marketplace routing redirects, specifically validating the /kassa redirect behavior to ensure middleware and routing changes operate correctly.

Do I need Python 3.11 and dev mode enabled for local server validation?

Yes, local server validation requires Python 3.11+ with dev mode enabled and an authenticated-free local path via CIVITAE_DEV_MODE=1 to properly exercise HTTP endpoints and WebSocket behavior.

Why is my WebSocket connectivity not working after a dependency upgrade?

WebSocket connectivity may fail after a dependency upgrade if runtime regressions occurred, so you should verify the /ws WebSocket upgrade behavior locally in dev mode before deployment.