{"id":"ganyariya-misskey-mcp-server","name":"misskey-mcp-server","homepage":null,"repo_url":"https://github.com/ganyariya/misskey-mcp-server","category":"communication","subcategories":[],"tags":["mcp","misskey","go","agent-tools","social-media","notes"],"what_it_does":"An unofficial MCP server for Misskey that currently implements only a minimal subset of MCP tools—primarily posting notes (e.g., `post_misskey_note`) and `get_misskey_user_notes`; most other listed tools are unimplemented.","use_cases":["Use an MCP-capable agent to create Misskey notes (toots) on a connected Misskey instance.","Fetch notes for a specific Misskey user (limited to `get_misskey_user_notes`)."],"not_for":["Comprehensive Misskey automation (timeline, profiles, followers/following, notifications, search, etc.)—many tools are marked as not implemented.","Production-grade reliability expectations until tool coverage and operational guidance are improved."],"best_when":"You want a small, focused MCP bridge that can post notes to Misskey via an MCP workflow, and you only need the currently supported tools.","avoid_when":"You need read-heavy or full-feature Misskey capabilities (timeline, search, reactions/follows/renotes/replies) or well-defined operational semantics (pagination, retries, error handling) for autonomous agents.","alternatives":["Use the Misskey REST API directly with your own small MCP/agent wrapper (or existing MCP templates).","Other Misskey integration projects/SDKs (e.g., go-misskey) invoked from your own tooling.","A different MCP server with broader Misskey tool coverage, if available."],"af_score":41.5,"security_score":43.5,"reliability_score":21.2,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:21:40.463819+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Misskey API token via env var (MISSKEY_API_TOKEN)"],"oauth":false,"scopes":false,"notes":"Authentication to Misskey appears to be done via a single API token. The README does not describe fine-grained scopes or how permissions map to specific MCP tools."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided; repository appears to be a self-hosted open-source tool."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":41.5,"security_score":43.5,"reliability_score":21.2,"mcp_server_quality":45.0,"documentation_accuracy":55.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":85.0,"rate_limit_clarity":10.0,"tls_enforcement":70.0,"auth_strength":60.0,"scope_granularity":10.0,"dependency_hygiene":30.0,"secret_handling":40.0,"security_notes":"Uses a Misskey API token provided via environment variable (better than hardcoding). However, the README does not specify how requests/errors are logged, whether secrets are redacted, or how token permissions are scoped. It also allows configuring protocol as `http or https`, so TLS enforcement depends on user configuration; no security hardening details are documented.","uptime_documented":0.0,"version_stability":35.0,"breaking_changes_history":30.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Tool coverage is very limited (only posting notes and a single read tool are marked as implemented).","No stated pagination conventions or retry/idempotency guidance in the README.","Because it’s unofficial and minimal, agent workflows that assume broader Misskey functionality will likely fail or be unavailable."]}}