lodestar-stamp-mcp

Name: lodestar-stamp-mcp
Author: io.github.Banjo-Ventures

MCPcommunitylive

v0.1.12io.github.Banjo-VenturesMITUpdated 7d agonpm GitHub

Dated, source-linked receipts before an agent recommends or books. Lodestar does not approve.

Endpoint healthlive

checked 2 days ago · 324ms

100% of the last 4 checks reached this endpoint

Works in

ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). 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 →

224Downloads/wk

7d agoLast update

Package

Authorio.github.Banjo-Ventures

LicenseMIT

Version0.1.12

Sourcenpm+mcp-registry

npmlodestar-stamp-mcp

GitHubBanjo-Ventures/lodestar

SBOMCycloneDX 1.6 ↓

Trust Status

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 surface5 tools · none privileged

Security scan✓ Cleanv0.1.8 · 25d agoHow well does this scan work?

EvalsNone

IndexedSep 5, 2026

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

Tools

5 tools · none privileged

Statically extracted from the published packagev0.1.8 · 25d 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.

get_receiptNo description published

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

batch_receiptsNo description published

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

find_businessNo description published

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

list_marketsList every Lodestar Stamp market on the record from the live Trust API: slug, name, identity, receipt fields, business count and edition.

List every Lodestar Stamp market on the record from the live Trust API: slug, name, identity, receipt fields, business count and edition.

No input schema was published for this tool.

list_indexList businesses covered by a Lodestar Stamp draft record. Optional market reads that market's index; omitted reads the primary record.

List businesses covered by a Lodestar Stamp draft record. Optional market reads that market's index; omitted reads the primary record.

No input schema was published for this tool.

2 of 5 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

Dated, source-linked receipts before an agent recommends or books. Lodestar does not approve.

Keywords

mcp

Alternatives

Comparing tool surfaces…

lodestar-stamp-mcp

Tools

Tools exposed

Dependency tree