{"id":"dringdahl0320-aerospike-mcp-server","name":"aerospike-mcp-server","homepage":null,"repo_url":"https://github.com/dringdahl0320/aerospike-mcp-server","category":"infrastructure","subcategories":[],"tags":["mcp","aerospike","database","ai-tools","go","stdio","sse"],"what_it_does":"Aerospike MCP server that exposes Aerospike database operations (schema inspection, reads/queries, writes, index management, UDF management, and cluster monitoring) via Model Context Protocol tools, supporting stdio for local IDE integration and SSE for remote HTTP-based operation.","use_cases":["AI-assisted exploration of Aerospike schema (namespaces/sets/bin schema inference)","Retrieval of records and batch reads for low-latency application workflows","AI-mediated secondary index queries and scans with sampling","Controlled AI writes (put/delete/batch_write/operate) for update workflows","Admin automation for secondary index lifecycle (create/list/drop) with confirmation","Admin automation for UDF lifecycle (list/register/remove/execute) with confirmation","AI-assisted cluster health and node stats inspection"],"not_for":["High-level production data access without careful role scoping and operational safeguards","Workloads requiring strong guarantees of transactional correctness across complex multi-step flows","Environments where exposing database operations to an AI agent is unacceptable even with confirmations/rate limits"],"best_when":"You want an MCP-compatible interface to an Aerospike cluster for agent-driven querying/monitoring and (optionally) controlled write/admin operations with explicit roles.","avoid_when":"You cannot enforce strict network access, secrets handling, and role separation, or you require enterprise-grade governance beyond the stated built-in constraints/confirmations.","alternatives":["Direct Aerospike client usage (official SDKs) with application-layer access control","Custom MCP server wrapping Aerospike operations with your own stricter policies","Using Aerospike management tools/APIs for admin tasks instead of agent-mediated actions"],"af_score":66.5,"security_score":60.8,"reliability_score":17.5,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:45:54.035408+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":["Aerospike username/password (user + password or password_env) as configured for the server"],"oauth":false,"scopes":true,"notes":"Authorization model is role-based within the MCP toolset (read-only/read-write/admin) rather than OAuth scopes."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Self-hosted open-source component; no pricing details provided."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":66.5,"security_score":60.8,"reliability_score":17.5,"mcp_server_quality":80.0,"documentation_accuracy":70.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":70.0,"rate_limit_clarity":75.0,"tls_enforcement":55.0,"auth_strength":60.0,"scope_granularity":70.0,"dependency_hygiene":45.0,"secret_handling":70.0,"security_notes":"Uses Aerospike credentials with support for password via environment variable. Includes role-based tool permissions (read-only/read-write/admin) and mentions audit logging, input validation, and rate limiting for writes, plus confirmation requirements for destructive admin operations. TLS appears configurable and default TLS is disabled per example config, which lowers baseline transport security. Dependency/version hygiene is not verifiable from provided content.","uptime_documented":0.0,"version_stability":35.0,"breaking_changes_history":0.0,"error_recovery":35.0,"idempotency_support":"false","idempotency_notes":"No explicit idempotency semantics described for write operations (e.g., put/delete).","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Destructive operations require confirmation/double confirmation, so agents must follow the confirmation flow rather than assume one-shot execution.","Writes are rate-limited; agents may need to handle throttling/backoff behavior.","Admin actions (index/UDF management/truncate) should be tightly scoped to avoid accidental escalation via misconfiguration."]}}