NeuronForm 3D map models
REMOTE · NEURONFORM.COM
Design 3D-printable multi-colour map models from OpenStreetMap data, render them, and share them.
Available components
Last scanned (14 hours ago)
Scores higher than 67% 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 Security80
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability48
- 11% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1720 tokens (~61/item across 28 items; 10 tools + 18 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +1
- 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 21 Nov 2026 · Probed https://neuronform.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=neuronform.com | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e06f7883967ed23a0e4684fdd7d3caf0 |
| SANs: neuronform.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of neuronform.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| neuronform.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; connect-src 'self' https://challenges.cloudflare.com https://tiles.openfreemap.org; worker-src 'self' blob:; frame-src https://challenges.cloudflare.com; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), autoplay=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://neuronform.com/mcp | Verified | 200 | |
| http (plaintext) | http://neuronform.com/mcp | HTTPS enforced | 301 | https://neuronform.com/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 →
create_design Create design from brief ~96
Compiles a short brief into a complete design with the configurator defaults; the centre given by place or lat and lon is the centre of tile 0. Invalid values fall back to their defaults with a notice naming the brief field. Change the result with edit_design.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | object | yes | Design brief; place or lat and lon is required. |
| lang | string | – | Language of the summaries and error messages; default en. |
No output schema declared.
No examples provided.
edit_design Edit design ~287
Changes a design and returns the complete changed design, validated against the rules and the limits of anonymous use. changes takes brief fields (an absent field keeps the design: width, rotation, model_width, exaggeration, relief, frame, colors, label, tiles, shape, or place or lat and lon to move the centre of tile 0); patch takes JSON Patch operations for every other field, applied after changes. The service stores no design: send the complete design every time and continue with the returned one.
| Name | Type | Req | Description |
|---|---|---|---|
| changes | object | – | Brief fields to change. tiles arranges a new compact layout, label replaces the text of the first edge label or adds one, colors without template keeps the other colours. |
| design | object | yes | Complete design (MapRequest) as create_design returns it; the full JSON schema is the resource neuronform://schema/design and get_design_guide explains every section. |
| lang | string | – | Language of the summaries and error messages; default en. |
| patch | array | – | JSON Patch operations (RFC 6902 add, replace, remove) on the design JSON, applied after changes, such as {"op": "replace", "path": "/terrain/vertical_exaggeration", "value": 2.5} or {"op": "add", "pa… |
No output schema declared.
No examples provided.
edit_tiles Add or remove tiles ~114
Adds a tile at, or removes the tile at, a compass side of a tile and returns the updated design.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| design | object | yes | Complete design (MapRequest) as create_design returns it; the full JSON schema is the resource neuronform://schema/design and get_design_guide explains every section. |
| direction | string | yes | – |
| lang | string | – | Language of the summaries and error messages; default en. |
| tile | integer | – | Reference tile; default 0. |
No output schema declared.
No examples provided.
find_map_elements Find map elements ~187
Lists roads and paths, buildings, areas, or ground regions of the design with a ready-to-insert request fragment and its target path; a building also carries the placement of a custom house that replaces it.
| Name | Type | Req | Description |
|---|---|---|---|
| class | string | – | Feature class such as highway.residential, or a prefix such as highway. |
| design | object | yes | Complete design (MapRequest) as create_design returns it; the full JSON schema is the resource neuronform://schema/design and get_design_guide explains every section. |
| kind | string | yes | – |
| lang | string | – | Language of the summaries and error messages; default en. |
| limit | integer | – | Number of elements; default 10. |
| name | string | – | Text the element name contains. |
| near | object | – | Orders the elements by distance from this point. |
| tile | integer | – | Searches only this tile. |
No output schema declared.
No examples provided.
get_design_guide Get design guide ~57
Returns the guide of one topic of the design JSON with the JSON schema of its fields.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the summaries and error messages; default en. |
| topic | string | – | Guide topic; default overview. |
No output schema declared.
No examples provided.
list_templates List templates ~61
Lists published gallery templates with slug, title, and image URL; with a slug it returns the design of that template.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the summaries and error messages; default en. |
| slug | string | – | Template whose design is returned. |
No output schema declared.
No examples provided.
render_design Render design ~284
Renders a design as an image, returns its summary, and opens the interactive 3D viewer where the host supports it. The default overview shows four 3D views from the north, east, south, and west beside the top view with north up and a scale bar, so proportions and relief read from every side; view top or oblique with a direction gives one larger view, resolution high doubles the size. A repeated render of the same design and options is answered from the cache.
| Name | Type | Req | Description |
|---|---|---|---|
| design | object | yes | Complete design (MapRequest) as create_design returns it; the full JSON schema is the resource neuronform://schema/design and get_design_guide explains every section. |
| direction | string | – | Compass direction the camera of view oblique looks from, 35° above the horizon; default sw. Only with view oblique. |
| lang | string | – | Language of the summaries and error messages; default en. |
| resolution | string | – | standard (default) or high, which doubles the width and the height of the image. |
| view | string | – | Image layout: overview (default, 1600 × 800 px: four 3D views and the top view), top (800 × 800 px top view with north up and scale bar), or oblique (800 × 800 px 3D view from direction). |
No output schema declared.
No examples provided.
search_places Search places ~85
Searches places, streets, and house numbers in the place index of NeuronForm and returns candidates with name, lat, lon, and kind.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the summaries and error messages; default en. |
| limit | integer | – | Number of candidates; default 5. |
| query | string | yes | Place or address, 2 to 200 characters. |
No output schema declared.
No examples provided.
share_design Share design link ~91
Stores the design and returns a link, valid for 90 days, that opens exactly this design in the NeuronForm configurator.
| Name | Type | Req | Description |
|---|---|---|---|
| design | object | yes | Complete design (MapRequest) as create_design returns it; the full JSON schema is the resource neuronform://schema/design and get_design_guide explains every section. |
| lang | string | – | Language of the summaries and error messages; default en. |
No output schema declared.
No examples provided.
validate_design Validate design ~86
Checks a design against the request rules, the limits of anonymous use, and the restricted areas without generating it.
| Name | Type | Req | Description |
|---|---|---|---|
| design | object | yes | Complete design (MapRequest) as create_design returns it; the full JSON schema is the resource neuronform://schema/design and get_design_guide explains every section. |
| lang | string | – | Language of the summaries and error messages; default en. |
No output schema declared.
No examples provided.
How do I install the NeuronForm 3D map models MCP server?
NeuronForm 3D map models is a hosted endpoint at https://neuronform.com/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 · neuronform.com
claude mcp add --transport http com-neuronform-mcp 'https://neuronform.com/mcp'
What is the NeuronForm 3D map models MCP server?
NeuronForm 3D map models is an MCP server listed in the public MCP registry as com.neuronform/mcp. Design 3D-printable multi-colour map models from OpenStreetMap data, render them, and share them. This page covers its hosted endpoint (https://neuronform.com/mcp).
Is the NeuronForm 3D map models MCP server safe to use?
NeuronForm 3D map models scores 77 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 NeuronForm 3D map models MCP server expose?
NeuronForm 3D map models exposes 10 tools: search_places, create_design, edit_design, get_design_guide, find_map_elements, and 5 more. Their descriptions and schemas cost roughly 1,348 tokens of context every time the server is loaded.
Does the NeuronForm 3D map models MCP server require authentication?
No. We connected to NeuronForm 3D map models without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the NeuronForm 3D map models MCP server still maintained?
NeuronForm 3D map models 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 NeuronForm 3D map models MCP server?
VerifyMCP ran 14 checks on NeuronForm 3D map models, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.