io.github.harrisboatworks/mercury-repower

MCPcommunitylive
v1.0.0io.github.harrisboatworksUnknownUpdated 4mo agoGitHub

Live Mercury outboard data and CAD quote builder from a Mercury Platinum Dealer in Ontario.

There are several ways of editing your application. Simply visit the Lovable Project and start prompting. Changes made via Lovable will be committed automatically to this repo. Use your preferred IDE If you want to work locally using your own IDE, you can clone this repo and push changes. Pushed changes will also be reflected in Lovable. The only requirement is having Node.js & npm installed -…

Endpoint healthlive
checked 9 days ago · 900ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (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 →
1Forks
4mo agoLast update
Package
Authorio.github.harrisboatworks
LicenseUnknown
Version1.0.0
Sourcemcp-registry
GitHubharrisboatworks/mercury-builder-pro
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

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

Tools

Source not readable3mo ago

The repository archive could not be read at scan time (The operation was aborted due to timeout), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.

About

There are several ways of editing your application. Simply visit the Lovable Project and start prompting. Changes made via Lovable will be committed automatically to this repo. Use your preferred IDE If you want to work locally using your own IDE, you can clone this repo and push changes. Pushed changes will also be reflected in Lovable. The only requirement is having Node.js & npm installed - install with nvm Edit a file directly in GitHub Navigate to the desired file(s). Click the "Edit"…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.