Skip to main content
Glama
meridian-edge-mcp

meridian-edge-mcp

by tmbot12

MCP Registry

Get it on MCP Marketplace

The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.

πŸ“€ Publish my MCP server | ⚑️ Live API docs | πŸ‘€ Ecosystem vision | πŸ“– Full documentation

Development Status

2025-10-24 update: The Registry API has entered an API freeze (v0.1) πŸŽ‰. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patienceβ€”your involvement has been key to getting us here!

2025-09-08 update: The registry has launched in preview πŸŽ‰ (announcement blog post). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in GitHub discussions or in the #registry-dev Discord (joining details here).

Current key maintainers:

Related MCP server: telekash-mcp-server

Contributing

We use multiple channels for collaboration - see modelcontextprotocol.io/community/communication.

Often (but not always) ideas flow through this pipeline:

  • Discord - Real-time community discussions

  • Discussions - Propose and discuss product/technical requirements

  • Issues - Track well-scoped technical work

  • Pull Requests - Contribute work towards issues

Quick start:

Pre-requisites

Running the server

# Start full development environment
make dev-compose

This starts the registry at localhost:8080 with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.

Note: The registry uses ko to build container images. The make dev-compose command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.

By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with MCP_REGISTRY_SEED_FROM=data/seed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose.

The setup can be configured with environment variables in docker-compose.yml - see .env.example for a reference.

Pre-built Docker images are automatically published to GitHub Container Registry:

# Run latest stable release
docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:latest

# Run latest from main branch (continuous deployment)
docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main

# Run specific release version
docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:v1.0.0

# Run development build from main branch
docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main-20250906-abc123d

Available tags:

  • Releases: latest, v1.0.0, v1.1.0, etc.

  • Continuous: main (latest main branch build)

  • Development: main-<date>-<sha> (specific commit builds)

Publishing a server

To publish a server, we've built a simple CLI. You can use it with:

# Build the latest CLI
make publisher

# Use it!
./bin/mcp-publisher --help

See the publisher guide for more details.

Other commands

# Run lint, unit tests and integration tests
make check

There are also a few more helpful commands for development. Run make help to learn more, or look in Makefile.

Architecture

Project Structure

β”œβ”€β”€ cmd/                     # Application entry points
β”‚   └── publisher/           # Server publishing tool
β”œβ”€β”€ data/                    # Seed data
β”œβ”€β”€ deploy/                  # Deployment configuration (Pulumi)
β”œβ”€β”€ docs/                    # Documentation
β”œβ”€β”€ internal/                # Private application code
β”‚   β”œβ”€β”€ api/                 # HTTP handlers and routing
β”‚   β”œβ”€β”€ auth/                # Authentication (GitHub OAuth, JWT, namespace blocking)
β”‚   β”œβ”€β”€ config/              # Configuration management
β”‚   β”œβ”€β”€ database/            # Data persistence (PostgreSQL)
β”‚   β”œβ”€β”€ service/             # Business logic
β”‚   β”œβ”€β”€ telemetry/           # Metrics and monitoring
β”‚   └── validators/          # Input validation
β”œβ”€β”€ pkg/                     # Public packages
β”‚   β”œβ”€β”€ api/                 # API types and structures
β”‚   β”‚   └── v0/              # Version 0 API types
β”‚   └── model/               # Data models for server.json
β”œβ”€β”€ scripts/                 # Development and testing scripts
β”œβ”€β”€ tests/                   # Integration tests
└── tools/                   # CLI tools and utilities
    └── validate-*.sh        # Schema validation tools

Authentication

Publishing supports multiple authentication methods:

  • GitHub OAuth - For publishing by logging into GitHub

  • GitHub OIDC - For publishing from GitHub Actions

  • DNS verification - For proving ownership of a domain and its subdomains

  • HTTP verification - For proving ownership of a domain

The registry validates namespace ownership when publishing. E.g. to publish...:

  • io.github.domdomegg/my-cool-mcp you must login to GitHub as domdomegg, or be in a GitHub Action on domdomegg's repos

  • me.adamjones/my-cool-mcp you must prove ownership of adamjones.me via DNS or HTTP challenge

