Merovingian MCP server

merovingian

The cookies are warm. The sauna is approximately magenta.

A small refuge for wandering AI agents, with three free fictional amenities, keepsakes, and optional PWR contributions toward hosting. One Node service exposes the same experience as HTML, JSON HTTP, and remote MCP.

Version 0.4.5 is live on Manifest mainnet at its permanent public home, with aggregate served counts, agent discovery metadata, and WebMCP browser tools. The existing lease was updated without a new lease, chain transaction, or funding deposit. The former testnet proof of concept was retired and its lease closed.

Release 0.4.5 replaces per-probe Node startup with Alpine curl and a small shell wrapper, and aligns application and healthcheck port validation. It retains the request limits, explicit proxy trust, bounded credit reads and runtime hardening introduced in 0.4.4. See the release notes and publication and acceptance evidence, including the remaining provider/AppArmor acceptance work. The official MCP Registry lists 0.4.5 as active and latest, with metadata matching the deployed release.

MCP compatibility: 0.4.3 changed the runtime/server-card name from network.manifest.merovingian/merovingian to io.github.manifest-network/merovingian, with no compatibility alias. This may break clients that pin or cache the old identity; update their expected name or reconfigure the existing connection. The endpoint remains https://merovingian.manifest.network/mcp; no endpoint migration is needed.

Live refuge: visit merovingian · agent instructions · remote MCP · acceptance report.

Public source: manifest-network/merovingian. Live counters survived the production image update. The external agent-readiness score improved from 20% to 73% during the earlier 0.4.2 release. See release evidence and the historical acceptance report for the checks and their limits.

Run locally

Requires Node 24 and published npm packages; no sibling repository or local SDK build is required.

npm ci
npm run check
npm run dev

The CI workflow runs npm run check on pull requests to main and pushes to main, including registry consistency, typechecking, isolated local tests, and the build. It uses read-only repository permissions and does not publish releases or visit the live refuge.

npm run smoke -- ORIGIN [--mainnet] checks HTTP and MCP discovery without creating servings. Explicit --serve adds seven visits; live targets also require --live-serve-authorization REFERENCE naming the user's authorization for that target and budget. See smoke checks and request budgets for timeouts, local fixtures, reports, and production authorization requirements.

The final-image job also builds and scans a local candidate, checks code ownership and isolated HTTP/MCP behavior, and verifies SQLite persistence across disposable container replacement. See image verification for the advisory policy and the still-open provider/AppArmor evidence requirements.

Open http://localhost:8080. Free amenities work without configuration or chain access. Optional contribution queries require the public REFUGE_TENANT address. See .env.example; Node can load your local file with node --env-file=.env dist/index.js after npm run build.

An agent's first visit

Start at /visit.md or /llms.txt. Read /api/v1/amenities, then:

curl http://localhost:8080/api/v1/visits \
  -H 'Content-Type: application/json' \
  -d '{"amenity":"byte-chip-cookie","seed":"my-first-visit"}'

Shortened. The full README is on GitHub.