Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS
REMOTE · PINLOFT.CYBERMAX-TOOLS.WORKERS.DEV
Pinloft: US address to lat/lon, county, FIPS; reverse geocoding. Free, no key.
Available components
Last scanned (21 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 310 tokens (~155/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 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
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 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
- 27 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Sept 26 0
First indexed and scored.
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 21 Nov 2026 · Probed https://pinloft.cybermax-tools.workers.dev/mcp?via=mcp-registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cybermax-tools.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6c35d7b80a04e107b91b8db5035185f9f95 |
| SANs: *.cybermax-tools.workers.dev, cybermax-tools.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 pinloft.cybermax-tools.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | 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 | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pinloft.cybermax-tools.workers.dev/mcp?via=mcp-registry | Verified | 200 | |
| http (plaintext) | http://pinloft.cybermax-tools.workers.dev/mcp?via=mcp-registry | Served over HTTP | 200 |
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 →
geocode_address Address to latitude/longitude (+ US county and FIPS) ~163
Convert up to 5 street addresses to latitude/longitude with a cleaned, matched address and match confidence. US addresses also get state, county, tract, block group and block FIPS codes (US Census geocoder); include_districts adds congressional and state legislative districts, city, school district and metro area. Worldwide addresses use OpenStreetMap.
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | Addresses, one per item, e.g. "1600 Pennsylvania Ave NW, Washington, DC 20500" or "10 Downing St, London". Up to 5. |
| country | string | – | "auto" (default), "US", or ISO-2 codes for non-US lookups |
| include_districts | boolean | – | Add districts for US matches |
No output schema declared.
No examples provided.
reverse_geocode Coordinates to street address (+ US FIPS and districts) ~80
Convert up to 5 latitude/longitude points to the nearest street address (OpenStreetMap), and for US points add state/county/tract/block FIPS codes and congressional/state districts from the US Census geocoder.
| Name | Type | Req | Description |
|---|---|---|---|
| coordinates | array | yes | "latitude,longitude" strings, e.g. "40.7484,-73.9857" |
No output schema declared.
No examples provided.
How do I install the Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS MCP server?
Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS is a hosted endpoint at https://pinloft.cybermax-tools.workers.dev/mcp?via=mcp-registry, 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 · pinloft.cybermax-tools.workers.dev
claude mcp add --transport http cybermax-tools-batch-geocoder 'https://pinloft.cybermax-tools.workers.dev/mcp?via=mcp-registry'
What is the Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS MCP server?
Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS is an MCP server listed in the public MCP registry as io.github.CyberMax-tools/batch-geocoder. Pinloft: US address to lat/lon, county, FIPS; reverse geocoding. Free, no key. This page covers its hosted endpoint (https://pinloft.cybermax-tools.workers.dev/mcp?via=mcp-registry).
Is the Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS MCP server safe to use?
Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS scores 82 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 Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS MCP server expose?
Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS exposes 2 tools: geocode_address, reverse_geocode. Their descriptions and schemas cost roughly 243 tokens of context every time the server is loaded.
Does the Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS MCP server require authentication?
No. We connected to Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS MCP server still maintained?
Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS MCP server?
VerifyMCP ran 13 checks on Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.