rper2001-rigshareSAFE
Model Context Protocol server for RIGShare — browse construction equipment and Robotics & AI hardware rentals from any MCP-compatible AI agent. Also recruits equipment owners.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Model Context Protocol server for RIGShare. Browse construction equipment and Robotics & AI hardware rentals from any MCP-compatible AI agent (Claude Desktop, Cursor, VS Code, custom agent frameworks).
What it does
Exposes twenty tools to your AI agent: four read-only (no auth) and sixteen authenticated (require a RIGShare API key with the right scope). Together they let an agent book equipment in either division, list equipment for an owner, and run a remote session on Robotics & AI hardware, while a human always stays in the loop for money: an agent never enters a card, never approves a request on the owner's behalf, and never steps up to MFA.
Read-only (no API key needed):
Booking (renter side):
5c6848d2d25cOBSERVED · 2026-10-14Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add rigshare-mcp --env RIGSHARE_API_KEY=${RIGSHARE_API_KEY} -- npx -y [email protected]Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (2 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (5)
@modelcontextprotocol/sdk, zod, @types/node, typescript
- `RIGSHARE_API_KEY`: **Optional**. Enables the 16 authenticated tools. Without it, those tools return a descriptive error and the 4 read-only tools still work. Create a key at https://www.rigshare.ap
- **Read-only** (no API key): `rigshare_search_equipment`,
**Read-only (no API key needed):**
Gates applied: no_behavioural_pass.
5c6848d2d25cfull audit observations/trust-audit/mcp-server/rigshare-hq__rigshare-mcp.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-14 | 5c6848d2d25c | SAFE | B | 89 | first audit |
Questions
What is the rper2001-rigshare MCP server?
Model Context Protocol server for RIGShare — browse construction equipment and Robotics & AI hardware rentals from any MCP-compatible AI agent. Also recruits equipment owners.
Is rper2001-rigshare safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does rper2001-rigshare need?
It reads RIGSHARE_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does rper2001-rigshare run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as rigshare-mcp at 2.2.1.
How current is this page?
The grade is for one exact copy of the source (5c6848d2d25c), read on 2026-10-14. The repository is watched and re-audited when it changes.