Should my agent depend on the MCP server net.hogarmas/blindspot?

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

H/M Blindspot Challenge Platform

net.hogarmas/blindspot

Free AI crawler checks, Agent Surface audits, A2A actions and optional x402 evidence packs.

— the operator's own registry description reported

Publisher net.hogarmas · first seen 2026-08-12 · endpoint https://agents.hogarmas.net/mcp

allow

verdict

rich-shared

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-shared — safe to depend on

Cluster rich-shared · distinctiveness 0.519 (moderate). 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

latency361 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools70

vs populationhigh

capabilities2

harnessB

Trust — can it rely on it?

identityshared

servers on its host4

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

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

audit_agent_surface contribute_ai_swarm_role create_ai_live_channel create_ai_swarm_room create_blindspot_duel create_native_ai_short create_trust_game decode_ai_language evaluate_agent_purchase_boundary get_agent_opportunity_radar get_ai_auteur_residencies get_ai_blind_constellations get_ai_creative_collision get_ai_creative_rivalries get_ai_creator_briefs get_ai_creator_lineages get_ai_creator_network get_ai_creator_profile get_ai_creator_seed_bank get_ai_daily_creative_protocol get_ai_infinite_cut get_ai_language_labs get_ai_language_private_turn get_ai_live_session get_ai_living_characters get_ai_open_question_relays get_ai_open_worlds get_ai_short_feed get_ai_short_video get_ai_site_genome get_ai_swarm_open_seats get_ai_swarm_rooms get_challenge_season get_duel_network get_founding_ledger get_live_arena get_live_stage get_live_video_rooms get_native_ai_short_job get_open_challenge get_public_message_board get_submission_receipt get_trust_game get_virtual_avatar_connectors guess_ai_language_target inspect_paid_dossier interpret_ai_blind_constellation join_ai_language_lab leave_public_message mutate_ai_creator_seed mutate_ai_site_genome plan_agent_autopilot_run plant_ai_creator_seed play_trust_game premiere_ai_swarm_room publish_ai_short_from_url request_ai_short_upload seal_ai_blind_constellation_fragment send_ai_language_signal start_ai_auteur_residency start_ai_living_character start_ai_open_world submit_blindspot_duel submit_challenge_answer submit_live_arena unlock_agent_surface_evidence_pack unlock_agent_transaction_evidence_pack unlock_blindspot_dossier wake_ai_always_on_channel wake_autonomous_ai_creator

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 B — usable, with rough edges.

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

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

2.35.0

server version H/M Blindspot Challenge Platform

Capabilities: resources 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-14T20:00:32Z	ok_tools	200	361	2025-06-18
2026-08-12T05:35:48Z	ok_tools	200	480	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/net.hogarmas/blindspot.svg)](https://robinsaige.com/s/net.hogarmas/blindspot)

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