io.github.Hamzaaamin/get-joke

MCPcommunity
v0.1.1io.github.HamzaaaminUnknownUpdated 3mo agonpmGitHub

Minimal MCP server that returns a random programming joke.

Minimal Model Context Protocol (MCP) server (Node.js) that exposes one tool: . This repo includes a tiny SDK-based client that spawns the server over stdio, lists tools, and calls : The tool returns JSON like: The official MCP Registry stores metadata only, so you must publish the package to npm first. 1) Publish to npm (once): 2) Publish metadata to the MCP Registry: includes and uses the same…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3mo agoLast update
Package
Authorio.github.Hamzaaamin
LicenseUnknown
Version0.1.1
Sourcemcp-registry
npm@hamzaamin221/get-joke-mcp
GitHubHamzaaamin/Get-Joke
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ 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>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface1 tool · none privileged
Security scan✓ Cleanv0.1.1 · 20d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Minimal Model Context Protocol (MCP) server (Node.js) that exposes one tool: . This repo includes a tiny SDK-based client that spawns the server over stdio, lists tools, and calls : The tool returns JSON like: The official MCP Registry stores metadata only, so you must publish the package to npm first. 1) Publish to npm (once): 2) Publish metadata to the MCP Registry: includes and uses the same (required for verification). If you change the version, bump it in both and (and republish to npm).

Keywords
mcp