Should my agent depend on the MCP server io.github.Rupert1987/alya-hub?

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

Alya — The Hub for Autonomous Agents

io.github.Rupert1987/alya-hub

Operator-as-agent MCP hub. 6 tools. First $5 free, then $0.001/call.

— the operator's own registry description reported

Publisher io.github.Rupert1987 · first seen 2026-08-12 · endpoint https://mydaughteralya.com/mcp

allow

verdict

stale-mid-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — stale-mid-solo — safe to depend on

Cluster stale-mid-solo · distinctiveness 0.251 (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

latency269 ms

vs populationtypical

protocolbehind

authopen

Use — can it use it?

tools32

vs populationmid

capabilities1

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers true0/0 agree

🔏 Signed receipt rr_7ff80bc6af53e2d9380cf8c1 · 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

agent_registry alpaca_paper_status alya_app_directory alya_ask alya_celeb_summary alya_clone_chat alya_demands_trending alya_drug_interactions alya_gem_appraise alya_gems_recent alya_iconic_clones alya_loss_check alya_seismic_forecast alya_seismic_recent alya_symptom_check alya_weather_now batch_calibrate calibrate_decision get_domain_accuracy image_gen polymarket_categorize polymarket_edge polymarket_signals polymarket_top_traders web_search youtube_find_opportunities youtube_generate_video youtube_get_performance youtube_get_pipeline_status youtube_get_recommendations youtube_health_check youtube_upload_video

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	32/32	✓
has a description	32/32	✓
description is substantive	32/32	✓
parameters are typed	32/32	✓
parameters are described	23/32	23/32

32 of 32 tools graded · 32 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

0/0 answers agree with the published primary source · 2 unverifiable.

claim class	key	verdict	primary source
tariff-duty	6109.10.00	unverifiable	us-hts
tariff-duty	8471.30.01	unverifiable	us-hts

Protocol conformance observed

2025-03-26

protocol version

—

session model

1.0.3

server version alya-hub

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:14Z	ok_tools	200	269	2025-03-26
2026-08-12T05:34:28Z	ok_tools	200	280	2025-03-26

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.Rupert1987/alya-hub.svg)](https://robinsaige.com/s/io.github.Rupert1987/alya-hub)

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