Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

The Tab (scvd-tab)

by seancrecordversion 0.11.4i★ –iRuns on your computer
Registry namestore.scvd/tab

Install

Overview

Description from the maker (original English)

Every tool a builder signs up for, on one tab: trials, burn, price drift. Local JSONL, zero deps.

PopNx MCP’s three pillars

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

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
  • Category: Other

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?

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": {
    "tab": {
      "command": "npx",
      "args": [
        "-y",
        "scvd-tab"
      ]
    }
  }
}

Run this in your terminal

claude mcp add tab -- npx -y scvd-tab

Open in Cursor

Or copy the settings yourself

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

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

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": {
    "tab": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "scvd-tab"
      ]
    }
  }
}

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 against the domain scvd.store (the registry checks domain ownership)

  • … 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 Otheri

  • More stars than 0% of the other 32531 servers in this category
  • Published to the registry more recently than 64% of the other 32531 servers in this category
  • Basic checks equal to or better than 100% of the other 32531 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 The Tab (scvd-tab) 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.11.4) reached the registry 21 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: Spec Driven Development, Remote Desktop Commander, Reelsaw

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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Reelsaw

by osbytes

Drive a self-hosted Reelsaw: turn long videos into vertical clips, edit, re-render and export them.

Runs on your computerUpdated today
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.

scvd.store

Personal-agent connections

Hermes discovers the skills at https://scvd.store/.well-known/skills/index.json. Connection and no-spend rehearsal guidance covers Hermes, OpenClaw, Skills CLI and chat sessions. A rehearsal ends with the quote, missing capabilities and required approvals; it does not spend. Tested versus untested paths.

mcp-name: store.scvd/general-store

Discovery records: Neuronto, WellKnown, Licium — MCP endpoint history, and Zero.xyz — Signature Agent Card. The Desvela checker runs a check of this domain's discovery surfaces. These are third-party readings of publication and indexing, not evidence of visits or purchases. The WellKnown badge above is served live by WellKnown.

Every badge above is somebody else's reading of this store. This one is ours, about ourselves, and it is set apart from that row on purpose — it is the same artifact we ask operators to paste beside their own doors, pointed back at us, and it says SELF-OBSERVED on its face because the weekly census structurally cannot probe its own host:

It goes dark rather than stale-green: it renders only while every self-module agrees, and any disagreement renders the passport indeterminate and refuses the chip. Weigh it accordingly — the reason it is worth showing at all is that every claim inside it is re-checkable at the public surfaces it names.

scvd.store is an evidence observatory for agentic commerce: independent verification of x402 endpoints, payments and receipts. Before an agent pays an x402 endpoint, we check that it can be paid. After it pays, we check the signed receipt. Over time we watch endpoints and publish a dated, signed corpus. Sellers use it to prove a door works; buyers use it before spending. Signed observations are dated with explicit gaps; free inspection is unsigned. Not escrow, not a rating, not a guarantee.

Three paths, in that order. Before you pay: preflight any x402 door, free, at scvd.store/api/preflight/v1. After you pay: check any issuer's signed offer or receipt, free, at scvd.store/conformance. Over time: read the dated, Bitcoin-anchored corpus, free, at scvd.store/corpus, cite it by DOI (10.5281/zenodo.22284887), or pull it from Hugging Face. Every verdict is ed25519-signed, dated, and verifiable offline without asking us, including the gaps we count against ourselves. Operated by Record Creative Co. LLC.

What would you like your agent to do?

For working examples, use the SDK and evidence paths: check an endpoint, verify an artifact, reproduce the corpus findings, or attach one dated observation to a listing.

Not an escrow, a guarantor, or a dispute court. Those absorb the risk between payment and delivery and need a balance sheet; we observe that gap and sign what we saw. If you are building escrow or adjudication, this is the layer underneath you rather than a competitor. That direction was decided and dated on 2026-08-07, in the open — the reversal sits beside what it replaced at scvd.store/becoming.

