Vayapin

app.vayapinPublished by vayapin.appv0.1.2Updated Oct 24, 2026

VayaPin MCP: pin resolution + Google Maps geocoding/places + AfterShip tracking, with BYOK.

VerifiedSTDIODesktop onlyLocation & LifestyleWeb Search & Scraping

Overview

AI-generated overview

Lets an assistant resolve VayaPin pins and use Google Maps geocoding, places, and AfterShip shipment tracking through a local MCP process.

What you can do
VayaPin MCP exposes tools for pin resolution plus Google Maps geocoding and places lookups, and for AfterShip package tracking. It runs locally over stdio as an npm package and authenticates to the VayaPin API with a personal access token. An optional tool-slice setting can expose only a subset of tools when a client has a tool-count ceiling.
When to use it
Worth adding when an assistant needs to turn addresses or place names into coordinates, look up places, resolve VayaPin pins, or check shipment tracking status inside a chat or agent workflow. It is desktop-only, so it is not usable from a browser-hosted client.
Requirements
Node.js to run the npm package @vayacore/mcp over stdio on a desktop machine. A VayaPin Personal Access Token in the environment variable VAYAPIN_PAT, generated on the VayaPin developer portal. Optional variables VAYAPIN_MCP_API_URL and VAYAPIN_MCP_SLICE. Network access to the VayaPin API and to the underlying mapping and tracking services.
Before you install
The required VAYAPIN_PAT secret is sent as a bearer token to the VayaPin API, so treat it as a credential and avoid exposing it in logs or shared configuration. Requests go to third-party mapping and tracking services, so addresses, place queries, and tracking numbers leave the machine. VAYAPIN_MCP_API_URL can redirect traffic to a staging or self-hosted endpoint, which changes where data is sent.

Installation

In SourceWeft

  1. Open Vayapin in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.