go_mcp_server_moex

go_mcp_server_moex exposes selected MOEX ISS endpoints via an MCP server (mcp-go). It can run over multiple transports (stdio, HTTP, SSE) and provides MCP tools that map to MOEX endpoints for engines/markets/boards/securities and security history.

Evaluated Apr 04, 2026 (16d ago)

Repo ↗ API Gateway mcp mcp-server go moex market-data sse http stdio

⚙ 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

The README documents transport options and request header overrides but does not describe authentication/authorization, TLS requirements, or rate limiting for the MCP endpoints. If exposed beyond a trusted network, the lack of described auth is a major risk. Secret handling and dependency security posture are not evidenced in the provided content.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want a lightweight MCP wrapper around MOEX ISS that your own trusted infrastructure can run (local or internal network), optionally over HTTP/SSE for agent connectivity.

Avoid When

When you need fine-grained access control, documented rate limits, or robust documented error/retry semantics for the MCP layer.

Use Cases

• Give an agent a tool-based interface to query MOEX ISS reference data (engines, markets, boards, securities)
• Retrieve market/security history for downstream analytics or reporting
• Integrate MOEX data access into agent workflows using MCP

Not For

• Production deployments that require strong authentication/authorization for the MCP surface
• Use cases needing guaranteed SLAs, documented uptime, or explicit reliability guarantees from this project
• Clients that require a public OpenAPI/SDK for the MCP interface (none is described)

Interface

REST API

Yes

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

OAuth: No Scopes: No

No authentication mechanism is described for the MCP server. This suggests access control may be absent or handled externally (e.g., by a reverse proxy), but that is not documented.

Pricing

Free tier: No

Requires CC: No

No pricing information provided (repo appears to be a self-hosted/open-source project).

Agent Metadata

Pagination

first/limit-based for list_securities; history endpoint mentions limit/start; no general cursor guidance described

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Uses ISS parameters where the README notes some ISS pagination params are not documented; use first for list_securities
⚠ For stdio transport, defaults are controlled via environment variables (MOEX_LANG, MOEX_BASE_URL); for HTTP/SSE, overrides are via request headers (X-MOEX-LANG, X-MOEX-BASE-URL)
⚠ HTTP pathing differs by transport: /mcp for HTTP; SSE publishes /sse and /message for sending requests

Alternatives

Call MOEX ISS directly from your application using HTTP clients Use an existing MOEX API wrapper (if available) and expose your own MCP tools Build a custom MCP server over the MOEX REST API using your preferred framework

Full Evaluation Report

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

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.