dev.forgesworn/rendezvous-mcp
NPM · RENDEZVOUS-MCP
Fair meeting point discovery for AI agents with isochrone-based travel time fairness
Available components
Last scanned (10 hours ago)
Scores higher than 93% of npm servers
Category Maps and Location
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 → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 39 of 123 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- 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 206 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 0
- Stability: 0.97 → pass security
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 5 Nov 2026 · Analysed npm/rendezvous-mcp@1.1.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| 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 | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:988b85f4fa9135627bb44c4a5c7a30f94fbc83bd04c5f3faf8d4d6ec5cf2cc94647d664bbf5eae0b3ede903bfd9528c49edcb83762190f55be7a94ebd |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 123 packages
| Packages resolved | 123 |
|---|---|
| Stale | 39 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get-directions ~64
Get directions between two points with distance, duration, and turn-by-turn steps. Returns a GeoJSON LineString of the route geometry.
| Name | Type | Req | Description |
|---|---|---|---|
| from | object | yes | Starting point |
| to | object | yes | Destination point |
| transport_mode | string | yes | Travel 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.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude of starting point |
| lon | number | yes | Longitude of starting point |
| time_minutes | number | yes | Maximum travel time in minutes |
| transport_mode | string | yes | Travel 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.
| Name | Type | Req | Description |
|---|---|---|---|
| fairness | string | – | Scoring strategy: min_max (default, minimise longest journey), min_total (minimise total travel), min_variance (equalise travel times) |
| participants | array | yes | Participant locations (2–10 people) |
| transport_mode | string | yes | How participants will travel |
| venues | array | yes | Candidate 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.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Centre latitude |
| lon | number | yes | Centre longitude |
| radius_km | number | – | Search radius in km (default 5) |
| venue_types | array | yes | Venue 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.
| Name | Type | Req | Description |
|---|---|---|---|
| macaroon | string | yes | The macaroon from the payment_required response |
| preimage | string | yes | The payment preimage obtained after paying the invoice |
No output schema declared.
No examples provided.
How do I install the dev.forgesworn/rendezvous-mcp server?
dev.forgesworn/rendezvous-mcp runs locally as an npm package, launched with npx -y rendezvous-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · rendezvous-mcp
claude mcp add dev-forgesworn-rendezvous-mcp -- npx -y rendezvous-mcp
What is the dev.forgesworn/rendezvous-mcp server?
dev.forgesworn/rendezvous-mcp is listed in the public MCP registry as dev.forgesworn/rendezvous-mcp. Fair meeting point discovery for AI agents with isochrone-based travel time fairness. This page covers its npm package (rendezvous-mcp).
Is the dev.forgesworn/rendezvous-mcp server safe to use?
dev.forgesworn/rendezvous-mcp scores 90 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 dev.forgesworn/rendezvous-mcp server expose?
dev.forgesworn/rendezvous-mcp exposes 5 tools: score-venues, search-venues, get-isochrone, get-directions, store-routing-credentials. Their descriptions and schemas cost roughly 548 tokens of context every time the server is loaded.
Is the dev.forgesworn/rendezvous-mcp server still maintained?
dev.forgesworn/rendezvous-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the dev.forgesworn/rendezvous-mcp server under?
dev.forgesworn/rendezvous-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.