Frostbyte

io.github.OzorOwnPublished by GitHub account OzorOwnv1.0.0Updated Oct 24, 2026

MCP server giving AI agents access to 40+ APIs: geo, crypto, screenshots, DNS, and more

VerifiedSTDIODesktop onlyWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Frostbyte is a local MCP server that gives an assistant access to 40+ third-party APIs such as geo, crypto, screenshots, and DNS lookups.

What you can do
Frostbyte runs as a local stdio MCP server that exposes a broad set of API-backed utilities to an AI assistant. According to its registry description, it covers more than 40 APIs, including geolocation, cryptocurrency data, screenshots, and DNS lookups. Requests are routed through a Frostbyte gateway rather than called directly. The manifest does not list individual tools, so the exact tool names and parameters are not documented here.
When to use it
Consider it when you want one MCP server that bundles many small utility lookups — location, crypto prices, DNS records, page screenshots — instead of installing a separate server for each. It is a general-purpose convenience layer, not a deep integration with any single service.
Requirements
Runs as a local process on the user's machine, distributed as an OCI image (ghcr.io/ozorown/frostbyte-mcp:latest) over stdio, so a container runtime is needed. Desktop only. Optional secret FROSTBYTE_API_KEY for the gateway; a free tier is auto-created if it is not set. Optional FROSTBYTE_BASE_URL, defaulting to a hosted gateway URL. Network access is required.
Before you install
Requests are routed through a third-party gateway, so the queries and any data you pass may leave your machine and be handled by that operator. The optional FROSTBYTE_API_KEY is a credential; treat it as a secret and avoid committing it. The manifest declares no authentication and does not list tools, so review what each tool actually sends before relying on it for sensitive data.

Installation

In SourceWeft

  1. Open Frostbyte in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.