pickfit

BrowseMCP servers

ontos

In-VPC knowledge-graph runtime that extracts facts and serves them to agents with audit.

Tested on Linux

Use it

Linux x86_64

  1. install enclave-ontos via uv tool install

    uv tool install enclave-ontos

Add it to your agent

claude mcp add --transport http ontos http://127.0.0.1:8765/mcp
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "ontos": {
      "type": "http",
      "url": "http://127.0.0.1:8765/mcp"
    }
  }
}

This server speaks HTTP: start it first and keep it running (ontos serve --host 127.0.0.1 --port 8765), then add the URL.

What it does

These come from the README; pickfit didn’t check them one by one.

  • Extract typed entities and relationships from data
    Not tested
  • Store facts as immutable records tagged with their source
    Not tested
  • Serve the knowledge graph to agents over MCP
    Not tested
  • Write an audit record for every query
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. A tool call works
  4. Works offline

Good for

  • ingest text and PDF corpora
  • query graph with ontos query or ask tool
  • export graph for visualization
  • verify audit chain

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client called one of its tools

  • Replayed from scratch
  • Works offline
  • Checked on 31 Oct 2026
  • Version 0.7.0

An MCP client handshake over HTTP listed 6 tools, and a call to search returned a result.

Differences the test machine hit

  • README: ontos serve binds streamable-HTTP
    In the test: MCP probe must use --url http://127.0.0.1:8765/mcp after starting server in background; no stdio mode exists

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.