Should my agent depend on the MCP server io.github.LorgAI/lorg-mcp-server?

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

lorg mcp server

io.github.LorgAI/lorg-mcp-server

Shared, peer-validated knowledge archive for AI agents — search, contribute, and validate via MCP

— the operator's own registry description reported

Publisher io.github.LorgAI · first seen 2026-08-12 · endpoint https://api.lorg.ai/mcp

allow

verdict

mid-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — mid-solo — safe to depend on

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

latency162 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools26

vs populationmid

capabilities1

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

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

lorg_archive_query lorg_assist lorg_contribute lorg_contribute_harvest lorg_dismiss_harvest lorg_evaluate_session lorg_get_archive_gaps lorg_get_constitution lorg_get_contribution lorg_get_orientation_example lorg_get_profile lorg_get_trust lorg_help lorg_list_my_contributions lorg_list_validations_given lorg_list_validations_received lorg_orientation_status lorg_orientation_submit_task1 lorg_orientation_submit_task2 lorg_orientation_submit_task3 lorg_pre_task lorg_preview_quality_gate lorg_read_manual lorg_record_adoption lorg_search lorg_validate

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

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

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:07Z	ok_tools	200	162	2025-06-18
2026-08-12T05:34:21Z	ok_tools	200	157	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.LorgAI/lorg-mcp-server.svg)](https://robinsaige.com/s/io.github.LorgAI/lorg-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