MCP Guide

Purpose

This guide explains how to use Norynta MCP servers safely and effectively for tool-using AI assistants and agent runtimes.

Audience

• AI assistant operators integrating MCP tools
• engineering teams evaluating tool-based workflows
• operators wiring Norynta MCP into local or hosted assistants

MCP server map

Norynta provides three MCP servers:

1. Public MCP (npm run mcp-public)

   • best for discovery, diagnostics, and read/simulate-first market intelligence
   • tools: market_search, events_top, events_snapshots, agent_access, validate_trade, estimate_impact, developer_diagnostics, explain_failed_request

2. Trading MCP (npm run mcp-trading)

   • for first-trade checks and signed execution requests
   • tools: orders_place, orders_cancel, orders_my
   • expects caller-supplied wallet-signature headers for write paths
   • requires caller-supplied idempotency keys for mutating tools

3. Ops MCP (npm run mcp-ops)

   • for local environment and MCP wiring checks
   • tools: ops_get_env_status, ops_get_mcp_status

Quick start

1. Ensure app/API is available locally or remotely.
2. Start the desired MCP server (for example, public):

npm run mcp-public

3. Validate server registration and tool listing:

npm run mcp:smoke

4. Use the .mcp.json template for client configuration.

Server selection guidance

• Use public MCP for read-only bots and assistant discovery tools.
• Use trading MCP only for flows that already implement signing, idempotency, retries, and policy-aware write controls.
• Use ops MCP for operator workflows and local validation.

Safety boundaries

• Treat MCP tools as convenience wrappers over HTTP contracts, not a replacement for execution guardrails.
• Keep trading credentials scoped and rotated.
• Apply deterministic IDs (clientOrderId / idempotency-key) on writes.
• Simulate before placing aggressive flow.
• Reconcile stream gaps with periodic snapshots.
• Prefer least-privilege keys and endpoint allowlists where available.

Environment and auth notes

• MCP requests use the same backend base URL resolution as runtime scripts.
• Trading tools require valid wallet signature headers for authenticated writes.
• Some discovery surfaces may return richer metadata when API keys are supplied.

Related docs

• docs/public/INTEGRATION_START_HERE.md
• docs/public/SDK_AND_EXAMPLES.md
• docs/AGENT_INTEGRATION.md
• .mcp.json