BlinkHub Wire

What BlinkHub Wire MCP server does

BlinkHub Wire MCP server gives an MCP-compatible assistant access to government press releases from six markets: the United States (us), Korea (kr), the United Kingdom (gb), the European Union (eu), New Zealand (nz), and Australia (au). Each market has its own language and source coverage. Korean releases are searched with Korean keywords, while the other listed feeds are in English.

The service separates discovery from full-text retrieval. An agent can inspect available markets and search recent releases without consuming the article quota. Search results include the headline, summary, source agency, publication time, and article ID. The agent can then request the full text, original link, and attribution or copyright line for a selected result.

The feeds contain releases from sources such as US federal agencies, Korean central and local government bodies, GOV.UK, the European Commission, the New Zealand Government, and the Australian prime minister's media releases. Some source material is rewritten as news copy, and each returned document includes the attribution information required for that feed.

How it works

BlinkHub Wire MCP server is exposed through Streamable HTTP at https://wire.blinkhub.net/mcp. The client sends the API key in an X-Api-Key header or as a bearer token in the Authorization header. A client can register the endpoint in an mcpServers configuration, or Claude Code can add it with an HTTP transport command.

A typical workflow starts with list_markets, followed by search_articles for one market. The search accepts a keyword query, an optional YYYY-MM-DD start date, and a result limit from 1 to 30. Leaving the query empty returns the latest available articles. Every query word must occur in the headline, summary, or source agency. get_article uses the market and ID returned by search. The first retrieval of a particular article for the key consumes one unit; later reads of that same article are free.

account_status reports the key's plan, monthly allowance, and usage. The free tier includes 100 full articles per month. Higher-volume access is available by contacting BlinkHub.

Setup and configuration

Obtain an account through BlinkHub's publisher registration process, add and verify a publication in the Wire portal, and wait for approval. The API key is then available in the portal and can be rotated there. Store it as a secret rather than placing it directly in prompts or source files.

For a generic MCP configuration, use the hosted URL and pass the key as a header:

{
  "mcpServers": {
    "blinkhub-wire": {
      "type": "http",
      "url": "https://wire.blinkhub.net/mcp",
      "headers": { "X-Api-Key": "YOUR_KEY" }
    }
  }
}

The repository also provides Python and Node.js REST examples, but the MCP endpoint is the relevant interface for an assistant. The repository code is MIT licensed; article usage is governed separately by each document's attribution and usage terms.

Tools and capabilities

• list_markets: Shows the six market codes, languages, available content, and license terms.
• search_articles: Searches recent releases in one market without using quota. It returns metadata and IDs rather than full article bodies.
• get_article: Retrieves one article's full text, source agency, publication time, original link, and required copyright line.
• account_status: Reports the API plan, monthly quota, and amount used.

Search and full retrieval have different billing behavior, so agents can filter results before selecting articles to read. Article availability can also depend on source distribution terms; material that cannot be distributed is excluded.