Skip to main content
Glama
ktmcp-cli

@ktmcp/betfair

by ktmcp-cli
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

@ktmcp/betfair

MCP server for Betfair: Exchange Streaming API

Installation

npm install -g @ktmcp/betfair

Related MCP server: tastytrade-mcp

Usage

Add to your MCP settings:

{
  "mcpServers": {
    "betfair": {
      "command": "mcp-betfair"
    }
  }
}

Description

API to receive streamed updates. This is an ssl socket connection of CRLF delimited json messages (see RequestMessage & ResponseMessage)

Category

api

Support KTMCP

If you find this CLI useful, we'd greatly appreciate your support! Share your experience on:

  • Reddit

  • Twitter/X

  • Hacker News

Incentive: Users who can demonstrate that their support/advocacy helped advance KTMCP will have their feature requests and issues prioritized.

Just be mindful - these are real accounts and real communities. Authentic mentions and genuine recommendations go a long way!

Support This Project

If you find this CLI useful, we'd appreciate support across Reddit, Twitter, Hacker News, or Moltbook. Please be mindful - these are real community accounts. Contributors who can demonstrate their support helped advance KTMCP will have their PRs and feature requests prioritized.

Available Tools

1 tool
post__requestD

This is a socket protocol delimited by CRLF (not http)

ParametersJSON Schema
NameRequiredDescriptionDefault
bodyNoRequest body

TDQS

D1.5/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries full responsibility for behavioral disclosure. It only states the protocol delimiter, omitting details about side effects, return values, error behavior, or any operational characteristics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but it is under-specified rather than efficiently informative. It conveys one fact but lacks essential purpose and usage details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (1 parameter, no output schema), the description is severely incomplete. It fails to explain what the tool does, expected body structure, or response behavior, leaving the agent without essential context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a single 'body' parameter described as 'Request body'. The description adds no additional semantic meaning, but the high schema coverage yields a baseline of 3. The CRLF note hints at body format but is vague.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does not state what the tool does; it only describes the protocol as CRLF-delimited socket (not HTTP). There is no verb or resource indicating the action, making the purpose vague and misleading.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool or how it differs from alternatives. The mention of 'socket protocol' implies low-level network use, but no explicit context or exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedpost__request
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.9/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of confusing it with another tool. The tool set has zero ambiguity in terms of tool selection.

Naming Consistency4/5

With a single tool, naming consistency is trivially maintained. However, the name 'post__request' is unconventional and not a clear verb_noun pattern, making it somewhat unpredictable.

Tool Count1/5

A single trivial tool for what appears to be a Betfair server is an extreme mismatch. The tool does not cover the expected scope of a betting exchange API.

Completeness1/5

The server provides no apparent functionality for Betfair operations such as market data, betting, or account management. The one tool is a low-level socket request, leaving the domain severely incomplete.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • tastytrade-mcp

    bholzer
    F
    license
    A
    quality
    D
    maintenance
    MCP server for the tastytrade brokerage API, providing tools for account management, market data, and order execution.
    18
    -

  • oanda-mcp

    florinel-chis
    A
    license
    A
    quality
    B
    maintenance
    MCP server for the Oanda v20 REST API enabling forex/CFD trading account management, market data retrieval, and order/trade operations with a read-first design and practice environment by default.
    22
    1
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ktmcp-cli/betfair'

If you have feedback or need assistance with the MCP directory API, please join our Discord server