PinSharing Maps

com.pinsharingPublished by pinsharing.comOfficial publisherv1.0.2Updated Nov 5, 2026

Geocoding, static maps and privacy-safe area maps from OpenStreetMap data. Hard caps, no overage.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle Media & Design

Server details

Identifier: com.pinsharing/maps
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Nov 5, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to pinsharing.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.pinsharing%2Fmaps.svg)](https://sourceweft.com/mcp/com.pinsharing%2Fmaps?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

PinSharing Maps is a hosted MCP server on OpenStreetMap data that lets an assistant geocode places and render static or privacy-area map images.

What you can do: Convert addresses or place names to coordinates, and coordinates back to an address or place
Render static map images with markers or a route
Render privacy-area maps that show a shaded area instead of an exact pin
Get code and URLs for interactive maps in MapLibre GL JS, Leaflet or OpenLayers
When to use it: Useful when an assistant needs to turn addresses into coordinates, place markers or routes on a map image, or show an approximate location without revealing an exact point. It suits chat or document workflows that need map visuals without building a mapping stack.
Requirements: A remote MCP endpoint at api.pinsharing.com, reachable over HTTPS. A PinSharing API key (ps_...) sent as a bearer token in the Authorization header; a free key is available from the dashboard. Clients that only launch local stdio servers need the provided bridge, which requires Git and Node.js 18+.

Before you install

The API key is a credential: keep it out of shared configs and logs. Tool calls consume metered units (geocodes and static images) against monthly caps, with no overage billing. Map results and images must carry OpenStreetMap attribution wherever they appear. Requests go to a third-party service, api.pinsharing.com.

Installation

In SourceWeft

Open PinSharing Maps in the dashboard and add it to a workspace.
Connect Authorization token credentials. They are stored privately and never shown on public pages.
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/com.pinsharing%2Fmaps/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": {
    "pinsharing-maps": {
      "type": "http",
      "url": "https://api.pinsharing.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

PinSharing MCP

PinSharing (https://pinsharing.com) is a map API built on OpenStreetMap data, with a free plan and flat paid plans. It provides static map images, including a privacy-area mode, geocoding, and tiles. This repository provides a small stdio-to-HTTP bridge for MCP clients that can only launch local servers.

MCP Registry: com.pinsharing/maps

Most clients: use the hosted server directly

The hosted MCP server is available at:

https://api.pinsharing.com/v1/mcp

See https://pinsharing.com/docs/mcp for setup. With Claude Code:

bash

claude mcp add --transport http pinsharing https://api.pinsharing.com/v1/mcp --header "Authorization: Bearer YOUR_KEY"

claude mcp add --transport http pinsharing https://api.pinsharing.com/v1/mcp --header "Authorization: Bearer YOUR_KEY"

Clients that only run local servers (stdio)

Some clients, such as Claude Desktop with claude_desktop_config.json, can only launch local stdio MCP servers. For those, use this bridge.

json

{  "mcpServers": {    "pinsharing": {      "command": "npx",      "args": ["-y", "github:Software-Consulting/pinsharing-mcp"],      "env": { "PINSHARING_API_KEY": "ps_your_key" }    }  }}

{  "mcpServers": {    "pinsharing": {      "command": "npx",      "args": ["-y", "github:Software-Consulting/pinsharing-mcp"],      "env": { "PINSHARING_API_KEY": "ps_your_key" }    }  }}

Git and Node.js 18+ are required. An npm package (@pinsharing/mcp) is coming.

Tools

Tool	What it does	What it counts
`geocode`	Convert addresses or place names to coordinates	1 geocode
`reverse_geocode`	Convert coordinates to an address or place	1 geocode
`static_map`	Render a map image with markers or a route	1 static image
`privacy_area_map`	Show roughly where a place is (a shaded area, no pin); never reveals the exact point	1 static image
`map_setup`	Code and URLs for an interactive map (MapLibre GL JS, Leaflet, OpenLayers)	free

Configuration

Variable	Required	Default	Description
`PINSHARING_API_KEY`	Recommended	none	PinSharing API key (`ps_...`). Without it, discovery works and tool calls return the server's `missing_key` error.
`PINSHARING_MCP_URL`	No	`https://api.pinsharing.com/v1/mcp`	Hosted MCP server URL. Must be `https:` unless the host is `localhost` or `127.0.0.1`.
`PINSHARING_MCP_TIMEOUT_MS`	No	`60000`	HTTP timeout in milliseconds.
`PINSHARING_MCP_DEBUG`	No	unset	Set to `1` to write debug logs to stderr.

How it works

The bridge reads JSON-RPC messages from stdin, one per line, and forwards each one to the hosted MCP server over HTTPS. Responses are written to stdout, one JSON object per line. Nothing is stored locally. The API key is only sent to api.pinsharing.com in the Authorization header, and never printed in logs or errors.

Plans and caps

PinSharing has hard monthly caps and no overage billing. A free plan is available without a card:

Pricing and caps: https://pinsharing.com/pricing
Free keys / dashboard: https://pinsharing.com/dashboard

Attribution

Development

The project has zero runtime or development dependencies.

License

MIT. PinSharing is a service of Wells Software Consulting LLC.

Source: README.md at commit d5e94d1

Tools

This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

v1.0.2LatestNov 5, 2026
v1.0.0Nov 5, 2026

Score

60% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declaredRequired10 pts
Tools listed15 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