Execute adsb-flight-tracker-mcp

io.github.EvozimPublished by GitHub account Evozimv2.0.0Updated Oct 24, 2026

Premium agentic endpoint for adsb-flight-tracker-mcp.

VerifiedSSEWeb executableLocation & Lifestyle

Overview

AI-generated overview

A remote MCP endpoint for an ADS-B flight tracker that requires a paid x402 payment signature on each request.

What you can do
Connects an assistant to a hosted ADS-B flight-tracking service over SSE so it can query aircraft and flight data from that endpoint. The manifest lists no individual tools, so the exact queries available are not documented here. Access is gated by a per-request payment signature rather than a conventional API key.
When to use it
Consider it when you want an assistant to pull live ADS-B flight-tracking data from a hosted service and you are prepared to pay per request in USDC on Base Mainnet.
Requirements
A remote SSE endpoint at the provider's host; no local runtime or package is needed. Each request needs a Payment-Signature header containing a Base64-encoded EIP-3009 TransferWithAuthorization signature for x402 V2 settlement on Base Mainnet, costing $0.25 USDC. A wallet able to produce that signature is required.
Before you install
Every request involves a real USDC payment of $0.25 on Base Mainnet, so usage spends money. The Payment-Signature header is a cryptographic authorization tied to your wallet; treat it as a secret and do not share it. The manifest lists no tools, so verify what data the endpoint returns before relying on it.

Installation

In SourceWeft

  1. Open Execute adsb-flight-tracker-mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Evozim%2Fadsb-flight-tracker-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "execute-adsb-flight-tracker": {
      "type": "sse",
      "url": "https://api.m2mcent.com/adsb-flight-tracker-mcp/sse"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.