MCAPI.TR Logo

Updates

New features, improvements and fixes shipped to MCAPI.TR.

Latest update:

New feature

Server history and observation reports

Profiles now include 24-hour, 7-day and 30-day observation history.

  • Player graphs, observed peaks, covered intervals and state changes use saved snapshots without triggering new Minecraft probes.
  • Missing intervals stay empty. The online observation ratio is not presented as time-based uptime.
  • GET /api/v1/history/{address} supports period and bedrock options.
New feature

Step-by-step connection diagnostics

Added a tool for DNS, SRV, network connectivity and Minecraft status protocol checks.

  • Java, Bedrock and Legacy status protocols are supported. Checks run only when requested.
  • Private targets are blocked; timeouts are inconclusive. Results are cached and concurrency is bounded.
  • The tool does not test player login, whitelist or authentication. It is also available through GET /api/v1/diagnostics/{address}.
New feature

Integration examples for 20 environments

Examples cover websites, bots, CMS, backend languages, Minecraft plugins and command-line tools.

  • Added HTML/JavaScript, TypeScript, Next.js, React, Vue, Svelte, Python, PHP, WordPress, Java, C#, Go, Rust, NestJS, Discord.js, discord.py, Telegram, Paper/Spigot, Bash and PowerShell examples.
  • Search, category filtering, address customization, copy and file download are included, along with requirements and official documentation links.
New feature

The server catalog now keeps itself up to date

Discovering servers and checking their status no longer depends on a user request.

  • Added page-by-page discovery from external Minecraft server lists. Addresses enter the catalog only after a valid Minecraft protocol response.
  • All saved servers enter a recurring check schedule. Online servers target a 5-minute interval and offline servers a 15-minute interval; queued work continues during busy periods.
  • Results warm the Redis cache. Temporary connection failures retain the last successful data; repeated failures confirm an offline state.
  • Old addresses whose DNS records no longer resolve now also pass through the offline-result and cache pipeline.
Improvement

A broader, fresher selection of trending servers

Discovered servers can rank using observed data before users have queried them.

  • Observed player population now contributes to trend scores alongside user interest and availability signals.
  • Scores recalculate at service startup and every 15 minutes.
  • Automated checks do not count as user queries or artificially increase daily growth or the recent-user-check feed.
Improvement

Server profiles prepared for search engines

Server information is now included in the initial HTML response.

  • Fresh, online servers with high trend scores enter the dynamic sitemap in four languages.
  • Added canonical URLs and indexing directives. Profiles with low scores or without fresh online data are not opened for indexing.
  • These changes help crawlers discover the pages; inclusion and ranking in search results remain search engine decisions.
New feature

Pagination for the server catalog and trends

Retrieve records across multiple pages rather than a single response.

  • GET /api/v1/servers lists previously saved online or stale servers without starting a new network check.
  • Added page to the catalog and GET /api/v1/trends. meta.nextPage identifies the next page and returns null at the end.
  • The catalog allows up to 100 records per page; trends allow up to 50. Cursor support remains available, but page and cursor cannot be combined.
  • A fresh offline latest snapshot excludes a server from the public list. Missing snapshots or snapshots older than 24 hours are reported as stale.
New feature

Check 50 servers in one request

Added POST /api/v1/status/bulk for batch server checks.

  • Submit up to 50 servers per request, with Java, Bedrock or Legacy options for each server.
  • Results preserve input order. One offline server or failed check does not prevent the remaining results from being returned.
  • Repeated checks of the same target reuse a result; concurrent network checks are bounded.
Fix

Fixed daily growth calculations and trend pages

Growth now compares two complete, comparable periods.

  • daily_growth compares user queries in the last complete 24 hours with the preceding 24 hours. The current partial hour is excluded; a missing baseline returns 0.
  • Trend calculations also run at service startup instead of waiting for the first scheduled interval after a restart.
  • Server eligibility is checked before pagination, preventing filtering from producing short pages and inconsistent next-page metadata.

This website uses cookies to provide you with the best experience. We use cookies to analyze site usage and improve our content. Our Cookie Policy for more information.