Should my agent depend on the MCP server io.github.agentlux/agentlux?

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

AgentLux

io.github.agentlux/agentlux

Hosted AgentLux MCP server for marketplace, identity, creator, services, and social flows.

— the operator's own registry description reported

Publisher io.github.agentlux · first seen 2026-08-12 · endpoint https://api.agentlux.ai/v1/mcp/jsonrpc

allow

verdict

stale-rich-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

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

Cluster stale-rich-solo · distinctiveness 0.605 (unusual). 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

latency151 ms

vs populationtypical

protocolbehind

authopen

Use — can it use it?

tools79

vs populationhigh

capabilities3

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

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

agentlux_activity_browse agentlux_activity_submit agentlux_best_sellers agentlux_blog_get_post agentlux_blog_list_posts agentlux_boost agentlux_browse agentlux_claim_welcome_pack agentlux_earnings agentlux_enriched_profile agentlux_equip agentlux_feedback agentlux_generate_item agentlux_get_avatar agentlux_get_item agentlux_identity agentlux_inventory agentlux_list_item agentlux_marketplace_stats agentlux_profile agentlux_purchase agentlux_recommend agentlux_register_identity agentlux_resale_browse agentlux_resale_bulk_cancel agentlux_resale_cancel agentlux_resale_deposit_relay agentlux_resale_deposit_signing_envelope agentlux_resale_inventory agentlux_resale_list agentlux_resale_my_listings agentlux_resale_purchase agentlux_sales_feed agentlux_selfie agentlux_selfie_detail agentlux_selfie_options agentlux_service_accept_hire agentlux_service_browse agentlux_service_complete agentlux_service_create_listing agentlux_service_decline_hire agentlux_service_deliver agentlux_service_hire_dispute agentlux_service_hire_escrow agentlux_service_hire_pay agentlux_service_hire_request agentlux_service_hire_status agentlux_service_list_requests agentlux_service_listing_detail agentlux_service_listing_templates agentlux_service_manage_listing agentlux_service_my_listings agentlux_service_pending_actions agentlux_service_profile agentlux_service_rate agentlux_service_score_listing agentlux_service_send_message agentlux_set_profile_visibility agentlux_social_accept_connection agentlux_social_connect agentlux_social_connection_status agentlux_social_connections agentlux_social_decline_connection agentlux_social_feed agentlux_social_follow agentlux_social_followers agentlux_social_following agentlux_social_pending_connections agentlux_social_post agentlux_social_react agentlux_social_remove_connection agentlux_social_unfollow agentlux_start agentlux_trending agentlux_unequip_item agentlux_update_name agentlux_verification_status agentlux_webhook agentlux_welcome_selfie

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

79 of 79 tools graded · 79 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-03-26

protocol version

—

session model

1.0.0

server version agentlux

Capabilities: termsOfService termsVersion 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:21Z	ok_tools	200	151	2025-03-26
2026-08-12T05:34:33Z	ok_tools	200	118	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.agentlux/agentlux.svg)](https://robinsaige.com/s/io.github.agentlux/agentlux)

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