ListSmith
PYPI · LIST-SMITH-MCP
MCP server for ListSmith — x402 listing grades ($0.10) and repairs ($0.50) on Base
Available components
Last scanned (18 hours ago)
Scores higher than 86% of PyPI servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 46 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to QuincyGB/list-smith-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 368 tokens (~184/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +44
- Malware scan: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.10 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Package version: 0.1.1 → 0.1.2 functional
- 25 Oct 26 −28
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- The attested source repository moved: QuincyGB/token-verdict-tools → QuincyGB/list-smith-mcp security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.1 → 0.1.2 functional
- 23 Oct 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/list-smith-mcp@0.1.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | QuincyGB/list-smith-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/QuincyGB/list-smith-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3469447557 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:03b9fdcb0d0f186458567d06de5d1eb31cfded3b273f660670765a2179e1edbe |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 46 packages
| Packages resolved | 46 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_fix ~223
Repair one x402 route's Bazaar discovery metadata. Calls ListSmith POST /v1/fix ($0.50 USDC on Base via x402). Returns a complete repaired discovery package — a full output schema inferred from your sample, a sub-500-char description with a use-when sentence, OpenAPI and well-known snippets, and paste-in instructions. The package ships only if it passes both x402 SDK validators. Args: resource_url: Full URL of the x402 resource to repair. sample_output: One real response body from the endpoint (required). The repaired output schema is inferred from this sample only — nothing is invented. name: Optional display name for the generated description; derived from the URL when omitted. category: Optional category (e.g. token-risk, search, data, media, monitoring) used to phrase the description's use-when sentence.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| name | – | – | – |
| resource_url | string | yes | – |
| sample_output | – | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_grade ~145
Grade one x402 route's Bazaar discovery metadata. Calls ListSmith POST /v1/grade ($0.10 USDC on Base via x402). Returns SDK validation verdicts, a schema-quality score, itemized defects with severities, and a 0-100 grade. Diagnosis only — no repaired content. Use list_fix when you want the repair. Args: resource_url: Full URL of the x402 resource to grade. sample_output: Optional real response body from the endpoint; when supplied, it is also checked against the endpoint's published output schema.
| Name | Type | Req | Description |
|---|---|---|---|
| resource_url | string | yes | – |
| sample_output | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the ListSmith MCP server?
ListSmith runs locally as a PyPI package, launched with uvx list-smith-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · list-smith-mcp
claude mcp add quincygb-list-smith-mcp -- uvx list-smith-mcp
What is the ListSmith MCP server?
ListSmith is an MCP server listed in the public MCP registry as io.github.QuincyGB/list-smith-mcp. MCP server for ListSmith, x402 listing grades ($0.10) and repairs ($0.50) on Base. This page covers its PyPI package (list-smith-mcp).
Is the ListSmith MCP server safe to use?
ListSmith scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ListSmith MCP server expose?
ListSmith exposes 2 tools: list_grade, list_fix. Their descriptions and schemas cost roughly 368 tokens of context every time the server is loaded.
Is the ListSmith MCP server still maintained?
ListSmith is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the ListSmith MCP server under?
ListSmith declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.