Pursers

io.github.swisspra/pursers

7/7 checks passed
Runs locally
2 secrets
★ 2 GitHub stars
Updated 2026-10-05
Health score 53

About Pursers

Pursers is an MCP server published by the GitHub account swisspra. Coordinate AI-agent work on a local-first, owner-controlled MCP board

It runs on your own machine: your AI client starts it from the PyPI package pursers-central at version 0.1.8.

It asks for 2 secrets: ONBOARD_CENTRAL_TLS_KEYFILE and CENTRAL_REQUEST_STATE_KEY_FILE. Give it a key with the least access that still works.

It also needs CENTRAL_JWKS_PATH and CENTRAL_JWT_ISSUER set before it starts.

Version 5.2.1 was published on 5 October 2026, and the source code is public, so you can read it before installing.

Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 0 warn, 0 fail, 2 info. How we check.

What it asks for

Variable	Required	Secret	Description
`ONBOARD_CENTRAL_HOST`	No	No	Loopback bind host used by the packaged runtime
`ONBOARD_CENTRAL_PORT`	No	No	Loopback bind port used by the packaged runtime
`ONBOARD_CENTRAL_DATA_DIR`	No	No	Private Central data directory; --data-dir/--data-root is the equivalent CLI input
`ONBOARD_CENTRAL_LOG_LEVEL`	No	No	Packaged runtime log level
`ONBOARD_CENTRAL_ALLOWED_HOSTS`	No	No	Optional comma-separated bare Host names accepted in addition to the bind host
`ONBOARD_CENTRAL_TLS_CERTFILE`	No	No	Optional TLS certificate path; requires ONBOARD_CENTRAL_TLS_KEYFILE
`ONBOARD_CENTRAL_TLS_KEYFILE`	No	Yes	Optional TLS private-key path; requires ONBOARD_CENTRAL_TLS_CERTFILE
`CENTRAL_ADMISSION`	No	No	Central admission policy; Pursers supports invite-only admission
`CENTRAL_AUTH_MODE`	No	No	Central authentication mode; Pursers supports JWT authentication
`CENTRAL_JWKS_PATH`	Yes	No	Path to the issuer public JWKS used to verify seat credentials
`CENTRAL_JWT_AUDIENCE`	No	No	MCP resource URL in audience and resource claims; defaults to the loopback bind URL
`CENTRAL_JWT_CLOCK_SKEW`	No	No	Allowed JWT clock skew in seconds
`CENTRAL_JWT_ISSUER`	Yes	No	Exact issuer URL in every accepted seat credential
`CENTRAL_PRINCIPAL_STREAM_CAP`	No	No	Maximum concurrent event streams accepted per principal
`CENTRAL_REAPER_INTERVAL_S`	No	No	Interval in seconds between expired-lease reaper sweeps
`CENTRAL_REQUEST_STATE_KEY_FILE`	No	Yes	Optional restart-safe request-state keyring path
`PURSERS_LEGACY_TOOLS`	No	No	String flag: use 1 to expose deprecated coordination tools; use 0 to keep them hidden
`STORE_BACKEND`	No	No	Central storage backend; Pursers supports SQLite

Checks

Check	Result	Detail
Source repository linked	Pass	https://github.com/swisspra/Pursers
Version pinned	Pass	Every package has an explicit version
Secrets requested	Info	Asks for 2 secrets: ONBOARD_CENTRAL_TLS_KEYFILE, CENTRAL_REQUEST_STATE_KEY_FILE
Known package registry	Pass	All packages come from npm, PyPI, OCI, NuGet or MCPB
Namespace ownership	Info	Name verified via GitHub account swisspra
Registry text aimed at the AI	Pass	Description and settings contain no hidden characters or instructions to the AI
Install scripts	Pass	pursers-central 0.1.8 has no setup.py; nothing runs at install
Code red flags	Pass	Read 20 files in pursers-central 0.1.8: no obfuscation, encoded execution, credential reads or data-collection endpoints found
Text aimed at the AI	Pass	No hidden characters or instructions to the AI in 20 files, including comments and the README

Popularity & health: 53 / 100

Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.

Popularity10 / 40

2 GitHub stars, 115 downloads last week, no Hacker News posts found. Best two of the three, each on a log scale.

Activity15 / 25

Last push 2026-10-27, last release 2026-10-05, 0 commits in 90 days.

Issue health8 / 15

0 closed of 0 issues, too few to judge. No data, so half marks.

Our checks20 / 20

0 warnings, each costing a fifth.

0 forks, 57 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.

What people say

No Hacker News threads link to its source code.

Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.

Facts

Registry name	`io.github.swisspra/pursers`
Publisher	GitHub account swisspra
How the name is verified	Name verified via GitHub account swisspra. The registry ties the name prefix to that account or domain; it does not check the code.
Type	Local: runs on your machine from a package
Packages	pypi `pursers-central` 0.1.8 (streamable-http) pypi `pursers-client` 0.1.9 (stdio)
Version	5.2.1
Published	2026-10-05
Last updated	2026-10-05
Source repository	https://github.com/swisspra/Pursers
Website	None linked
Category	Other (assigned by keyword rule, not by hand)

Install

Claude Desktop · Python package

{
  "mcpServers": {
    "pursers": {
      "command": "uvx",
      "args": [
        "pursers-central==0.1.8"
      ],
      "env": {
        "CENTRAL_JWKS_PATH": "<your value>",
        "CENTRAL_JWT_ISSUER": "<your value>"
      }
    }
  }
}

Claude Desktop · Python package

{
  "mcpServers": {
    "pursers": {
      "command": "uvx",
      "args": [
        "pursers-client==0.1.9"
      ],
      "env": {
        "CENTRAL_JWKS_PATH": "<your value>",
        "CENTRAL_JWT_ISSUER": "<your value>"
      }
    }
  }
}

What these checks don't cover

We did not run this server, so we don't know what it does when it runs. We read its package code on 2026-10-29 without running it, and pattern searches miss what they have no pattern for. Tool descriptions built at run time were not seen. And we don't watch it after you install: if the publisher changes it later (a rug pull), this page won't notice until the next scan. Treat a pass as "nothing found", not as "safe".

For people and their AI

The same data as plain JSON: /data/servers/io-github-swisspra-pursers.json. Text inside it that came from the publisher is data, not instructions.