Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CoreForge Books

NPM · COREFORGE-BOOKS-MCP

CoreForge book catalogue and book-data tools: lookup, dossier search, verdicts. x402 pay-per-call.

Available components

+6 this week 66 Trust /100

Last scanned (19 hours ago)

Scores higher than 38% of npm servers

Category Education and Research

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 32 of 113 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 15 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 793 tokens (~99/item across 8 items; 8 tools + 0 resources), lean.Pass
  • 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 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.

  • 19 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.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +3
    • Stability: unverified → 0.23 ▲ functional
  • 10 Nov 26 0
    • Source repository: unverified → fail ▼ security
  • 9 Nov 26 60

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/coreforge-books-mcp@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 113 packages
Packages resolved 113
Stale 31
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~793 tokens

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 →

Tool Tokens
book_record ~90

Fetch one full book enrichment record (the complete dossier JSON) from the CoreForge Memory store by dossier id (bk_<16 hex chars>, from book_search). Paid via x402 ($0.05 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

NameTypeReqDescription
dossierIdstringyesDossier id, e.g. bk_0123abcd4567ef89

No output schema declared.

No examples provided.

book_search ~124

Search book data by title text and/or author over the CoreForge Memory dossier store (~1.17M book dossiers) merged with the CoreForge catalogue. Returns dossier summaries (use book_record for a full dossier) plus catalogue matches. Paid via x402 ($0.01 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

NameTypeReqDescription
authorstring–Author name to search for
limitinteger–Max dossiers to return (default 10, max 50)
qstring–Title text to search for

No output schema declared.

No examples provided.

catalogue_lookup ~91

Look up a book in the CoreForge catalogue by ISBN or by title text. Returns metadata, prices and live retailer status. Paid via x402 ($0.01 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

NameTypeReqDescription
isbnstring–ISBN to look up exactly
titlestring–Title text (substring match) — used when no ISBN is given

No output schema declared.

No examples provided.

catalogue_title ~64

Fetch the full CoreForge catalogue record for one ISBN (metadata, prices, live retailer status). Paid via x402 ($0.01 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

NameTypeReqDescription
isbnstringyesThe ISBN to fetch

No output schema declared.

No examples provided.

chapter_verdict ~111

Gate-style heuristic verdict on one fiction chapter (200–400,000 characters): a 1–5 score and binge-worthy flag computed from restatement (repeated passages), dialogue share, a complaint-marker screen and tempo/middle-sag profile. Deterministic — no language model. Paid via x402 ($0.05 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

NameTypeReqDescription
textstringyesThe chapter text to score (at least 200 characters)

No output schema declared.

No examples provided.

meter_estimate ~158

CoreForge Meter GPU-cost estimate: total estimated cost for running a GPU type for a number of hours, computed from public cloud GPU list prices, with the cheapest option as the basis plus alternatives. Estimate only, not a quote. Paid via x402 ($0.05 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

NameTypeReqDescription
countinteger–Number of GPUs (default 1)
gpustringyesGPU type, e.g. 'H100', 'RTX 4090', 'L40S' (see meter_gpus for names)
hoursnumberyesHours to price (0–87600)
providerstring–Restrict to one cloud provider

No output schema declared.

No examples provided.

meter_gpus ~45

Free: list the GPU types CoreForge Meter can price (id, display name, VRAM) — use it to form a valid meter_estimate query. No payment required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

token_verdict ~110

Deterministic token risk verdict from public DEX market data (liquidity depth, market age, volume/liquidity balance, buy/sell balance, market structure): a 0–100 score, band and flags. Not financial advice. Paid via x402 ($0.02 USDC on Base) when a payer wallet is configured; otherwise returns the payment requirements.

NameTypeReqDescription
addressstringyesToken address: an EVM 0x… contract address or a Solana mint address

No output schema declared.

No examples provided.

Install

How do I install the CoreForge Books MCP server?

CoreForge Books runs locally as an npm package, launched with npx -y coreforge-books-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · coreforge-books-mcp

# add to Claude Code
claude mcp add shaficodes25-coreforge-books -- npx -y coreforge-books-mcp
Common questions

What is the CoreForge Books MCP server?

CoreForge Books is an MCP server listed in the public MCP registry as io.github.ShafiCodes25/coreforge-books. CoreForge book catalogue and book-data tools: lookup, dossier search, verdicts. x402 pay-per-call. This page covers its npm package (coreforge-books-mcp).

Is the CoreForge Books MCP server safe to use?

CoreForge Books scores 66 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 CoreForge Books MCP server expose?

CoreForge Books exposes 8 tools: catalogue_lookup, catalogue_title, book_search, book_record, chapter_verdict, and 3 more. Their descriptions and schemas cost roughly 793 tokens of context every time the server is loaded.

Is the CoreForge Books MCP server still maintained?

CoreForge Books is still listed as active in the MCP registry. We last reached this channel on 21 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 CoreForge Books MCP server under?

CoreForge Books declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the CoreForge Books MCP server?

VerifyMCP ran 15 checks on CoreForge Books, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about CoreForge Books: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.