Home · MCP servers · GitHub release history

GitHub release history MCP server

How often a GitHub project ships releases. Add one address to your AI assistant and it can call the tool below itself, with your FoxAPIs key. It costs the same credits as the REST API, and an answer with no data is not charged.

Server address

https://foxapis.com/mcp/data/release-history

Streamable HTTP, bearer key in the Authorization header. This address carries only the GitHub release history tool; https://foxapis.com/mcp/data carries all of them, and ?source=release-history,github picks several.

What you can ask

Five prompts to give your assistant once the server is added:

  1. How often does vercel/next.js ship a release?
  2. When was the last release of this GitHub repository and what is its typical gap between releases?
  3. Is this open source project still releasing regularly? Check its release cadence.
  4. Compare the release cadence of two GitHub repositories.
  5. How many releases did this project ship in the last 90 days?

The tool your assistant gets

ToolWhat it returnsInputsCredits a call
release_historyA repository's releases, cadence and streaks, read live and kept 6 hours: releases in the last 90 days, typical gap, longest gap and a plain sentence.repo (required)1

Credits come from the same file as the pricing page. Plans and top-ups are on pricing.

Set it up

Use your FoxAPIs key (it starts with fxp_) as the bearer token. Get one free at foxapis.com/trial.

Claude Code

Run in a terminal. Its docs.

claude mcp add --transport http foxapis-data https://foxapis.com/mcp/data/release-history \
  --header "Authorization: Bearer YOUR_KEY"

The Claude Code docs show this form (--transport http, name, URL, --header) for a server that takes a bearer token.

Cursor

.cursor/mcp.json in a project, or ~/.cursor/mcp.json for every project. Its docs.

{
  "mcpServers": {
    "foxapis-data": {
      "url": "https://foxapis.com/mcp/data/release-history",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

Cursor's remote-server example uses a url and a headers object.

VS Code (Copilot)

.mcp.json at the workspace root, or ~/.copilot/mcp-config.json. Its docs.

{
  "mcpServers": {
    "foxapis-data": {
      "type": "http",
      "url": "https://foxapis.com/mcp/data/release-history",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      },
      "tools": [
        "*"
      ]
    }
  }
}

Do not store a real key in a file you share.

Cline

cline_mcp_settings.json (open it from Cline's MCP Servers panel). Its docs.

{
  "mcpServers": {
    "foxapis-data": {
      "type": "streamableHttp",
      "url": "https://foxapis.com/mcp/data/release-history",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Cline's docs say that leaving type out selects the older SSE transport, so keep type.

Zed

settings.json (Zed: open settings). Its docs.

{
  "context_servers": {
    "foxapis-data": {
      "url": "https://foxapis.com/mcp/data/release-history",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

n8n

an MCP Client Tool node in a workflow. Its docs.

Endpoint: https://foxapis.com/mcp/data/release-history
Server transport: HTTP Streamable
Authentication: Header Auth
  Name: Authorization
  Value: Bearer YOUR_KEY

Not run by us: the fields are the ones n8n's MCP Client Tool documents. The server speaks Streamable HTTP.

Claude Desktop and ChatGPT

Not covered here: their custom-connector screens ask for sign-in (OAuth) or no authentication, and this server takes a bearer key in a header, so it works best in the clients above. We have not tested it in either.

A real answer

The release_history tool called once through a real MCP client session on 20 November 2026 with the input {"repo":"vercel/next.js"}. Long text is cut and lists are cut to three items for display; it is not invented.


  

Charged: 1 credit.

Try it free

Runs the release_history call with the sample input below. No key and no sign-up; a few runs a day per visitor.

{
  "repo": "vercel/next.js"
}

Other data-source MCP servers

GitHub · Hacker News · Stack Overflow · Hugging Face · PubMed · bioRxiv · all of them

Free to start: 100 credits, no card. Then from $10. Credits you buy never expire.

Get my free key

The same data over REST: GitHub release history. More: all MCP servers · people and company tools