Osmosis-Apply-1.7B-MCP

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.

Evaluated Mar 30, 2026 (21d ago)
Repo ↗ Infrastructure osmosis mcp agent-tools blockchain automation
⚙ Agent Friendliness
32
/ 100
Can an agent use this?
🔒 Security
36
/ 100
Is it safe for agents?
⚡ Reliability
22
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
40
Documentation
30
Error Messages
0
Auth Simplicity
50
Rate Limits
10

🔒 Security

TLS Enforcement
50
Auth Strength
30
Scope Granularity
20
Dep. Hygiene
40
Secret Handling
40

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.

⚡ Reliability

Uptime/SLA
0
Version Stability
40
Breaking Changes
30
Error Recovery
20
AF Security Reliability

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

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

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

Free tier: No
Requires CC: No

Pricing details were not provided.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known 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.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Osmosis-Apply-1.7B-MCP.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-30.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered