Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
PinSharing Maps is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Geocoding, static maps and privacy-safe area maps from OpenStreetMap data. Hard caps, no overage.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http pinsharing-maps-mcp https://api.pinsharing.com/v1/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'
# 2 — ask your agent for something these tools do
# geocode, reverse_geocode, school_lookup and 3 more
It needs AUTHORIZATION (Bearer followed by your PinSharing API key (ps_…). Free keys: https://pinsharing.com/dashboard): this sends it in the Authorization header from your environment, so export it first — its endpoint answers 401 without it.
PinSharing Maps costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Claude Code reads AUTHORIZATION (Bearer followed by your PinSharing API key (ps_…). Free keys: https://pinsharing.com/dashboard) from your environment each time it connects and sends it in the Authorization header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx AUTHORIZATION … and open a new terminal (Windows).
claude mcp add --scope user --transport http pinsharing-maps-mcp https://api.pinsharing.com/v1/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
It reaches a system of yours, so it needs your own credential rather than the publisher’s: Authorization header — Bearer followed by your PinSharing API key (ps_…). Free keys: https://pinsharing.com/dashboard. You set it in your own client’s config, on your machine — this marketplace never holds it.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Look up an address, place name or point of interest and get coordinates (lat, lon), a readable label and address parts, from OpenStreetMap data. Use it before static_map or privacy_area_map when you only have an address. Counts 1 address lookup against the account's monthly cap. Results may be stored: up to 30 days on the Free plan, indefinitely on paid plans. Show "© OpenStreetMap contributors" w
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bbox | array | no | [min_lon, min_lat, max_lon, max_lat] |
| lang | string | no | Preferred language for names, e.g. en, de, fr |
| limit | integer | no | Maximum number of matches |
| near | object | no | Prefer matches near this point |
| query | string | yes | Address, place or point of interest, e.g. "233 S Wacker Dr, Chicago" or "Oswego, Illinois" |
Find the nearest address or place to a latitude/longitude, from OpenStreetMap data. Counts 1 address lookup against the account's monthly cap. Same storage terms and attribution as geocode.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lang | string | no | Preferred language for names, e.g. en, de, fr |
| lat | number | yes | Latitude of the point to look up, in decimal degrees (WGS84) |
| limit | integer | no | Maximum number of nearby addresses or places to return |
| lon | number | yes | Longitude of the point to look up, in decimal degrees (WGS84) |
For a US latitude/longitude, return the public school district(s) and, by grade, the assigned public school with its attendance zone (method, confidence, school year, source), from NCES/Census data and PinSharing's attendance-zone collection. Where no zone is mapped yet, it lists the district's nearest regular schools for those grades instead and says so in coverage. Use geocode first if you only
| Parameter | Type | Required | Notes |
|---|---|---|---|
| grade | string | no | Only this grade: PK, K or 1 to 12. Omit for every grade |
| lat | number | yes | Latitude of the home or listing, in decimal degrees (WGS84) |
| lon | number | yes | Longitude of the home or listing, in decimal degrees (WGS84) |
Render a map as an image (returned inline) with optional pins (markers) and a line (path, e.g. a route). Give center and zoom, or just markers and/or path and the view is fitted automatically. Also returns a reusable image URL for web pages (add your key). Counts 1 static image against the account's monthly cap. Do not use this to show a private address such as someone's home; use privacy_area_map
| Parameter | Type | Required | Notes |
|---|---|---|---|
| center | object | no | Map centre; use with zoom |
| format | string | no | Image format. jpg and webp are smaller than png |
| height | integer | no | Image height in CSS pixels |
| markers | array | no | Pins to draw |
| padding | integer | no | Space in pixels kept around markers and paths when the view is fitted automatically |
| path | array | no | A line through these points, in order |
| scale | integer | no | Pixel density: 2 renders a sharper image for high-density screens at double the pixel size |
| style | string | no | Map style: light (default), dark, white or grayscale |
| width | integer | no | Image width in CSS pixels |
| zoom | number | no | 0 = world, 10 = city, 15 = streets, 18 = buildings |
Show roughly where a place is without revealing the exact point. The point is snapped to a grid and drawn as a shaded circle that always contains the true point, with no pin; every address in the same grid cell gets the identical image, so the exact location cannot be recovered or averaged out across listings. Use it for real-estate, rental and marketplace listings, people's homes, or any location
| Parameter | Type | Required | Notes |
|---|---|---|---|
| color | string | no | Circle colour as hex, e.g. 0f766e |
| format | string | no | Image format. jpg and webp are smaller than png |
| height | integer | no | Image height in CSS pixels |
| lat | number | yes | Latitude of the exact place to hide. It is snapped to the grid before use and never returned |
| lon | number | yes | Longitude of the exact place to hide. It is snapped to the grid before use and never returned |
| radius_m | number | no | Minimum circle radius in metres; it is raised if needed so the circle always contains the true point |
| scale | integer | no | Pixel density: 2 renders a sharper image for high-density screens at double the pixel size |
| snap_deg | number | no | Grid size in degrees (0.01 is about 1 km). 0 turns snapping off and is not recommended |
| style | string | no | Map style: light (default), dark, white or grayscale |
| width | integer | no | Image width in CSS pixels |
Get ready-to-paste HTML/JavaScript for an interactive, zoomable PinSharing map in a web page (MapLibre GL JS vector map, Leaflet or OpenLayers raster map), or the raster tile URL template for any other library. Replace YOUR_KEY with a key restricted to the website. Needs no key and uses no quota; the map itself counts map tiles when viewed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| library | string | yes | maplibre = vector map (sharpest); leaflet or openlayers = raster tiles; tile_url = just the XYZ URL template |
| style | string | no | Map style: light (default), dark, white or grayscale |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install PinSharing Maps or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| geocode | no tags | |
| reverse_geocode | no tags | |
| school_lookup | no tags | |
| static_map | no tags | |
| privacy_area_map | no tags | |
| map_setup | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.2.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish PinSharing Maps can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.