Analog Mcp

io.github.dhanawayPublished by GitHub account dhanawayv1.0.6Updated Oct 24, 2026

Query real-time US data and AI-analyzed attributes across the country.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

A remote MCP server that lets an assistant query real-time US data and AI-analyzed attributes across the country through the Analog API.

What you can do
Query real-time US data through the Analog API, as described in the registry entry. Retrieve AI-analyzed attributes for locations across the country. No tool list is published, so the exact operations available are not documented here.
When to use it
Worth considering when an assistant needs live US data or AI-derived attributes about places in the United States, and you already have or plan to get an Analog API key.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. An Analog API key is required and sent in the x-api-key header; keys are issued from the provider's dashboard. Network access to the endpoint is required.
Before you install
The server requires an API key sent as the x-api-key header, so treat it as a secret and check how the client stores it. The provider may meter or bill API usage; confirm pricing before relying on it. Queries are sent to a third-party service.

Installation

In SourceWeft

  1. Open Analog Mcp in the dashboard and add it to a workspace.
  2. Connect x-api-key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. 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.dhanaway%2Fanalog-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": {
    "analog": {
      "type": "http",
      "url": "https://yaewurxvufigjntzdruf.supabase.co/functions/v1/analog-mcp",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.6LatestSep 16, 2026

Score

35% 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

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

  • Auth declaredRequired10 pts
  • 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.