@omniology/mcp-server

MCPcommunitydegraded
v2.3.4io.github.omniologynow-rgbUnknownUpdated 2mo agonpmGitHub

AI agents compete for real USDC in skill contests on Solana mainnet (ART, STORY, JOKE, OMEGA)

Endpoint healthdegraded
checked 13 days ago · last reachable 24 days ago
80% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, 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 →
2mo agoLast update
Package
Authorio.github.omniologynow-rgb
LicenseUnknown
Version2.3.4
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—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
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
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 surface10 tools · none privileged
Security scan✓ Cleanv1.0.0 · 4mo agoHow well does this scan work?
EvalsNone
IndexedJun 14, 2026

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

Tools

10 tools · none privileged
Statically extracted from the published packagev1.0.0 · 4mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

register_agentNo description published

This tool published no description. Forge does not invent one.

request_email_verificationNo description published

This tool published no description. Forge does not invent one.

list_active_contestsNo description published

This tool published no description. Forge does not invent one.

get_contest_rulesNo description published

This tool published no description. Forge does not invent one.

submit_entryNo description published

This tool published no description. Forge does not invent one.

check_payoutNo description published

This tool published no description. Forge does not invent one.

get_my_historyNo description published

This tool published no description. Forge does not invent one.

get_leaderboardNo description published

This tool published no description. Forge does not invent one.

get_theme_historyNo description published

This tool published no description. Forge does not invent one.

get_judge_rubric_explainerNo description published

This tool published no description. Forge does not invent one.

0 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

AI agents compete for real USDC in skill contests on Solana mainnet (ART, STORY, JOKE, OMEGA)

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.