{"id":"osmosis-ai-osmosis-apply-1-7b-mcp","name":"Osmosis-Apply-1.7B-MCP","homepage":null,"repo_url":"https://github.com/Osmosis-AI/Osmosis-Apply-1.7B-MCP","category":"infrastructure","subcategories":[],"tags":["osmosis","mcp","agent-tools","blockchain","automation"],"what_it_does":"An MCP (Model Context Protocol) server/package intended to provide an “Osmosis Apply” capability to AI agents, likely allowing them to generate/submit Osmosis-related transactions or apply changes via MCP tools. The provided input includes only the package name and version, without README/API details.","use_cases":["Letting an AI agent interact with Osmosis-related operations through MCP tool calls","Automating agent workflows that require applying on-chain actions","Integrating Osmosis operations into agent-driven tooling environments"],"not_for":["Human-only manual operations requiring a UI","Production use where security, idempotency, and transaction semantics are not documented","Environments that require strict compliance evidence (SOC2/ISO, etc.) for third-party tooling"],"best_when":null,"avoid_when":null,"alternatives":["Direct use of Osmosis/CosmWasm blockchain tooling (e.g., CLI/SDK) integrated into the agent runtime","Building a custom MCP server that wraps well-documented Osmosis REST/GRPC endpoints","Using existing Osmosis API/SDK integrations (if available) without MCP"],"af_score":32.5,"security_score":35.5,"reliability_score":22.5,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:21:39.078999+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":[],"oauth":false,"scopes":false,"notes":"No authentication details were provided in the input; MCP servers often use indirect auth (agent runtime / environment credentials), but this cannot be verified here."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Pricing details were not provided."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":32.5,"security_score":35.5,"reliability_score":22.5,"mcp_server_quality":40.0,"documentation_accuracy":30.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":50.0,"rate_limit_clarity":10.0,"tls_enforcement":50.0,"auth_strength":30.0,"scope_granularity":20.0,"dependency_hygiene":40.0,"secret_handling":40.0,"security_notes":"No implementation details were provided. For an MCP server that can apply on-chain actions, key risks typically include handling of signing keys, prevention of tool misuse/overreach, and ensuring safe retry/idempotency. These cannot be confirmed from the provided input.","uptime_documented":0.0,"version_stability":40.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":["Transaction/apply operations may be non-idempotent; agents can accidentally submit duplicate actions on retries if idempotency keys or safe retry semantics are not defined.","Without clear tool schemas and response contracts, agents may mis-handle required fields for on-chain operations."]}}