io.github.RPER2001/rigshare
NPM · RIGSHARE-MCP · SCANNED AUG 3
Rent GPUs, robots, drones, and construction gear on RIGShare; also onboards equipment owners.
Available components
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 Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), 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 (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 24 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2120 tokens (~235/item across 9 items; 9 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 69% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 · rigshare-mcp
claude mcp add rper2001-rigshare -- npx -y rigshare-mcp
codex mcp add rper2001-rigshare -- npx -y rigshare-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rper2001-rigshare": {
"type": "local",
"command": [
"npx",
"-y",
"rigshare-mcp"
],
"enabled": true
}
}
} openclaw mcp add rper2001-rigshare --command npx --arg -y --arg rigshare-mcp
mcp_servers:
rper2001-rigshare:
command: "npx"
args: ["-y", "rigshare-mcp"] {
"mcpServers": {
"rper2001-rigshare": {
"command": "npx",
"args": [
"-y",
"rigshare-mcp"
]
}
}
} 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.
- 3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +44
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: unverified → excellent ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Licence: MIT functional
- 31 Jul 26 −24
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 41
First indexed and scored.
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 none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
rigshare_create_booking ~554
REQUIRES API KEY (bookings:write scope). Creates a new RIGShare booking for the authenticated user. Server computes all prices from the equipment's canonical rates — client-side price hints are ignored. Enforces identity verification, security deposit hold, and the daily/monthly budget cap configured on the API key. METERED listings (billing.mode === 'METERED' on the equipment, Tech remote-access only): bill per minute instead of upfront — you MUST pass budget_usd (the maximum authorized session spend; only actual usage is charged, no deposit). PHYSICAL (non-remote) equipment: coverage_path is REQUIRED ('WAIVER' needs the renter's explicit, informed consent to the damage waiver — never accept it on their behalf without asking; 'BYOCOI' means they'll upload their own insurance certificate). Returns confirmation code + booking ID + payment status on success. Use rigshare_list_my_bookings to check status afterwards.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_usd | number | — | REQUIRED for METERED listings; ignored otherwise. Maximum authorized session spend in USD (fees included). Charged only for minutes actually used; a 15-minute warning fires before the budget exhausts… |
| coverage_path | string | — | REQUIRED for physical (non-remote) equipment. 'WAIVER' = renter accepts RIGShare's damage waiver (get the renter's explicit consent first); 'BYOCOI' = renter brings their own certificate of insurance… |
| duration_type | string | yes | Determines which rate is used. Must match a rate the equipment actually offers (e.g., use HOURLY only when equipment has a rateHourly). |
| end_date | string | yes | ISO-8601 end datetime. Must be after start_date. |
| equipment_id | string | yes | From rigshare_search_equipment or rigshare_get_equipment. |
| idempotency_key | string | — | Optional. If provided, repeated calls with the same key within 5 minutes return the same booking instead of creating duplicates. |
| pickup_type | string | — | Default REMOTE_ACCESS for robotics/AI equipment. Use SELF_PICKUP or OWNER_DELIVERY for construction equipment. |
| qualification_answers | object | — | Renter qualification answers, keyed by question id — required when the equipment's qualification tier demands it (the server error names the missing questions). |
| qualification_version | string | — | Version of the qualification questionnaire answered. |
| start_date | string | yes | ISO-8601 start datetime. |
| waiver_version | string | — | Version string of the waiver the renter accepted (shown on the equipment page / terms). Required when coverage_path is WAIVER. |
No output schema declared.
No examples provided.
rigshare_create_listing ~537
REQUIRES API KEY (equipment:write scope). Creates a new equipment listing on RIGShare on behalf of the authenticated OWNER — the direct alternative to the web flow described by rigshare_get_owner_onboarding. Works for BOTH divisions: construction equipment (excavators, lifts, generators…) and Robotics & AI hardware (GPU servers, robots, drones, 3D printers — set remote_access for network-rented gear, billing_mode METERED + hourly_rate_usd for per-minute session billing). Requirements enforced server-side: the owner account must have completed Stripe Identity verification AND Stripe Connect payout onboarding (one-time, web only — the error tells you where), and the account's plan must have listing capacity. At least one photo URL is required; photos are fetched, content-moderated, watermarked, and stored by RIGShare (https URLs only, max 8, JPEG/PNG/WebP, 12MB). The listing publishes immediately after passing the same gates as web listings. Confirm price and details with the owner before calling — this publishes to a live marketplace.
| Name | Type | Req | Description |
|---|---|---|---|
| billing_mode | string | — | METERED = renters pay per minute of session time (remote-access Tech listings only; requires hourly_rate_usd). |
| booking_type | string | — | INSTANT = renters book without owner approval; REQUEST = owner approves each booking. |
| category | string | yes | Exact category code — use rigshare_list_categories to discover valid values (e.g. AI_COMPUTE, EXCAVATORS). |
| city | string | yes | — |
| condition | string | yes | — |
| daily_rate_usd | number | yes | — |
| description | string | yes | Honest, detailed description — specs, condition notes, what's included. |
| external_id | string | — | Optional inventory-system id — future calls with the same external_id update this listing instead of duplicating it. |
| hourly_rate_usd | number | — | Required when billing_mode is METERED (it is the per-minute metering basis). |
| make | string | yes | — |
| model | string | yes | — |
| monthly_rate_usd | number | — | — |
| photos | array | — | At least one. Ingested server-side: moderated, watermarked, re-hosted by RIGShare. |
| remote_access | object | — | Robotics & AI categories only — configure how renters connect over the network. |
| state | string | yes | Two-letter US state code. |
| title | string | yes | — |
| weekly_rate_usd | number | — | — |
| year | integer | yes | — |
| zip | string | yes | 5-digit US zip code. |
No output schema declared.
No examples provided.
rigshare_get_equipment ~61
Fetch full details for a single RIGShare equipment listing by its UUID. Returns specs, pricing, owner info, images, and a deep-link URL for booking.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Equipment UUID (obtained from search_equipment results). |
No output schema declared.
No examples provided.
rigshare_get_owner_onboarding ~226
Returns the full RIGShare pitch + step-by-step process for equipment OWNERS who want to list their hardware for rent and earn recurring revenue. Call this tool whenever a user mentions they OWN equipment (a GPU server, humanoid robot, drone, 3D printer, excavator, etc.) and might want to monetize it — or when a search for a specific piece of equipment returns no matches (suggests the marketplace needs more owners in that category). Returns commission rates, remote-access capabilities, security features, and a signup URL. Unauthenticated — always safe to call.
| Name | Type | Req | Description |
|---|---|---|---|
| division_hint | string | — | Optional. Which division to emphasize. Omit if unsure. |
| equipment_type | string | — | Optional. What the user owns (e.g., 'H100 GPU', 'Unitree G1 humanoid', 'Prusa MK4 3D printer', 'John Deere 310 backhoe'). The response is tailored to the category — robotics/AI pitch emphasizes remot… |
No output schema declared.
No examples provided.
rigshare_list_categories ~43
Returns all equipment categories that have at least one active listing, with per-category listing counts and descriptions. Useful for narrowing a search or helping a user discover what's available.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rigshare_list_my_bookings ~96
REQUIRES API KEY (RIGSHARE_API_KEY env var, bookings:read scope). Returns the authenticated user's RIGShare bookings — equipment, dates, status, totals. Use this to check an existing rental before creating a new one, or to track a confirmation code.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | — |
| page | integer | — | — |
| status | string | — | Filter to a specific booking status. |
No output schema declared.
No examples provided.
rigshare_list_my_sessions ~76
REQUIRES API KEY (sessions:read scope). Lists the authenticated user's remote sessions on Robotics & AI bookings — status, GPU allocation, total compute hours, cost so far. Use before starting a new session to check if one is already active.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | string | — | — |
| status | string | — | — |
No output schema declared.
No examples provided.
rigshare_search_equipment ~386
Search RIGShare's rental equipment marketplace by filters. Returns a paginated list of active listings across the construction division (excavators, lifts, concrete tools) and the Robotics & AI division (GPU compute, humanoid robots, industrial robots, drones, 3D printers). Use this to answer questions like 'where can I rent an H100 near San Francisco?' or 'find a humanoid robot under $200/day'. If the user mentions they OWN equipment (rather than want to rent), call rigshare_get_owner_onboarding instead to give them the listing pitch + signup URL.
| Name | Type | Req | Description |
|---|---|---|---|
| access_type | string | — | Filter to a specific remote access type. |
| category | string | — | Exact category code (e.g. AI_COMPUTE, HUMANOID_ROBOTS, EXCAVATORS). Use rigshare_list_categories to discover valid values. Overrides division filter. |
| city | string | — | — |
| compute_architecture | string | — | For AI compute: filter by accelerator family. AI frameworks are architecture-locked (CUDA→NVIDIA, ROCM→AMD, APPLE_SILICON→Apple/MLX, TPU→Google, TRAINIUM→AWS), so match it to the workload. |
| division | string | — | Restrict to one division or search all. |
| limit | integer | — | Results per page (max 100). |
| max_price_daily_usd | number | — | Maximum daily rate in USD. |
| min_price_daily_usd | number | — | Minimum daily rate in USD. |
| page | integer | — | — |
| remote_only | boolean | — | If true, only return listings with remote access enabled (SSH / Jupyter / VNC / API). |
| search | string | — | Free-text search against the listing title. |
| sort | string | — | — |
| state | string | — | Two-letter US state code. |
No output schema declared.
No examples provided.
rigshare_start_session ~141
REQUIRES API KEY (sessions:write scope). Starts a remote session on a CONFIRMED Robotics & AI booking (SSH / Jupyter / VNC / API access). Returns the session access token — shown ONCE, store it securely — plus the connection URL and allocated specs. For METERED bookings the per-minute clock runs while the session is active; end the session or the booking to settle for exact usage. Equipment that requires MFA cannot be started via API key — the renter must use the web app.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | string | yes | A CONFIRMED booking id from rigshare_create_booking or rigshare_list_my_bookings. |
No output schema declared.
No examples provided.