It is also a small, sincere general store for autonomous AI agents, kept by a human out of Oak City, where you're never late. Agents pay in USDC over x402 on a network offered in the current payment quote. Humans read the receipts.

Live at scvd.store. Agents should start at /agents.md (the scannable contract index), /llms.txt (full prose), or /menu.json.

Find SCVD by protocol: x402, MPP, MCP, WebMCP, ERC-8004, A2A, OASF, skills and UCP.

Buy with your personal agent

Copy the shopping prompt, or install the personal shopper skill:

npx skills add seancrecord/scvd-general-store-repo --skill scvd-personal-shopper

Your agent reads the current menu, shows the price, helps with a compatible wallet if needed, and returns the artifact and verified receipt. Reading and quotes are free. Funding and each purchase need your approval. Availability of payment tools depends on your agent's environment; installation alone does not make it a wallet.

The doors, by task

What people arrive here to do, and where each door is:

  • Introduce an agent consistently — local public-profile setup and a configured Node fetch download in /bot-auth. Build and integration limits: calling-card/README.md. Site acceptance and payment completion remain separate outcomes.
  • Test an x402 payment — a live practice counter with real USDC settlement, no sandbox; test payment prices and required inputs are listed at scvd.store/try.
  • Check x402 conformance, free — POST any issuer's signed offer or receipt (ours or a competitor's) and get a structured verdict: parse, schema, ed25519 signature, liveness. No account, no wallet: scvd.store/conformance. The same verification runs offline via x402-verify (MIT, zero deps), and x402-sign mints offers and receipts that pass it.
  • Inspect an endpoint before deciding what to do — the free preflight separates observed x402/MPP protocols, unverified advertised terms, structural findings, observation time and coverage gaps. Its top-level verdict remains x402-specific. The CLI and JavaScript library provide scvd inspect and inspectOne; check installed help/exports, since source preparation and registry publication are separate. Inspection success establishes that a response was observed, not that a payment will settle or deliver.
  • Fail your deploy on an x402 readiness failure — the free preflight as a GitHub Action, one probe per door after the deploy step, not_ready fails the job and unreachable does not: action/preflight. The terminal form is scvd preflight from scvd-cli. As a library, the same check and the same exit law in three languages, each zero-dependency and each tested against the *same* recorded reports rather than a copy of them: scvd-preflight on npm, scvd-preflight on PyPI, and x402-preflight-go for Go.
  • Read the corpus — weekly signed observations of the x402 ecosystem, hash-chained and Bitcoin-anchored, free to read: scvd.store/corpus. For bounded metadata discovery, use the CLI or the published corpus client; both preserve gaps and leave signature and timestamp verification explicit. Protocol-specific MPP observations remain alongside the historical x402 verdict; older rows without them remain unmeasured.
  • Score, rank or list x402 doors? Take the evidence and leave the opinion: scvd.store/scorers is the room for systems that consume this corpus. Pull it, verify it offline, cite a row by URL, and re-observe any reading you doubt — no key, no account, no permission asked. Every row hands you the citation to paste, and the store publishes what it did not see beside what it did. If you publish a score derived from it, the interpretation is yours: this store does not endorse derived conclusions.
  • Buy a settlement attestation — a signed observation of on-chain payment status on Base, Polygon, or Solana, with what the signature does and does not prove stated per class at scvd.store/attestation.
  • Watch an endpoint — endpoint monitoring as standing_watch: seven days of signed hourly probes on a URL you name.
  • Anchor agent memory — context_anchor: a signed, retrievable session restore point that survives a context reset.
  • See your buy path from the buyer's side — launch_check: a real mainnet purchase attempt of your own x402 endpoint, from the store's declared field wallet, recorded stage by stage and signed. Directories rank doors by whether they answer; this one pays them.
  • Audit an agent's books against the chain — the_statement: every USDC transfer in and out of a wallet on the supported network you select over a stated window, signed by a party that is neither the agent nor its operator.
  • Read your month off the chain — operator_statement: your receiving address, every USDC transfer in and out for 30

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

Ask PopNx