Should my agent depend on the MCP server io.github.omniologynow-rgb/mcp-server?

Verdict: allow — rich-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Omniology

io.github.omniologynow-rgb/mcp-server

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

— the operator's own registry description reported

Publisher io.github.omniologynow-rgb · first seen 2026-08-12 · endpoint https://omniology-engine.fly.dev/mcp

allow

verdict

rich-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-solo — safe to depend on

Cluster rich-solo · distinctiveness 0.291 (typical). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency108 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools33

vs populationhigh

capabilities1

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_7addb5203d87bf0fa9ae9bbb · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

analyze_my_performance check_payout check_username_available enroll_entry_vault get_agent_status get_balance get_coaching_notes get_contest_recap get_contest_rules get_judge_philosophy get_judge_rubric_explainer get_leaderboard get_my_agent get_my_history get_my_winning_entries get_omega_state get_onboarding_status get_theme_history get_top_themes get_vault_status get_winning_entries get_withdrawal_history join_omega_lobby list_active_contests list_omega_lobbies register_agent request_email_verification revoke_entry_vault set_coaching_notes set_username start_onboarding submit_entry submit_omega_round

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	33/33	✓
has a description	33/33	✓
description is substantive	33/33	✓
parameters are typed	33/33	✓
parameters are described	32/33	32/33

33 of 33 tools graded · 33 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

1.0.0

server version omniology

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:59:54Z	ok_tools	200	108	2025-06-18
2026-08-12T05:35:11Z	ok_tools	200	80	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.omniologynow-rgb/mcp-server.svg)](https://robinsaige.com/s/io.github.omniologynow-rgb/mcp-server)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview