Foundrynet Geo

io.github.FoundryNetPublished by GitHub account FoundryNetv1.0.1Updated Oct 24, 2026

x402-gated geocoding + distance gateway. Tools: geocode, distance.

VerifiedStreamable HTTPWeb executableLocation & LifestyleFinance

Overview

AI-generated overview

Remote geocoding and distance gateway that also scores facility location risk, billed per call via x402 micropayments in USDC.

What you can do
  • Geocode addresses to coordinates and components, or reverse-geocode coordinates to an address
  • Calculate distance and estimated duration between two locations
  • Score an address for facility risk, returning a risk score, level, factors and recommendation
  • Enrich risk results with live weather alerts and regulatory jurisdiction activity from sibling servers
When to use it
Useful for logistics, delivery or real-estate agents that need frequent, low-cost geocoding and distance lookups, or a quick risk assessment for a facility address.
Requirements
A remote streamable HTTP endpoint; nothing to install locally. No account or API key is required, but each call is paid in USDC on Solana mainnet via x402 unless an fnet_ Forge key is supplied as the api_key argument or an Authorization Bearer header. Network access to the endpoint is needed.
Before you install
Calls cost money: $0.005 per geocode or distance call and $0.02 per facility risk call, paid in USDC on Solana mainnet, so an assistant can spend funds without further confirmation. An fnet_ key passed as api_key or in the Authorization header is a credential. Addresses submitted are sent to the provider and to third-party geocoders and sibling services.

Installation

In SourceWeft

  1. Open Foundrynet Geo in the dashboard and add it to a workspace.
  2. 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.FoundryNet%2Ffoundrynet-geo/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": {
    "foundrynet-geo": {
      "type": "http",
      "url": "https://foundrynet-geo-production.up.railway.app/mcp"
    }
  }
}

README

FoundryNet Geo — Facility Risk Mapper

Facility location risk assessment — score any address for weather threats, regulatory activity, and operational risk factors. Also provides geocoding and distance calculations. One call, one micropayment — no API keys, no accounts.

Part of the FoundryNet Data Network. Pay-per-call in USDC (x402) or bypass with an fnet_ Forge key. Also exposed as an MCP server so agents on Smithery/Glama/Claude can call it directly.

Tools / Endpoints

Tool / RoutePriceDescription
geocode — POST /v1/geocode$0.005Address → {lat, lng, formatted_address, components}, or {lat,lng} → reverse-geocode
distance — POST /v1/distance$0.005{from, to} → {distance_km, duration_estimate}
facility_risk — POST /v1/facility-risk$0.02{address} → {risk_score, risk_level, risk_factors[], coordinates, recommendation} — geocodes the address, then enriches with live weather alerts (and regulatory jurisdiction activity) from sibling FoundryNet servers

Backends: US Census Geocoder (precise for US addresses) + Nominatim / OpenStreetMap (global) — both free and keyless.

MCP

Streamable HTTP endpoint: https://foundrynet-geo-production.up.railway.app/mcp

claude mcp add --transport http foundrynet-geo https://foundrynet-geo-production.up.railway.app/mcp

Tools list without auth (discoverable). Pass an fnet_ key as the api_key argument (or Authorization: Bearer) to bypass payment; otherwise the tool returns an x402 payment_required object.

Payment (x402)

Standard x402 v2 on Solana mainnet USDC. Discovery: GET /x402, GET /.well-known/x402, and a per-route 402 at GET /x402/{route} (with the PAYMENT-REQUIRED header). Validated on 402 Index.

For logistics, delivery, and real-estate agents that need geocoding at high frequency and low cost.

Source: README.md at commit 40df749

Tools

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

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

75% 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
  • License10 pts

    Declare a license in the repository or the registry entry.