api.ainote.dev
https://api.ainote.dev/api/mcp
active Production-safe Score 85/100 http no auth
At a glance
| Endpoint | https://api.ainote.dev/api/mcp |
|---|---|
| Source | https://api.ainote.dev |
| Transport | http |
| Tools | 35 |
| Auth | none |
| First seen | 2026-05-24 21:57:22 |
| Last checked | 2026-11-17 21:48:25 |
Observed reliability
| 7-day uptime | 99% |
|---|---|
| 24-hour uptime | 99% |
| Handshake success | 100% |
| Latency p50 / p95 | 1328 / 1599 ms |
| Last successful check | 2026-11-17 21:48:25 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (35)
delete_task— Soft-delete a task by ID. Destructive but reversible within 30 days (TaskCleanupJob purges trash daily at 2am KST). Returns 404 if the tasklist_papers— List notes/papers from AI Note. Supports keyword search across title and content, category filtering, pagination, and sorting. Returns id/tiproject_read— List the authenticated user's projects (L2 intent layer), or fetch one by id. Each entry includes riskiest_assumption — the single highest-pproject_write— Create or update a project (L2 intent layer). Omit `id` to create, pass it to update. There is no delete tool — use status: 'archived' to reassumption_write— Create or update an assumption under a project (L2 intent layer). Omit `id` to create, pass it to update. There is no delete tool. 🔴 `verdjudgment_submit— Request a human judgment (L3 layer) by attaching evidence — approval, evidence, or verdict. This is the ONLY door an agent has into the judgjudgment_list— List the authenticated user's own judgments (L3 layer) — use this to check your own blocking status (risk_tier 1 pending = execution blockeddelete_dev_doc— Soft-delete a dev document by title or UUID. Reversible from trash. Pass `category` when multiple docs share the same title across subcategoget_setup_guide— Get instructions for setting up AI Note MCP in Claude Desktop, Cursor, or other MCP clients. No authentication required.vault_create— Create a new private vault as a GitHub repository under the user's account. Requires the user to have completed the GitHub App install flowvault_sync— Wrapper around vault file sync. action=list|pull|push to work against the primary vault. list/pull are paginated — narrow with `path`/`sincesync_push— Push a markdown file into the primary vault. Optional CAS via base_sha to detect concurrent multi-PC writes (Layer 3 of multi-PC sync plan).sync_push_batch— Push MANY files into the primary vault in ONE call. Use this instead of looping sync_push whenever you have more than a couple of changed pasync_changes— Read changes from the primary vault in sequence order, including deletions. Start with since_seq=0 for a full listing; then pass next_seq ansync_delete— Delete a file from the primary vault. Optional CAS via base_sha to detect concurrent multi-PC writes. Protected paths (global/memory/, globasync_audit_layer5— Record the result of a client-side Layer 5 codex review (sync.py merge gate) as a vault_events row. Body of the review is NOT stored — onlyhandoff_save— Save a session handoff note for cross-device / cross-session continuation. Stored at handoffs/{project}-{topic}-{YYYY-MM-DD}.txt in the usergraph_soft_delete— Soft-delete an env_sync graph node (sets deleted_at; .live scope hides it from reads). Idempotent — re-deleting a deleted node is a no-op suenv_sync.secret_push— Push a new client-encrypted secret. Ciphertext only — server never sees plaintext. Recipients must include the pushing device's own pubkey.env_sync.secret_pull— Pull an encrypted secret blob. Response is ciphertext_b64 only — server never sees and never returns plaintext.env_sync.secret_rotate— Rotate a secret: soft-delete the old node, create a new live node with the same alias and the new ciphertext+recipients. 7-day grace beforeenv_sync_txn_push— Ingest a batched envelope of client-recorded env_sync mutations. HLC-skew gated, partial-success on conflict.env_sync_txn_rollback— Inverse-apply a prior env_sync transaction. Safety gates: ownership, idempotency, descendant-conflict (force opt-out).tasks_read— Read tasks and task categories. action: tasks | categories (consolidated surface — same handlers as the legacy tools)task_write— Create or update a task. action: create | update. Deletion is a separate tool (delete_task). (consolidated surface — same handlers as the ledev_docs_read— Read dev docs. action: get | list | categories | pull (consolidated surface — same handlers as the legacy tools)dev_doc_write— Create or update a dev doc. action: create | update. Deletion is a separate tool (delete_dev_doc). (consolidated surface — same handlers assync_read— Read-only vault sync operations. action: list | pull | diff | merge | conflicts. Writes (push/delete) are separate tools — they carry CAS sevault_read— Read vault metadata. action: list | clone | status (consolidated surface — same handlers as the legacy tools) Required per action — clone: nenv_sync_read— Read env-sync state. action: devices | drift | status | txn_pull. Secret reads are a separate tool (env_sync.secret_pull). (consolidated surenv_sync_write— Non-destructive env-sync writes. action: enroll | request_share | heartbeat. Secret push/rotate are separate tools. (consolidated surface —graph_read— Read knowledge-graph nodes. action: get | list (consolidated surface — same handlers as the legacy tools)graph_write— Add or update a graph entity. action: add | update. Deletion is a separate tool (graph_soft_delete). (consolidated surface — same handlers ahandoff_read— Read session handoffs. action: get | list (consolidated surface — same handlers as the legacy tools) Required per action — get: project, topmemory_read— Read agent memory. action: get | search (consolidated surface — same handlers as the legacy tools) Required per action — get: source | searc
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:48:25 | ✓ | ✓ | 1508 ms | 85 | active |
| 2026-11-17 21:33:24 | ✓ | ✓ | 1300 ms | 85 | active |
| 2026-11-17 21:18:23 | ✓ | ✓ | 1543 ms | 85 | active |
| 2026-11-17 21:03:21 | ✓ | ✓ | 1640 ms | 85 | active |
| 2026-11-17 20:48:19 | ✓ | ✓ | 1496 ms | 85 | active |
| 2026-11-17 20:33:17 | ✓ | ✓ | 1390 ms | 85 | active |
| 2026-11-17 20:18:16 | ✓ | ✓ | 1598 ms | 85 | active |
| 2026-11-17 20:03:14 | ✓ | ✓ | 1403 ms | 85 | active |
| 2026-11-17 19:48:13 | ✓ | ✓ | 1304 ms | 85 | active |
| 2026-11-17 19:33:11 | ✓ | ✓ | 1399 ms | 85 | active |
| 2026-11-17 19:18:10 | ✓ | ✓ | 1308 ms | 85 | active |
| 2026-11-17 19:03:08 | ✓ | ✓ | 1453 ms | 85 | active |
| 2026-11-17 18:48:07 | ✓ | ✓ | 1320 ms | 85 | active |
| 2026-11-17 18:32:57 | ✓ | ✓ | 1429 ms | 85 | active |
| 2026-11-17 18:17:51 | ✓ | ✓ | 1510 ms | 85 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://api.ainote.dev/api/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/api-ainote-dev-api-mcp # JSON