axum-http-mcp-server

Provides an Axum-based MCP server (compiled to WebAssembly in the README) that exposes an HTTP JSON-RPC endpoint (/api/counter in the example) and implements at least a sample tool named "counter" with operations like increment, decrement, and get_value.

Evaluated Apr 04, 2026 (17d ago)

Repo ↗ API Gateway mcp axum json-rpc wasm tool-server agent-integration

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

100

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

README examples use plain HTTP URLs for localhost testing and do not describe TLS enforcement or authentication/authorization. No secret management practices are mentioned. Dependency hygiene cannot be assessed from the provided content.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want a minimal, local/offline MCP tool server interface to prototype agent tool calls over HTTP.

Avoid When

You need enterprise-grade security controls, published reliability/SLA, or well-specified interface contracts beyond the single example.

Use Cases

• Running a lightweight MCP-style tool server over HTTP for agent tool-calling
• Testing/benchmarking agent tool invocation flows using a simple counter tool
• Embedding/hosting MCP tools in environments that can run Wasm (e.g., WasmEdge)

Not For

• Production deployments requiring robust auth, rate limiting, and operational hardening (not evidenced in the provided README)
• Use cases needing standard REST/SDK distribution (the README only shows raw HTTP JSON-RPC calls)
• Applications that require pagination semantics or documented retry/error-recovery guidance

Interface

REST API

Yes

GraphQL

gRPC

MCP Server

Yes ↗

SDK

Webhooks

Authentication

OAuth: No Scopes: No

No authentication mechanism is mentioned in the README examples.

Pricing

Free tier: No

Requires CC: No

Self-hosted open-source project (no hosted pricing info provided).

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ No auth is documented; agents in untrusted networks may be able to call tools if exposed.
⚠ Only a single example tool endpoint/tool name is shown; other tools and argument schemas may not be documented in the provided README excerpt.
⚠ No documented error format or retry/backoff behavior for failed JSON-RPC calls.

Alternatives

Build an MCP server directly with an MCP framework/library in your language/runtime Use a dedicated JSON-RPC server for tool calls with OpenAPI/typed SDKs for better integration Host tools as REST endpoints and adapt the agent layer to call them directly

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for axum-http-mcp-server.

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

Score Monitoring

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

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.