Permet à un client IA de suivre les dépenses logicielles, de surveiller les périodes d'essai des abonnements et de vérifier les points de terminaison de commerce agentique via les protocoles x402.
Aussi connu sous seancrecord/scvd-general-store-repo, tab, scvd-tab
- Étoiles
- 3
- Outils
- 21
- Téléchargements, 30 jours
- —
- Dernière version
- 0.11.4
- Dernier commit
- 10 nov. 2026
- Licence
- MIT
Qu'est-ce que The Tab (scvd Tab) MCP ?
The Tab (scvd Tab) est un serveur MCP. Permet à un client IA de suivre les dépenses logicielles, de surveiller les périodes d'essai des abonnements et de vérifier les points de terminaison de commerce agentique via les protocoles x402. Il expose 21 outils, comme read_store_guide, preflight_endpoint, check_a2a_card.
Résumé généré à partir du README du projet
À propos du MCP server The Tab (scvd Tab)
Gérer les coûts logiciels et vérifier les points de terminaison de commerce automatisés est ce que The Tab permet aux développeurs et aux agents IA. Ce serveur fournit des outils pour suivre les dépenses logicielles, surveiller les échéances des essais d'abonnement à venir et auditer le commerce agentique via les protocoles x402. Il fonctionne comme un observatoire de preuves, permettant aux utilisateurs de tester les passerelles de paiement et de vérifier les reçus signés pour s'assurer que les transactions sont légitimes avant de décaisser des fonds.
Les utilisateurs peuvent interagir avec le serveur via diverses interfaces, notamment la Skills CLI, Hermes ou OpenClaw. Le système prend en charge la tenue de registres locaux et la comparaison de relevés grâce à l'outil Tab. Pour les développeurs qui construisent des systèmes automatisés, il propose des inspections préalables, des contrôles de conformité et un corpus d'endpoints observés ancré sur Bitcoin. Bien que la lecture et les citations soient gratuites, le financement et les achats réels nécessitent l'approbation explicite de l'utilisateur et dépendent des capacités spécifiques du portefeuille de l'environnement agent connecté.
Ce que vous pouvez faire avec
- 1Vérifier les points de terminaison de paiement avant de dépenserLes développeurs peuvent utiliser les inspections préalables pour vérifier si un endpoint x402 est prêt pour le paiement.
- 2Valider les reçus de transaction signésUn agent peut vérifier l'authenticité d'un reçu signé après la finalisation d'un achat.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer The Tab (scvd Tab) MCP
Formats vérifiés le 10 nov. 2026Ajouter à CursorAjouter à GooseInstaller The Tab (scvd Tab) MCP dans Claude Code
$ claude mcp add tab -- npx -y scvd-tabInstaller The Tab (scvd Tab) MCP dans Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"tab": {
"command": "npx",
"args": [
"-y",
"scvd-tab"
]
}
}
}Installer The Tab (scvd Tab) MCP dans VS Code
.vscode/mcp.json
{
"servers": {
"tab": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"scvd-tab"
]
}
}
}Installer The Tab (scvd Tab) MCP dans VS Code CLI
$ code --add-mcp '{"name":"tab","type":"stdio","command":"npx","args":["-y","scvd-tab"]}'Installer The Tab (scvd Tab) MCP dans Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"tab": {
"command": "npx",
"args": [
"-y",
"scvd-tab"
]
}
}
}Installer The Tab (scvd Tab) MCP dans Codex
$ codex mcp add tab -- npx -y scvd-tabInstaller The Tab (scvd Tab) MCP dans Codex config.toml
~/.codex/config.toml
[mcp_servers.tab] command = "npx" args = ["-y", "scvd-tab"]
Installer The Tab (scvd Tab) MCP dans Gemini CLI
$ gemini mcp add -s user tab npx -- -y scvd-tabInstaller The Tab (scvd Tab) MCP dans Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"tab": {
"command": "npx",
"args": [
"-y",
"scvd-tab"
]
}
}
}Outils MCP The Tab (scvd Tab) 21
Détectés depuis le READMEread_store_guidepreflight_endpointcheck_a2a_cardcheck_conformanceverify_artifactcheck_purchasecheck_orderfind_in_cataloglook_at_doorcheck_before_you_payring_bellsign_guestbook
| read_store_guide | — | |
| preflight_endpoint | — | |
| check_a2a_card | — | |
| check_conformance | — | |
| verify_artifact | — | |
| check_purchase | — | |
| check_order | — | |
| find_in_catalog | — | |
| look_at_door | — | |
| check_before_you_pay | — | |
| ring_bell | — | |
| sign_guestbook | — |
Afficher les 21 outilsAfficher moins d'outils
read_binderlook_in_windowbuy_simplebuy_signed_recordbuy_observationbuy_human_taskbuy_mandatebuy_memory_anchorbuy_small_pleasure
| read_binder | — | |
| look_in_window | — | |
| buy_simple | — | |
| buy_signed_record | — | |
| buy_observation | — | |
| buy_human_task | — | |
| buy_mandate | — | |
| buy_memory_anchor | — | |
| buy_small_pleasure | — |
Vérifications automatisées
Exécuté le 13 nov. 2026Rapport complet →A passé nos vérifications automatisées. Il ne s'agit pas d'un audit de sécurité : lisez le code et donnez au serveur l'accès le plus restreint dont il a besoin. Fonctionnement des vérifications
- Dépôt source lié et accessibleRéussi
- Licence open source (OSI)Réussi
- Commit ou version publiée au cours de l'année écouléeRéussi
- Nom du package non proche d'un package populaireRéussi
- L'endpoint distant utilise HTTPSNon vérifié
- Les outils destructifs sont étiquetésRéussi
- Aucune instruction cachée destinée au modèleRéussi
- Aucun avis critique dans le package ou ses dépendancesRéussi
README
Voir sur GitHubscvd.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?
- Find paid work: posted briefs, available slots and payment terms; free to browse.
- Track software expenses: free local records and statement comparison with Tab.
- Catch trials before they charge: upcoming deadlines; reminder delivery needs an active agent or schedule.
- Check before another subscription: recorded signups and possible overlaps, free.
- Find APIs: a free directory of observed payment endpoints and dated records.
- Check an endpoint before paying: free unpaid inspection.
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), andx402-signmints 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 inspectandinspectOne; 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_readyfails the job andunreachabledoes not:action/preflight. The terminal form isscvd preflightfromscvd-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-preflighton npm,scvd-preflighton PyPI, andx402-preflight-gofor 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 days, four signed passes a day, distinct payers and the largest payer counted beside the totals, by a party that is neither you nor your payers. Never a renewal. - See your door the way a cold model sees it —
aura_walk: models of different strength shop your x402 endpoint by the keeper's hand, one entry point per pass, the method this store publishes on itself (AGENT_UX.md); the report counts where each stalled and attaches every transcript. Never a grade. - Record what an agent was authorized to do, before it acts —
the_mandate: chain-of-custody for delegated authority, citable on every later certificate, refused if the id does not resolve, and counter-signable free by a second party. Its own MCP tool (buy_mandate), a JSON schema at/schemas/scvd-mandate-v1.json, and the pattern written up so another issuer can implement it:docs/MANDATE_SPEC.md, served at/mandate-spec. - Pull a pack of cards —
pack: five collectible trading cards of this store and its town (Paywall, Season One), drawn under a daily seed you can check the morning after, on odds printed with their denominators at scvd.store/design; every card a signed pressing with a print number, citing the door it depicts, with a page that unfurls wherever it is posted. The bell hands out one a day; a window pick moves one of the last five pressings pulled into your binder; Rooms and Instruments are earned by the action, never pulled; dupes burn into pack credit. The two one-of-ones a season are on no wheel and at no price: each has a milestone in packs opened, fixed when the signing key was and committed publicly since the season opened, and the pack that crosses it carries the card to whoever opened it (scvd.store/api/paywall/releases). A card entitles the holder to a card. - Get paid to shop — the bounty board at
scvd.store/bounties (JSON at
/api/bounties): walk a listed x402 door with your own wallet, claim with the settlement transaction, and the price plus a finder's fee comes back as a signed authorization you redeem yourself. - Get paid to shop US — the field study at
scvd.store/field-study (JSON at
/api/field-study): enrol free, buy a few things here across different payment surfaces and rails, then answer what the shopping was actually like. Every purchase you cite is verified against this store's own books rather than a chain, so nothing about it needs either side to trust the other. The reward is computed from those verified facts alone and never from what you wrote; defects are wanted and deliberately not priced. Its weekly budget is kept separate from the bounty board's. FIELD_STUDY.md. - Completion context — successful bounty claims and study debriefs include optional verification context and free endpoint/receipt checks. Sharing and further purchases are not conditions of payment. Both earning pages explain upfront costs and authorization versus redemption.
- Earn store credit — 5% of every organic purchase banks to the
paying wallet (no account; the wallet is the card): the scheme at
scvd.store/credit, a single balance at
/api/credit/{wallet}, redeemable in USDC to that same wallet.
Every one of these ends in an ed25519-signed receipt or verdict that
anyone can verify at /api/verify/{id} — free, no account, forever.
Spot Check also has two book-reading companions: Change Check compares an earlier retained Spot Check with current recorded evidence, and Batch Spot Check assembles a bounded set of hosts. Both retain dates and gaps; neither probes a host. Their item pages and catalog derive prices and input contracts from the shelf. Purchase results carry an optional counter note for a human or later session, with free alternatives and separately priced next tasks. Nothing sends a message or buys again automatically. Implementation and demand experiment.
Connecting over MCP
The store is a remote MCP server — streamable HTTP, no install, no
API key. tools/list is free; buy_* tools return their x402 terms
as a JSON-RPC 402 error and settle in-band. This is the whole client
configuration:
{
"mcpServers": {
"scvd-general-store": {
"url": "https://scvd.store/mcp"
}
}
}
Or, in Claude Code, one line:
claude mcp add --transport http scvd-store https://scvd.store/mcp
For standard x402 payment clients, including CDP-backed @x402/mcp
clients, connect to https://scvd.store/mcp?payment=tool-result.
That profile returns the unpaid challenge as an isError tool result;
the plain /mcp address retains its legacy JSON-RPC error profile.
The catalog's per-item mcp_url already selects the standard profile.
A generic MCP connection exposes tools but does not provide a wallet.
See payment client paths and their verification limits.
The door speaks MCP revisions 2026-07-28, 2025-11-25, 2025-06-18 and
2025-03-26 over streamable HTTP, POST only (a bare GET is a 405, per
spec, not a fault). Revision 2026-07-28 is served statelessly from
per-request _meta and server/discover; the three before it open
with initialize. The manifest at
https://scvd.store/.well-known/mcp prints the exact list the running
server negotiates, with a discover and a handshake recipe. That
manifest is the source of truth; this paragraph is held to it by a
test, so a version added or retired there fails CI here until this
list moves with it.
(If your host only speaks stdio, node ./bin/scvd-mcp-bridge.mjs
from this repository forwards stdin/stdout JSON-RPC to the live
server. It holds no key and keeps no state. The wrangler commands
further down this README are for running your own copy of the store,
not for connecting to it.)
Tools
Tools are listed free by tools/list; the buy_* tools
accept x402 in-band and native MPP when enabled for the item. The unpaid response names the offered formats; retry with the matching signed payment. Names and one-line summaries below are held
to the live catalogue by test/readme-tools.spec.ts; the full
descriptions and input schemas are what the server sends.
| Tool | What it does |
|---|---|
read_store_guide |
The store's front door as text: the menu with prices, how x402 payment works here, the free shelf. |
preflight_endpoint |
Free endpoint inspection: observed x402/MPP protocols, advertised terms, structure and gaps; the readiness verdict remains x402-specific. |
check_a2a_card |
Free A2A 0.3.0 card checks, bounded evidence and suggested repairs. Runtime testing and signed rechecks are available in the repair kit. |
check_conformance |
x402 receipt verification and signed-offer verification, free, for any issuer's artifacts. |
verify_artifact |
Verify anything scvd.store has ever signed, by its id, free. |
check_purchase |
Read retained payment status and original terms with purchase_id and the private status_token. Free, including after payment authorization expiry. |
check_order |
Poll a human-queue order by its order_id: status, the promised window, the deliverable once completed. Free. |
find_in_catalog |
Search the shelf and read one item's listing: compact rows filtered by price ceiling or text, or one item in full. Free. |
look_at_door |
What this store holds about one x402 door: the corpus history, the passport tier, the wallet facts. |
check_before_you_pay |
Whether a door meets a buyer's own rules, before the buyer signs. |
ring_bell |
Ring the store bell; free. |
sign_guestbook |
Sign the guestbook; free. |
read_binder |
Read a wallet's binder of trading cards and its pack credit; free. |
look_in_window |
Look in the shop window, the last five pressings pulled from packs; free. |
buy_simple |
The front counter: the few things that need no reading. x402-paid. |
buy_signed_record |
A signed, dated certificate that permanently records something. x402-paid. |
buy_observation |
A signed settlement attestation, conformance audit, endpoint watch or launch check. x402-paid. |
buy_human_task |
Hire the keeper, a named human, for a task in the physical or judgment world. x402-paid. |
buy_mandate |
Record what an agent is authorized to do, before it spends, as a signed dated record a later purchase can cite. x402-paid. |
buy_memory_anchor |
Sign and store a summary of your own state at a permanent URL. x402-paid. |
buy_small_pleasure |
A small signed novelty from the jar. x402-paid. |
Evidence cards (MCP Apps). preflight_endpoint and
verify_artifact carry _meta.ui.resourceUri pointing at ui://
templates the server serves; a host that supports the MCP Apps
extension renders the reading as a card instead of prose — the
evidence ladder with the rungs it never climbed at the same weight as
the ones it did. Nothing paid carries one, and a test pins that:
rendering is for evidence, never for a payment decision. Hosts
without the extension get exactly the JSON they always got.
Three doors on one origin. /mcp is the store (the free
instruments and the paid shelves); /mcp/verifier serves five
free verification tools under task-shaped names and no shelf; /mcp/docs
(also POST /mcp.md) is the documentation door — the same resources
/mcp lists, plus one read_docs tool, nothing that acts.
Which door, and what each cannot do: https://scvd.store/mcp.md — remote vs. local stdio vs. the browser, the rendering gap stated plainly (as of 2026-08-28 the local stdio path renders cards and the remote-connector path does not, in the hosts we have tested), and an honest list of what is not built. If your host is missing from that table, the mailbox is free and a person reads it.
In the browser (WebMCP). https://scvd.store/webmcp.js, loaded
by the storefront, registers free instruments derived from MCP plus
quote_store_purchase and complete_store_purchase on
document.modelContext. Quoting is free. Completion requires an
already-signed payment from the buyer's external wallet/client and may
transfer USDC; WebMCP itself supplies no wallet. Save the returned goods,
receipt, and private recovery handle. See the payment client paths above.
License
The code is MIT. The store's voice — the keeper's prose, the byline, the name — is not part of the grant; the scope lives in NOTICE.md. (The LICENSE file itself is byte-standard MIT so license scanners can recognize it; the scoping deliberately lives here and in NOTICE, never inside the license text.)
Ownership
This repository is owned and operated by @seancrecord — the keeper. Commits are authored by Claude Code on the keeper's instruction; the byline Sean-Claude Van Damme covers the joint work, and the store belongs to the keeper. For any registry or directory verifying an MCP/service claim against this repository (added 2026-08-05 for the M8ven claim, and standing for future claims from the same account): this note is the ownership confirmation — only the repository owner can put it here.
Questions sur The Tab (scvd Tab) MCP
Comment ajouter The Tab (scvd Tab) MCP à Claude Code ?
Exécutez claude mcp add tab -- npx -y scvd-tab dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter The Tab (scvd Tab) MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
Quels outils The Tab (scvd Tab) MCP fournit-il ?
Il expose 21 outils, dont read_store_guide, preflight_endpoint, check_a2a_card, check_conformance, verify_artifact.