Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Rel-Time Protocol (Bitcoin & VDF Provenance) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
trust score
238
downloads a day
local
runs on your machine
2k
downloads in 30d
What it does
Zero-knowledge Bitcoin Mainnet & VDF timestamping, Passkey signing, Sun-Stamps, and tamper audits.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user rel-time-protocol-bitcoin-vdf-provenance-mcp '--' npx -y @rel-time/mcp-server
# 2 — ask your agent for something these tools do
# reltime_anchor_file, reltime_link_passkey, reltime_stamp_file and 8 more
Rel-Time Protocol (Bitcoin & VDF Provenance) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
RDAll 1 server
relsun369-dev1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Rel-Time Protocol (Bitcoin & VDF Provenance) as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user rel-time-protocol-bitcoin-vdf-provenance-mcp '--' npx -y @rel-time/mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Zero-knowledge file anchoring + 1-Click Stamped Copy + 4-Plate Provenance Certificate: Computes the SHA-256 hash of a local file ENTIRELY ON THE LOCAL MACHINE (the file never leaves the user's computer), supports both Anonymous and Biometric (Passkey) Anchors, anchors the 64-char hash to the…
No parameter schema on file.
Links the user's hardware Passkey (TouchID, FaceID, or YubiKey) to @rel-time/mcp-server for Biometric Anchors. Opens https://rel-time.com/mcp-passkey in the system browser, waits for the user's biometric touch, and saves { public_key_hex, passkey_signature } to ~/.reltime/passkey.json.
No parameter schema on file.
Overlays the authentic 64-ray Rel-Time Sun-Stamp (Option A: pure crisp Sun-Stamp, zero glare, no pill) onto the bottom-right corner of a local PDF or Image (.png, .jpg, .jpeg, .webp, .gif) 100% locally. Returns 'Feature unavailable for this file type' for other file formats.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_path | string | yes | Absolute path to the local PDF or Image file. |
| hash | string | no | Optional 64-char hex hash to generate the Sun-Stamp from. If omitted, computes the SHA-256 hash of file_path locally. |
| output_path | string | no | Optional custom output file path for the stamped copy. |
Anchors a 64-character hexadecimal SHA-256 hash directly into the Rel-Time VDF & Bitcoin Merkle Tree. Consumes 1 Hash Credit from the configured Rel-Time API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_hash | string | yes | 64-character hex SHA-256 hash of the payload/artifact. |
| anchor_mode | string | no | 'standard' (Data Integrity) or 'temporal' (VDF Sequence Ordering). |
| api_key | string | no | Optional override for RELTIME_API_KEY. |
Generates and downloads the official 64-ray Rel-Time Sun-Stamp SVG (GET /v1/stamp/{hash}) for any 64-char SHA-256 hash or T_index. Requires NO API key and works across all tiers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hash | string | yes | 64-character hex SHA-256 hash (client_hash or t_index). |
| output_svg_path | string | no | Optional local file path where the .svg Sun-Stamp should be saved. |
Queries GET /v1/proof/{hash} to check the Bitcoin settlement status (Block Height, Block UTC Time, Bitcoin TXID, Merkle Root, and Merkle Inclusion Path) of an anchored hash. Optionally saves or updates the finalized .json Doomsday Proof receipt AND/OR generates the 4-Plate Sovereign…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hash | string | yes | The 64-character client_hash or t_index to verify. |
| file_path | string | no | Optional local file path corresponding to the anchored hash (used to verify local custody/Passkey ownership and populate exact file name, size, and MIME type on the Provenance Certificate). |
| output_json_path | string | no | Optional local file path to save the settled JSON Doomsday Proof receipt. |
| save_certificate_html | boolean | no | If true, generates and saves the 4-Plate Sovereign Cryptographic Provenance Certificate (reltime-certificate-<name>.html) on demand. |
| output_certificate_html_path | string | no | Optional custom file path to save the 4-Plate Provenance Certificate HTML. |
| open_certificate_in_browser | boolean | no | If true, generates the 4-Plate Sovereign Cryptographic Provenance Certificate HTML and opens it in the system browser. |
Checks the remaining Hash Credits, tier, and lifetime usage of the configured Rel-Time API key (GET /api/v1/account). If no API key is configured yet, returns the 4 available Rel-Time Tiers (universal $3, launch $5/25, standard $50/500, enterprise $399/5,000) and payment options…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | Optional: pass a rel_key_... API key to check its balance AND automatically save it to ~/.reltime/api_key.json for all future calls. |
Self-onboarding & Top-Up for all 4 Rel-Time Tiers via EITHER Bitcoin Lightning OR Stripe Card Checkout (POST /v1/agent/invoice & POST /v1/agent/claim). IMPORTANT: 1. Before calling create_invoice for a new key, ask the user which tier AND payment method (lightning or stripe) they want:…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | 'create_invoice' generates a Lightning BOLT11 invoice or Stripe Checkout Session; 'claim_invoice' exchanges a paid Lightning invoice_id or Stripe session_id ('cs_...') for a new API key or reloads an |
| pack | string | no | REQUIRED for 'create_invoice' after asking the user. Which tier the user selected: 'universal' ($3/anchor), 'launch' ($5 / 25 Hashes, max 3 per key), 'standard' ($50 / 500 Hashes), or 'enterprise' ($3 |
| payment_method | string | no | REQUIRED for 'create_invoice' after asking the user. Payment method: 'lightning' (Bitcoin Lightning BOLT11 invoice + QR code) or 'stripe' (Stripe Card Checkout URL + browser launch). Never guess — if |
| quantity | number | no | Optional credit quantity when pack is 'universal' ($3.00 per credit, default 1). |
| invoice_id | string | no | Required when action is 'claim_invoice'. Pass either the Strike Lightning invoice_id UUID or the Stripe Checkout session_id (cs_...). |
| api_key | string | no | Optional: pass an existing rel_key_... key (or omit to use RELTIME_API_KEY if reload_existing is true) to reload Hash Credits into that key without rotating it. |
| reload_existing | boolean | no | If true, reloads Hash Credits into the currently configured RELTIME_API_KEY (or passed api_key) instead of generating a new key. |
SUPERHIGHWAY EXCLUSIVE ($399 / 5,000 Hashes): Data Integrity Audit, Instant Tamper Detection & Forensic Timechain Report (GET /api/v1/account + GET /api/v1/account/history + local SHA-256 cross-reference). Fetches the account's chronological anchor ledger, aggregates Bitcoin block settlements,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| verify_local_path | string | no | Optional local file path or folder/directory path to audit bit-for-bit (Zero-Knowledge local SHA-256 + Passkey attestation check + Stamped Copy check) against the Rel-Time Bitcoin ledger. |
| limit | number | no | Maximum number of audit ledger entries to retrieve (default 100, max 500). |
| status_filter | string | no | Filter ledger entries by settlement status: 'all' (default), 'settled', or 'pending'. |
| mode_filter | string | no | Filter ledger entries by mode: 'all' (default), 'standard', 'temporal' (VDF T_index), or 'biometric' (Hardware Passkey attested). |
| signer_filter | string | no | Optional full or partial Hardware Passkey public_key_hex to filter anchors signed by a specific employee or corporate YubiKey. |
| save_html_report | boolean | no | If true (default), saves an interactive dark-mode HTML Superhighway Audit Trail dashboard (reltime-audit-report-<date>.html). |
| open_in_browser | boolean | no | If true (default), automatically opens the generated HTML Audit Trail dashboard in the user's browser. |
| export_csv | boolean | no | If true, also exports the audit ledger to a .csv spreadsheet file. |
| output_dir | string | no | Optional directory where the generated .html / .csv audit reports should be saved (defaults to verify_local_path folder or ~/.reltime/audits). |
| api_key | string | no | Optional override for RELTIME_API_KEY. |
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Rel-Time Protocol (Bitcoin & VDF Provenance) or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 93 / 100
Release 1.3.0 · scanned 4 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings1 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digestb6e63b1bbb5ca7616d3767491f2ad0d8d08495b3879a655c78e250d973e2c0fe
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (11 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| reltime_anchor_file | no tags | |
| reltime_anchor_folder | no tags | |
| reltime_link_passkey | no tags | |
| reltime_stamp_file | no tags | |
| reltime_anchor_hash | no tags | |
| reltime_get_sun_stamp | no tags | |
| reltime_check_proof | no tags | |
| reltime_account_status | no tags | |
| reltime_provision_agent_key | no tags | |
| reltime_audit_trail | no tags | |
| reltime_watch | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestb6e63b1bbb5ca761
Scanned2026-11-04
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.3.0. Pin a release below and the command asks for exactly that one.
1.3.0
4 Nov 2026
latestNo release note was published with this version.
1.2.14
3 Nov 2026
No release note was published with this version.
1.2.12
3 Nov 2026
No release note was published with this version.
1.2.11
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Rel-Time Protocol (Bitcoin & VDF Provenance) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.