← frontierterm.com

INDIVIDUAL MCP TOOL

get_alerts

Alerts newest first, each citing the change rows it is a claim about (changes, resolved; missing_change_ids if any did not resolve).

frontierterm.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://frontierterm.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_alerts and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

frontierterm.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.frontier-terminal]
url = "https://frontierterm.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "frontier-terminal": {
      "type": "http",
      "url": "https://frontierterm.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: frontier-terminal
Remote MCP URL: https://frontierterm.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "frontier-terminal": {
      "url": "https://frontierterm.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "frontier-terminal": {
      "type": "http",
      "url": "https://frontierterm.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "frontier-terminal",
  "transport": "streamable-http",
  "url": "https://frontierterm.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • describe — Orientation: the site’s llms.txt — what it tracks, the provenance rule every number obeys, and the pages behind each tool.
  • get_overview — The signal band.
  • get_prices — The API price catalog: one row per SKU key (provider + model + tier) at its newest revision, in USD per million tokens (input_per_mtok, cached_input_per_mtok, output_per_mtok; null = the vendor publishes no figure), plus delta vs.
  • get_hiring — Open roles per lab, counted from the CURRENT job-board set (a role missing from the board is closed), by department.
  • get_alert — One alert by id (ids come from get_alerts, get_overview, the Atom feed or an /alerts/<id> permalink), with every cited change row in full: fields lists every scalar field before and after, unchanged ones included.
  • get_price_history — Every observation of one SKU key, oldest first: points carry kind (baseline = the price as of the source’s first snapshot, added, modified with the changed fields in diff, removed, or current), the three USD-per-million-token figures, and the fetch each was read from.
  • get_hiring_history — Open roles per lab and department, per UTC day (dates, total, departments[].series), RECONSTRUCTED by undoing the change log backwards from the current job-board set — not a series of daily snapshots.
  • get_releases — Every SKU first listed on a vendor page after that source’s baseline, newest first, with the price printed beside it when it was first seen (first_seen_at is the detection, not the vendor’s launch date) and also_listed_by for keys two pages carry.