io.github.FoundryNet/foundrynet-geo
REMOTE · FOUNDRYNET-GEO-PRODUCTION.UP.RAILWAY.APP · SCANNED AUG 17
x402-gated geocoding + distance gateway. Tools: geocode, distance.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.FoundryNet/foundrynet-geo MCP server?
io.github.FoundryNet/foundrynet-geo is a hosted endpoint at https://foundrynet-geo-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · foundrynet-geo-production.up.railway.app
claude mcp add --transport http foundrynet-foundrynet-geo 'https://foundrynet-geo-production.up.railway.app/mcp'
{
"mcpServers": {
"foundrynet-foundrynet-geo": {
"url": "https://foundrynet-geo-production.up.railway.app/mcp"
}
}
} {
"servers": {
"foundrynet-foundrynet-geo": {
"type": "http",
"url": "https://foundrynet-geo-production.up.railway.app/mcp"
}
}
} [mcp_servers.foundrynet-foundrynet-geo] url = "https://foundrynet-geo-production.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"foundrynet-foundrynet-geo": {
"type": "remote",
"url": "https://foundrynet-geo-production.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add foundrynet-foundrynet-geo --url 'https://foundrynet-geo-production.up.railway.app/mcp' --transport streamable-http
mcp_servers:
foundrynet-foundrynet-geo:
url: "https://foundrynet-geo-production.up.railway.app/mcp" {
"McpServers": {
"foundrynet-foundrynet-geo": {
"Transport": "http",
"Url": "https://foundrynet-geo-production.up.railway.app/mcp"
}
}
} assistant mcp add foundrynet-foundrynet-geo -t streamable-http -u 'https://foundrynet-geo-production.up.railway.app/mcp'
{
"mcpServers": {
"foundrynet-foundrynet-geo": {
"type": "http",
"url": "https://foundrynet-geo-production.up.railway.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 9 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 7 Aug 26 0
- HSTS header: unverified → fail ▼ security
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Aug 2026 · Probed https://foundrynet-geo-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of foundrynet-geo-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 502 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://foundrynet-geo-production.up.railway.app/mcp | HTTP error | 502 | |
| http (plaintext) | http://foundrynet-geo-production.up.railway.app/mcp | HTTPS enforced | 301 | https://foundrynet-geo-production.up.railway.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
distance ~41
Distance + duration estimate between two places
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | – |
| from | string | yes | origin address |
| to | string | yes | destination address |
No output schema declared.
No examples provided.
facility_risk ~45
Facility location risk profile (weather threats + regulatory activity) for any address
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | facility / site address to assess |
| api_key | string | – | – |
No output schema declared.
No examples provided.
geocode ~54
Geocode an address ↔ lat/lng (Census + Nominatim)
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| api_key | string | – | – |
| lat | number | – | – |
| lng | number | – | – |
No output schema declared.
No examples provided.
What is the io.github.FoundryNet/foundrynet-geo MCP server?
io.github.FoundryNet/foundrynet-geo is an MCP server listed in the public MCP registry as io.github.FoundryNet/foundrynet-geo. x402-gated geocoding + distance gateway. Tools: geocode, distance. This page covers its hosted endpoint (https://foundrynet-geo-production.up.railway.app/mcp).
Is the io.github.FoundryNet/foundrynet-geo MCP server safe to use?
io.github.FoundryNet/foundrynet-geo scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.FoundryNet/foundrynet-geo MCP server expose?
io.github.FoundryNet/foundrynet-geo exposes 3 tools: geocode, distance, facility_risk. Their descriptions and schemas cost roughly 140 tokens of context every time the server is loaded.
Does the io.github.FoundryNet/foundrynet-geo MCP server require authentication?
No. We connected to io.github.FoundryNet/foundrynet-geo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.FoundryNet/foundrynet-geo MCP server still maintained?
io.github.FoundryNet/foundrynet-geo has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 29 July 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.