# match_info

Get the basics for a match in ONE call: the score, whether it's live, when it kicks off, and who's favored. No betting knowledge needed — this answers "who's winning?", "what's the score?", "what time does Brazil play (in my timezone)?", "who's the favorite?". Returns the live score + match clock, the status, the kickoff time (in timezone if you pass an IANA name like "America/New_York"), the favored team with a plain win probability (de-vigged from the 1x2 line), and a ready-to-read summary you can quote directly. Args: query: natural-language fixture or team, e.g. "Brazil vs Argentina" or just "Brazil". timezone: optional IANA timezone (e.g. "America/New_York", "Asia/Shanghai") for the kickoff time; default UTC. sport: optional filter — "football" or "basketball". date: optional UTC date "YYYY-MM-DD" to disambiguate same-name fixtures. On an ambiguous query, status is "ambiguous" and ask_user carries a prompt — do not guess. favorite is best-effort (null when no 1x2 is on file for the fixture).

Agent View of the PolicyLayer registry record for `match_info`. HTML page: https://policylayer.com/tools/dev-infersports-infersports/match-info

## Facts

- Tool: `match_info`
- Server: Infersports (`https://api.infersports.dev/mcp`) — https://policylayer.com/tools/dev-infersports-infersports.md
- Homepage: https://github.com/https://api.infersports.dev/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 4 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `date` | object | no |  |
| `query` | string | yes |  |
| `sport` | object | no |  |
| `timezone` | object | no |  |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "match_info",
    "arguments": {
      "query": "<query>"
    }
  }
}
```

## Why match_info is rated Low

This tool only retrieves and displays factual match data (score, time, status, favored team probability). It produces no side effects, does not modify data, does not execute code or external operations, and does not involve financial transactions. It is a pure read operation within a read-only server context.

From the tool's own definition: "Tool description explicitly states 'Read-only' server; tool retrieves match information: 'Get the basics for a match in ONE call: the score, whether it's live, when it kicks off, and who's favored' — all query/retrieval operations with 'no betting knowledge…"

## Use case

AI agents call match_info to retrieve information from Infersports without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Infersports:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "match_info": {}
  }
}
```

## Other tools on Infersports (16)

- `compare_lines` — Read — https://policylayer.com/tools/dev-infersports-infersports/compare-lines.md
- `compare_prob` — Read — https://policylayer.com/tools/dev-infersports-infersports/compare-prob.md
- `explain_handicap` — Read — https://policylayer.com/tools/dev-infersports-infersports/explain-handicap.md
- `find_arbitrage` — Read — https://policylayer.com/tools/dev-infersports-infersports/find-arbitrage.md
- `find_match` — Read — https://policylayer.com/tools/dev-infersports-infersports/find-match.md
- `find_value` — Read — https://policylayer.com/tools/dev-infersports-infersports/find-value.md
- `get_match_odds` — Read — https://policylayer.com/tools/dev-infersports-infersports/get-match-odds.md
- `get_opening_line` — Read — https://policylayer.com/tools/dev-infersports-infersports/get-opening-line.md
- `get_result` — Read — https://policylayer.com/tools/dev-infersports-infersports/get-result.md
- `get_sharp_line` — Read — https://policylayer.com/tools/dev-infersports-infersports/get-sharp-line.md
- `list_bookmakers` — Read — https://policylayer.com/tools/dev-infersports-infersports/list-bookmakers.md
- `list_events` — Read — https://policylayer.com/tools/dev-infersports-infersports/list-events.md
- `list_results` — Read — https://policylayer.com/tools/dev-infersports-infersports/list-results.md
- `list_today_matches` — Read — https://policylayer.com/tools/dev-infersports-infersports/list-today-matches.md
- `scan_slate` — Read — https://policylayer.com/tools/dev-infersports-infersports/scan-slate.md
- `score_prob` — Read — https://policylayer.com/tools/dev-infersports-infersports/score-prob.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-infersports-infersports · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-infersports-infersports