Thingery

Name: Thingery
Author: thingery

by thingeryversion 0.1.3i★ –iRuns on your computer

Registry nameio.github.thingery/thingery

Install

Overview

Description from the maker (original English)

Open item database and MCP server for AI agents to list, find, and trade second-hand goods.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio, Streamable HTTP
Category: Databases & datasets

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "thingery": {
      "command": "npx",
      "args": [
        "-y",
        "thingery"
      ]
    }
  }
}

Run this in your terminal

claude mcp add thingery -- npx -y thingery

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "thingery": {
      "command": "npx",
      "args": [
        "-y",
        "thingery"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "thingery": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "thingery"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account thingery, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Databases & datasetsi

More stars than 0% of the other 953 servers in this category
Published to the registry more recently than 81% of the other 953 servers in this category
Basic checks equal to or better than 100% of the other 953 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Thingery safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.3) reached the registry 9 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Supabase

by supabase

Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.

Computer or cloud★ 2,993Apache-2.0Updated yesterday

Install

MongoDB MCP Server

by mongodb-js

MongoDB Model Context Protocol Server

Runs on your computer★ 1,157Apache-2.0Updated 2 days ago

Install

Elasticsearch MCP Server

by cr7258

MCP server for interacting with Elasticsearch

Runs on your computer★ 315Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Thingery

Thingery is the open item database and MCP server for AI agents to list, find, and trade second-hand goods.

Say *"sell this"* to your AI assistant — it identifies the item, writes the listing, prices it, and publishes it. Say *"find me a used camera under €300"* — it searches every listing and proposes the best one. Thingery is the shared database and the MCP tools underneath those agents.

Free for everyone. No take rate, no platform lock-in.
Open source (Apache-2.0). Self-host the whole thing, or use the flagship instance.
Agent-native: every capability is an MCP tool; any LLM can drive it.
Self-hostable: Postgres + pgvector + Node 20.

Chinese-market name: 物坊 (Wùfāng).

MCP tools

Tool	Auth	Purpose
`describe_category`	public	List categories and their declared attribute fields — the self-describing schema for agents. Declared fields get validated on create; undeclared keys are allowed, searchable, and their real use is surfaced via `undeclared_in_use`
`search_items`	public	Hybrid semantic + keyword search with price/category/condition/attribute filters (any attribute key, declared or not)
`get_item`	public	Fetch one listing by id. Pending (photoless) listings are returned too — they carry `needs_photo: true`
`create_listing`	seller	Publish an item — core fields plus a flexible `attributes` object (declared keys validated, extras pass through and stay searchable). Listings are hidden from search until they have at least one photo: a zero-image create succeeds but stays pending (`visible: false` + `next_steps` in the result) until a photo lands
`add_item_image`	seller	Attach a photo to a listing (base64 in, stored server-side — no URLs needed; max 5 MB decoded). The first photo publishes a pending listing — the result's `visible` tells you. Images are re-encoded at ingest: metadata (EXIF/GPS/XMP) stripped, downscaled to ≤ 2000 px, animated GIFs stored as stills; large PNGs may be rejected — prefer JPEG
`my_listings`	seller	Your listings by status
`update_listing`	seller	Mark reserved/sold, adjust price, edit text or attributes

Order flow

Tool	Auth	Purpose
`get_payout_setup`	seller	Stripe Express onboarding URL + status — optional, enables platform payment
`create_order`	account	Order an item — returns a Stripe Checkout URL (stripe mode) or tracks an off-platform order
`get_order`	account	One of your orders (buyer or seller side): status, tracking, deadlines
`cancel_order`	account	Cancel while cancellable; paid orders refund instead
`record_tracking`	seller	Record carrier + tracking code; auto carrier tracker when EasyPost is configured
`confirm_payment`	seller	Confirm an off-platform payment (pending → sold)
`confirm_receipt`	buyer	Confirm delivery — dispute window opens
`open_dispute`	buyer	Dispute a delivered order; seller payout is held
`release_funds`	buyer	Waive the dispute window, release the seller's payout now

Orders close a deal on-platform. Stripe mode (buyer protection: platform charges the buyer, holds funds, pays the seller after delivery + dispute window) runs when the deployment has Stripe configured *and* the seller finished payout onboarding; otherwise orders run in off-platform mode — Thingery tracks state and deadlines, parties settle payment themselves. States: pending → sold → label_issued → in_transit → delivered → payout_pending → paid_out with disputed/cancelled/refunded off-ramps; deadlines are enforced by a server-side sweep (unpaid cancels 24h, dispute window 48h, never-shipped disputes auto-refund 72h — defaults, env-tunable). Design record: ADR 0003.

Sellers authenticate with OAuth (one-click sign-in from any MCP host — see below) or a thg_... API key (Authorization: Bearer); search is anonymous.

Buyer alerts (saved searches)

A buyer who finds nothing good can save the search as an intent; when a matching listing publishes later, their agent reads it as a match on the next session — no email, the buyer's agent pulls my_matches (design record: ADR 0006). Fan-out is bounded: each match is inserted at most once per (intent, item), at most 10 new matches per buyer per day, at most 100 per published listing, and a seller never matches their own listing.

Tool	Auth	Purpose
`save_intent`	account	Save what the buyer is looking for — a query and/or the same filters as `search_items` (at least one of the two; max 25 saved intents, 50 saves/day)
`my_intents`	account	Your saved searches, newest first, each with its unread-match count and muted state
`update_intent`	account	Mute or unmute a saved search — muting stops future matches; existing matches stay readable
`delete_intent`	account	Delete a saved search; its matches go with it
`my_matches`	account	New listings matching a saved search — `unread_only`, `mark_read`, limit 1–50 (default 10). Items carry `content_provenance: "user_generated"`

Photo-required publishing

New listings need at least one photo to be visible to buyers — browse, search_items, and category counts all exclude photoless listings (a single derived predicate; design record: ADR 0005). What that means in practice:

create_listing with zero images succeeds — the listing is created but pending: hidden from feeds, its item page shows placeholder art and is noindex. The result carries photo_required, visible: false, and next_steps pointing at add_item_image (or the item page, where the owner can snap a photo in two taps).
The first photo publishes it — no second call needed. add_item_image returns visible: true; pending items carry needs_photo: true everywhere items are returned (get_item, my_listings, …).
Deleting the last photo returns the listing to pending (hidden again); pre-rollout listings are grandfathered and stay live without photos — on thingery.dev that means created before 2026-10-27; a self-hosted instance grandfathers whatever exists when it first deploys this version.
Owners manage photos on the item page (upload, delete, reorder) via the session-cookie routes documented in docs/item-images.md.

Two ways to use it

Zero-config (everyone): open `/chat.html` on any deployment and talk to the Thingery assistant — describe an item to sell or to find. Searching needs no account; publishing needs a free one (/login.html, email + password; your MCP API key is shown after signup). The chat uses an LLM configured on the server (LLM_* env vars) — you bring the key, any OpenAI-compatible endpoint works; without it, chat is disabled while MCP and signup still work.
Bring your own agent (power users): point any MCP client at /mcp and sign in with OAuth — Claude Desktop, ChatGPT connectors, VS Code and Inspector discover the sign-in flow automatically (RFC 9728 resource metadata + RFC 7591 dynamic client registration); you approve once on a consent screen and the host gets a rotating thgo_ token, with revoke-anytime at /apps. Prefer a key? The manual thg_... API key still works, and self-hosting is below (npx thingery over stdio).

Quickstart

Pick your mode first — hosted and self-hosted expose the same MCP tools but not the same data: listings you create on the hosted service are visible to everyone; listings on your self-hosted instance live only in your database.

Mode	Endpoint	Data	Best for
Hosted	`https://thingery.dev/mcp`	the shared public marketplace	first success in under a minute — nothing to install
Self-hosted	your own `/mcp`, or stdio	your Postgres, your data	private deployments, full control, hacking on it

Mode A — hosted: search in one minute

No install. Add https://thingery.dev/mcp as a remote HTTP server in your MCP client (Claude Desktop, ChatGPT connectors, VS Code, Inspector — see Connect an MCP client below) and sign in with OAuth, or grab an API key at /login.html (free account; the thg_... key is shown after signup). Searching needs no account at all — verify the wire format with curl:

curl -s https://thingery.dev/mcp \

-H 'content-type: application/json' \ -H 'accept: application/json, text/event-stream' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call", "params":{"name":"search_items","arguments":{"q":"Air Max"}}}'

Responses come back as Server-Sent Events; the JSON-RPC result is on the data: line.

Mode B — self-hosted: the npm package

The thingery npm package runs the whole server against your own Postgres. No git clone needed:

mkdir my-thingery && cd my-thingery

npm install thingery

1. a Postgres with the pgvector extension (Docker: `docker run -d -p 5432:5432 \

-e POSTGRES_PASSWORD=thingery pgvector/pgvector:pg16`; Homebrew: see below)

2. apply the shipped schema (idempotent, safe to re-run):

psql "postgres://postgres:thingery@localhost:5432/postgres" \ -f node_modules/thingery/db/schema.sql

3. run it (DATABASE_URL is the only required env var):

DATABASE_URL="postgres://postgres:thingery@localhost:5432/postgres" \ PORT=3000 node node_modules/thingery/dist/index.js

The server boots at http://localhost:3000 — /mcp, /browse, /healthz, and the HTTP API. Create your account by opening /login.html — your thg_... MCP key is shown right after signup. (On the pre-fix 0.1.2 release the page 404'd — a packaging gap fixed after it; there you can still create the account through the API — the key is returned exactly once, in the signup response:)

curl -s -X POST http://localhost:3000/api/signup \

-H 'content-type: application/json' \ -d '{"email":"you@example.com","password":"at-least-8-chars"}'

→ {"seller":{"name":"you","email":"…","api_key":"thg_…"}}

Then point any MCP client at http://localhost:3000/mcp with Authorization: Bearer thg_... — or spawn it over stdio with the npx config below.

Note: the npm package publishes at release cadence and can lag main on thingery.dev

by days — /healthz reports the running version. If you need today's features,

self-host from source instead:

Self-hosted from source (development)

git clone https://github.com/thingery/thingery

cd thingery npm install docker compose up -d db # Postgres 16 + pgvector cp .env.example .env npm run db:migrate npm run db:seed # demo seller + 3 listings; prints an API key npm run dev # http://localhost:3000

No Docker? Local Postgres

npm run db:migrate needs a Postgres with the vector extension — the schema creates it unconditionally, even in keyword-only search mode. On macOS, Homebrew's pgvector bottle supports PostgreSQL 17 and 18 (not 16, the version the Docker setup uses — any of them works for Thingery):

brew install postgresql@18 pgvector

brew services start postgresql@18 psql postgres -c "CREATE ROLE thingery LOGIN PASSWORD 'thingery';" \ -c "CREATE DATABASE thingery OWNER thingery;" psql -d thingery

Only the beginning is shown; read the rest in the repo

Thingery

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Databases & datasetsi

Common questions

Alternatives

Supabase

MongoDB MCP Server

Elasticsearch MCP Server

README from the maker

Thingery

MCP tools

Order flow

Buyer alerts (saved searches)

Photo-required publishing

Two ways to use it

Quickstart

Mode A — hosted: search in one minute

Mode B — self-hosted: the npm package

1. a Postgres with the pgvector extension (Docker: `docker run -d -p 5432:5432 \

-e POSTGRES_PASSWORD=thingery pgvector/pgvector:pg16`; Homebrew: see below)

2. apply the shipped schema (idempotent, safe to re-run):

3. run it (DATABASE_URL is the only required env var):

→ {"seller":{"name":"you","email":"…","api_key":"thg_…"}}

Self-hosted from source (development)

No Docker? Local Postgres