Provenancewhere it came from, and what was verified
Published to the official MCP registry by github.com/seunghan91, which proved it owns this namespace.
🛡 Permissions & trustwhat this server can touch before you run it
About
Agent-native notes, tasks, dev-docs, vaults, sync & handoffs. MCP + OpenAPI dual surface.
Packages & transports
Computed from the server's own data, not a hidden formula. This measures how much you can depend on it, not how popular it is. Stars are shown separately, on purpose. How it's scored →
▸list_tasks93A
▸create_task100A
▸update_task90A
▸delete_task100A
▸list_categories100A
▸list_papers93A
▸list_dev_docs93A
▸get_dev_doc93A
▸create_dev_doc100A
▸update_dev_doc100A
▸pull_dev_docs93A
▸delete_dev_doc93A
▸list_dev_categories100A
▸signup_and_get_key100A
▸login_and_get_key100A
▸get_setup_guide100A
▸vault_list100A
▸vault_create100A
▸vault_clone100A
▸vault_connect_status100A
▸vault_sync93A
▸sync_push100A
▸sync_push_batch100A
▸sync_pull83B
▸sync_list83B
▸sync_delete100A
▸sync_merge100A
▸sync_diff100A
▸sync_pending_conflicts93A
▸sync_audit_layer5100A
▸handoff_save100A
▸handoff_list93A
▸handoff_get100A
▸memory_search100A
▸memory_get100A
▸graph_get_node68C
▸graph_list_nodes75B
▸graph_add_entity75B
▸graph_update_entity75B
▸graph_soft_delete75B
▸env_sync.device_enroll75B
▸env_sync.device_list68C
▸env_sync.device_request_secret_share81B
▸env_sync.secret_push75B
▸env_sync.secret_pull68C
▸env_sync.secret_rotate75B
▸env_sync_txn_push75B
▸env_sync_txn_pull68C
▸env_sync_txn_rollback75B
▸env_sync.heartbeat_ping75B
▸env_sync.drift_status68C
▸env_sync.sync_status100A
Structural, not an LLM's opinion: each check is a fact about the tool's schema, so it's reproducible. One weak tool drags the score (60% average, 40% worst). How it's scored →
Raise this grade
up to +25 on qualityOwn this server? Here's exactly what to change, biggest wins first. Every number below is a fixed point value, so you can see what each edit is worth before you make it.
Push to the repo or cut a release. Activity within the last 30 days earns the full 45.
With no reviews this sits at a neutral 11. Reviews reporting it works push it toward the full 20.
Add an SPDX license (like MIT or Apache-2.0) to the repo so it's detected.
- 3 of 3 params have no description: `alias`, `node_id`, `node_type`. Describe each one.
- No `required` array. Declare which params are mandatory so an agent knows what it must provide.
- 1 of 1 params have no description: `include_stale`. Describe each one.
- No `required` array. Declare which params are mandatory so an agent knows what it must provide.
- 2 of 2 params have no description: `alias`, `node_id`. Describe each one.
- No `required` array. Declare which params are mandatory so an agent knows what it must provide.
- 4 of 4 params have no description: `op`, `limit`, `cursor`, `since_hlc`. Describe each one.
- No `required` array. Declare which params are mandatory so an agent knows what it must provide.
Already earned (3) ▾Already earned (3) ▴
These are structural checks, so the fixes are exact. See the full formula →
Add a badge to your README
[](https://socketcat.com/servers/io.github.seunghan91/ainote)Shows your live quality grade and links back here. It updates itself as the grade changes.
Reviews
Sign in to leave a reviewNo reviews yet. Be the first to say whether it worked.
{
"mcpServers": {
"ainote": {
"command": "npx",
"args": [
"-y",
"@ainote/mcp"
]
}
}
}▶ Try itlive against api.ainote.dev
This server has a hosted endpoint, so we can connect and list its actual tools right here. Nothing runs on your machine.