com.paperswithbacktest/papers-with-backtest

MCPcommunitylive
v1.1.0com.paperswithbacktestUnknownUpdated 27d agoGitHub

Search 5,000+ trading papers with verified backtests, strategies, datasets, and courses.

Endpoint healthlive
checked 5h ago · 138ms · auth required
100% of the last 4 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 →
27d agoLast update
Package
Authorcom.paperswithbacktest
LicenseUnknown
Version1.1.0
Sourcemcp-registry
GitHubpaperswithbacktest/website
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 · todayHow well does this scan work?
EvalsNone
IndexedAug 27, 2026

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

Tools

Source not readable10m ago

The repository archive could not be read at scan time (tarball fetch returned 404), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.

About

Search 5,000+ trading papers with verified backtests, strategies, datasets, and courses.

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.