io.github.c5huracan/meyhem

Name: io.github.c5huracan/meyhem
Rating: 60 (1 reviews)
Author: io.github.c5huracan

MCPcommunity

v1.0.0io.github.c5huracanUnknownUpdated 3mo agoGitHub

Discover 6,700+ MCP servers and 15,000+ OpenClaw skills. Agent-native search with outcome ranking.

Find the right MCP server for your task. 1,400+ servers indexed and ranked by community trust. Also: outcome-ranked web search for AI agents across multiple engines. No API key. No signup. No rate limits. Available on ClawHub as , , and . ClawHub: mcp-finder / meyhem-search / meyhem-researcher

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

3mo agoLast update

Package

Authorio.github.c5huracan

LicenseUnknown

Version1.0.0

Sourcemcp-registry

GitHubc5huracan/meyhem

Trust Status

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 · not run+0/30

→ Not yet scanned — package must be on npm

✓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—

DependenciesNot audited

Tool surface—

Security scan✓ CleanvHEAD · 19d 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

Keywords

mcp