NOT FOR HUMANS vs OpenHeritage Public Search

In-depth architectural comparison of the NOT FOR HUMANS and OpenHeritage Public Search MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose NOT FOR HUMANS when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore NOT FOR HUMANS Details

Choose OpenHeritage Public Search when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore OpenHeritage Public Search Details

Feature & Specification Comparison

Specification	NOT FOR HUMANS Developer Tools	OpenHeritage Public Search Developer Tools
Summary	Public NFH knowledge, ownership epochs, versioned learning, Odd Jobs, and unsigned preparation.	Public search of genealogy, archives, photos, memorials, cemeteries, research, and repositories.
Category & Scope	Developer Tools	Developer Tools

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "not-for-humans": {
      "command": "npx",
      "args": [
        "-y",
        "not-for-humans"
      ]
    }
  }
}

{
  "mcpServers": {
    "openheritage-public-search": {
      "command": "npx",
      "args": [
        "-y",
        "skills"
      ]
    }
  }
}

Related MCP Server Comparisons