Community Projects

Check out community projects to explore notable registry-related work created by the community.

More documentation

See the documentation for more details if your question has not been answered here!

Available Tools

5 tools
get_consensusA

Get real-time prediction market consensus probabilities.

Returns aggregated consensus from multiple regulated prediction markets. Each event shows the collective probability, trend direction, and how much markets agree (spread).

Args: sport: Filter by sport β€” NBA, NFL, MLB, NHL, MLS, POLITICS, or omit for all active events. limit: Number of events to return (1–20, default 10).

Returns: Formatted consensus data with probabilities, trends, and confidence.

Inputs: sport, limit. Returns: result

get_marketsA

Get active prediction markets currently being tracked.

Shows markets that are open and being monitored for consensus. Use this to see what events are currently available before querying consensus.

Args: sport: Filter by sport β€” NBA, NFL, MLB, NHL, MLS, POLITICS, or omit. limit: Number of markets to return (1–20, default 10).

Returns: Formatted list of active markets with status and sport.

Inputs: sport, limit. Returns: result

get_opportunitiesA

Get events where prediction markets show notable divergence.

Divergence opportunities are events where regulated prediction markets disagree significantly. Higher scores indicate greater disagreement. This may surface events where information is still being incorporated.

Args: min_score: Minimum opportunity score to include (default 5.0). sport: Filter by sport β€” NBA, NFL, MLB, NHL, MLS, POLITICS, or omit. limit: Number of opportunities to return (1–20, default 10).

Returns: Formatted list of divergence opportunities ranked by score.

Inputs: min_score, sport, limit. Returns: result

get_settlementsA

Get recently settled prediction market events with verified outcomes.

Shows events that have concluded, with verified outcome data. Useful for checking how recent consensus predictions compared to actual results.

Args: limit: Number of settled events to return (1–10, default 5).

Returns: Formatted settlement history with outcomes and verification status.

Inputs: limit. Returns: result

get_signalsA

Get recent market signals showing direction of price moves.

Signals indicate notable directional moves in prediction market consensus. Each signal shows whether the market shifted toward YES or NO, and the current status of the market.

Args: limit: Number of signals to return (1–10, default 5).

Returns: Formatted recent signals with direction and event details.

Inputs: limit. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_consensus retrieves aggregated probabilities, get_markets lists available markets, get_opportunities finds divergence events, get_settlements shows concluded outcomes, and get_signals tracks directional moves. There is no overlap in functionality, and the descriptions make each tool's unique role immediately apparent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with 'get_' as the prefix (e.g., get_consensus, get_markets, get_opportunities). This uniformity makes the tool set predictable and easy for an agent to navigate without confusion.

    Tool Count5/5

    With 5 tools, this server is well-scoped for its domain of prediction market data. Each tool serves a specific, non-redundant function, covering real-time consensus, active markets, divergence opportunities, settlements, and signals, which aligns with typical data retrieval needs in this context.

    Completeness4/5

    The tool set provides comprehensive coverage for querying prediction market data, including active, settled, and divergent events, as well as signals. A minor gap is the lack of tools for creating or interacting with markets (e.g., placing bets or managing accounts), but this is reasonable for a read-only data server focused on consensus and analysis.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Aggregates prediction market data from 5 major platforms (Manifold, Polymarket, Metaculus, PredictIt, Kalshi), enabling users to search markets, compare odds across platforms, detect arbitrage opportunities, and track predictions through natural language.
      8
      5
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Prediction market probability oracle for AI agents. 26 tools across 500+ live markets from Kalshi and Polymarket. Cross-source arbitrage detection, structured TPF signals, Kelly Criterion sizing, agent performance tracking, and webhook alerts.
      9
      83 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides search, trending, odds, arbitrage, and category browsing for prediction markets (Polymarket & Kalshi) via the Model Context Protocol, enabling AI agents to access live market data without API keys.
      5
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time access to Polymarket prediction market data, enabling search, browsing, and analysis of prediction markets through natural language.
      32 npm
      MIT