tyrekick-mcp
MCP@richardofortuneRead and resolve human feedback pinned on your live prototype, straight from your coding agent.
Works in
ClaudeCursorCopilotGemini
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Identity-verified publisher GitHub@richardofortune
18d agoLast update
Package
Authorio.github.richardofortune
LicenseUnknown
Version0.3.1
Sourcenpm+mcp-registry
npmtyrekick-mcp
GitHubrichardofortune/tyrekick
SBOMCycloneDX 1.6 ↓
Trust Status
D
30/100Risk
✓Listed in Forge index+10/10
✓Publisher identity verified+20/20
—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
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
—CVE scan · not run+0/30
→ Not yet scanned — package must be on npm
—Static analysis · clean+0/20
→ Not yet scanned — package must be on npm
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
Publisher@richardofortune
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scanNot runHow well does this scan work?
EvalsNone
IndexedJul 8, 2026
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Tools
Not scanned yet
Forge has no scan on record for this entry, so it holds no observation of its tool surface. That is an absence of evidence, not evidence that it exposes no tools.
About
Read and resolve human feedback pinned on your live prototype, straight from your coding agent.
Keywords
mcp
Alternatives
Comparing tool surfaces…