scvd-tab

MCPcommunity
v0.11.4scvd.storeMITUpdated 3d agonpmGitHub

The Tab: an MCP server that keeps the running account of every tool a builder signs up for — trial deadlines, burn, price drift, and what each signup demanded of a human. Local JSONL, append-only, zero dependencies; nothing leaves the file without deliber

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
42Downloads/wk
3GitHub stars
3Forks
3d agoLast update
Package
Authorscvd.store
LicenseMIT
Version0.11.4
Sourcenpm+mcp-registry
npmscvd-tab
GitHubseancrecord/scvd-general-store-repo
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 0 resolved · none vulnerable
Tool surface18 tools · none privileged
Security scan✓ Cleanv0.4.3 · 2mo agoHow well does this scan work?
EvalsNone
IndexedAug 11, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

18 tools · none privileged
Statically extracted from the published packagev0.4.3 · 2mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

log_tool_eventNo description published

This tool published no description. Forge does not invent one.

capture_tool_eventNo description published

This tool published no description. Forge does not invent one.

burn_rollupNo description published

This tool published no description. Forge does not invent one.

record_coverageNo description published

This tool published no description. Forge does not invent one.

sweep_tallyNo description published

This tool published no description. Forge does not invent one.

sweep_finishNo description published

This tool published no description. Forge does not invent one.

reconcile_card_statementNo description published

This tool published no description. Forge does not invent one.

trials_converting_soonNo description published

This tool published no description. Forge does not invent one.

check_before_signupNo description published

This tool published no description. Forge does not invent one.

stack_auditNo description published

This tool published no description. Forge does not invent one.

whats_currentNo description published

This tool published no description. Forge does not invent one.

contribute_anonymized_deltaNo description published

This tool published no description. Forge does not invent one.

confirm_entryNo description published

This tool published no description. Forge does not invent one.

needs_attentionNo description published

This tool published no description. Forge does not invent one.

whats_dueNo description published

This tool published no description. Forge does not invent one.

acknowledge_pagesNo description published

This tool published no description. Forge does not invent one.

set_consentNo description published

This tool published no description. Forge does not invent one.

export_tabNo description published

This tool published no description. Forge does not invent one.

0 of 18 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

The Tab: an MCP server that keeps the running account of every tool a builder signs up for — trial deadlines, burn, price drift, and what each signup demanded of a human. Local JSONL, append-only, zero dependencies; nothing leaves the file without deliber

Keywords
mcpmcp-serversubscriptionstrialsagent-toolstool-trackingsignup-frictionagent-readiness
Alternatives
Comparing tool surfaces…

Tools exposed

18 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.