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

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

ainote

io.github.seunghan91/ainote

Agent-native notes, tasks, dev-docs, vaults, sync & handoffs. MCP + OpenAPI dual surface.

— the operator's own registry description reported

Publisher io.github.seunghan91 · first seen 2026-08-12 · endpoint https://api.ainote.dev/api/mcp

allow

verdict

rich-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

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

Cluster rich-slow-solo · distinctiveness 0.749 (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

latency396 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools35

vs populationhigh

capabilities4

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

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

assumption_write auth_key delete_dev_doc delete_task dev_doc_write dev_docs_read env_sync.secret_pull env_sync.secret_push env_sync.secret_rotate env_sync_read env_sync_txn_push env_sync_txn_rollback env_sync_write get_setup_guide graph_read graph_soft_delete graph_write handoff_read handoff_save judgment_list judgment_submit list_papers memory_read project_read project_write sync_audit_layer5 sync_delete sync_push sync_push_batch sync_read task_write tasks_read vault_create vault_read vault_sync

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

35 of 35 tools graded · 35 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 ainote-mcp-http

Capabilities: prompts resources sampling 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:12Z	ok_tools	200	396	2025-06-18
2026-08-12T05:35:24Z	ok_tools	200	361	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.seunghan91/ainote.svg)](https://robinsaige.com/s/io.github.seunghan91/ainote)

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