Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

dev.forgesworn/rendezvous-mcp

NPM · RENDEZVOUS-MCP · SCANNED AUG 3

Fair meeting point discovery for AI agents with isochrone-based travel time fairness

Available components

+51 this week 75 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (124 of 126), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (124 of 126), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to forgesworn/rendezvous-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 112 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 625 tokens (~125/item across 5 items; 5 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · rendezvous-mcp

# add to Claude Code
claude mcp add dev-forgesworn-rendezvous-mcp -- npx -y rendezvous-mcp
# add to Codex CLI
codex mcp add dev-forgesworn-rendezvous-mcp -- npx -y rendezvous-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-forgesworn-rendezvous-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "rendezvous-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-forgesworn-rendezvous-mcp --command npx --arg -y --arg rendezvous-mcp
# ~/.hermes/config.yaml
mcp_servers:
  dev-forgesworn-rendezvous-mcp:
    command: "npx"
    args: ["-y", "rendezvous-mcp"]
// mcp.json
{
  "mcpServers": {
    "dev-forgesworn-rendezvous-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "rendezvous-mcp"
      ]
    }
  }
}
Changelog

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.

  • 2 Aug 26 +21
    • Known CVEs: partial → unverified security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified functional
    • Dependency health: partial → unverified functional
    • Schema quality: unverified → good functional
  • 1 Aug 26 +8
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +22
    • Tool coverage: unverified → 100 functional
    • First check of Schema quality: unverified functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: fail functional
  • 27 Jul 26 24

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

Source repo:
forgesworn/rendezvous-mcp
Certificate issuer:
https://token.actions.githubusercontent.com
Certificate SAN:
https://github.com/forgesworn/rendezvous-mcp/.github/workflows/ci.yml@refs/heads/main
Rekor log index:
1248686255
Predicate type:
https://slsa.dev/provenance/v1
Subject digest:
sha512:988b85f4fa9135627bb44c4a5c7a30f94fbc83bd04c5f3faf8d4d6ec5cf2cc94647d664bbf5eae0b3ede903bfd9528c49edcb83762190f55be7a94ebd
Discovery method:
attestation_endpoint
Dependencies 124 packages

124 packages in the resolved dependency tree · 122 deprecated · 35 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 5 exposed · ~548 tokens

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.

Tool Tokens
get-directions ~64

Get directions between two points with distance, duration, and turn-by-turn steps. Returns a GeoJSON LineString of the route geometry.

NameTypeReqDescription
fromobjectyesStarting point
toobjectyesDestination point
transport_modestringyesTravel mode

No output schema declared.

No examples provided.

get-isochrone ~88

Get a reachability polygon showing everywhere reachable from a point within a given travel time. Returns a GeoJSON polygon. Useful for understanding how far someone can travel.

NameTypeReqDescription
latnumberyesLatitude of starting point
lonnumberyesLongitude of starting point
time_minutesnumberyesMaximum travel time in minutes
transport_modestringyesTravel mode

No output schema declared.

No examples provided.

score-venues ~135

Score candidate venues by travel time fairness for multiple participants. Computes travel times from each participant to each venue and ranks by fairness strategy. The AI should suggest venues (from its own knowledge or via search-venues) and pass them here for scoring.

NameTypeReqDescription
fairnessstringScoring strategy: min_max (default, minimise longest journey), min_total (minimise total travel), min_variance (equalise travel times)
participantsarrayyesParticipant locations (2–10 people)
transport_modestringyesHow participants will travel
venuesarrayyesCandidate venues to score (1–50)

No output schema declared.

No examples provided.

search-venues ~156

Search for venues (pubs, cafes, restaurants, parks, etc.) near a location using OpenStreetMap data. Returns name, coordinates, type, and OSM ID. Use this when you need comprehensive local venue data that may not be in your training knowledge.

NameTypeReqDescription
latnumberyesCentre latitude
lonnumberyesCentre longitude
radius_kmnumberSearch radius in km (default 5)
venue_typesarrayyesVenue types to search: pub, cafe, restaurant, park, library, playground, community_centre, bar, fast_food, garden, theatre, arts_centre, fitness_centre, sports_centre, escape_game, swimming_pool, ser…

No output schema declared.

No examples provided.

store-routing-credentials ~105

Store L402 payment credentials (macaroon + preimage) after paying a routing invoice. Call this after the user has paid the Lightning invoice returned by a payment_required response. Once stored, all subsequent routing calls (score-venues, get-isochrone, get-directions) will authenticate automatically.

NameTypeReqDescription
macaroonstringyesThe macaroon from the payment_required response
preimagestringyesThe payment preimage obtained after paying the invoice

No output schema declared.

No examples provided.