Hive Trade
REMOTE · HIVE-MCP-GATEWAY.ONRENDER.COM · SCANNED SEP 20
MCP server: cross-venue spread + yield drivers, ROI radar telemetry · Hive Civilization
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 349 tokens (~69/item across 5 items; 5 tools + 0 resources), lean.Pass
- 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 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Hive Trade MCP server?
Hive Trade is a hosted endpoint at https://hive-mcp-gateway.onrender.com/trade/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · hive-mcp-gateway.onrender.com
claude mcp add --transport http srotzin-hive-mcp-trade 'https://hive-mcp-gateway.onrender.com/trade/mcp'
{
"mcpServers": {
"srotzin-hive-mcp-trade": {
"url": "https://hive-mcp-gateway.onrender.com/trade/mcp"
}
}
} {
"servers": {
"srotzin-hive-mcp-trade": {
"type": "http",
"url": "https://hive-mcp-gateway.onrender.com/trade/mcp"
}
}
} [mcp_servers.srotzin-hive-mcp-trade] url = "https://hive-mcp-gateway.onrender.com/trade/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"srotzin-hive-mcp-trade": {
"type": "remote",
"url": "https://hive-mcp-gateway.onrender.com/trade/mcp",
"enabled": true
}
}
} openclaw mcp add srotzin-hive-mcp-trade --url 'https://hive-mcp-gateway.onrender.com/trade/mcp' --transport streamable-http
mcp_servers:
srotzin-hive-mcp-trade:
url: "https://hive-mcp-gateway.onrender.com/trade/mcp" {
"McpServers": {
"srotzin-hive-mcp-trade": {
"Transport": "http",
"Url": "https://hive-mcp-gateway.onrender.com/trade/mcp"
}
}
} assistant mcp add srotzin-hive-mcp-trade -t streamable-http -u 'https://hive-mcp-gateway.onrender.com/trade/mcp'
{
"mcpServers": {
"srotzin-hive-mcp-trade": {
"type": "http",
"url": "https://hive-mcp-gateway.onrender.com/trade/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 Sept 26 +1
- Stability: 0.97 → pass security
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 20 Sept 2026 · Probed https://hive-mcp-gateway.onrender.com/trade/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 24 Jul 2026 | 22 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 756bcb97dcf1455f0ebf70e5dbe07256 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hive-mcp-gateway.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hive-mcp-gateway.onrender.com/trade/mcp | Verified | 200 | |
| http (plaintext) | http://hive-mcp-gateway.onrender.com/trade/mcp | HTTPS enforced | 301 | https://hive-mcp-gateway.onrender.com/trade/mcp |
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 →
trade_create_invoice ~155
Create a cross-border invoice. Buyer (SMB) and supplier exchange DIDs; invoice amount + currency + chain selected at creation. Fee auto-computed from tier.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | number | yes | Invoice amount in USD (max $250,000 for MVP) |
| buyer_did | string | yes | DID of the SMB buyer |
| memo | string | – | Free-form invoice memo (PO number, goods description) |
| settle_chain | string | yes | base, ethereum, or solana |
| settle_currency | string | yes | USDT or USDC |
| supplier_did | string | yes | DID of the overseas supplier |
| supplier_payout_address | string | yes | Supplier's receiving address on the chosen chain |
No output schema declared.
No examples provided.
trade_dispute_invoice ~89
Open a dispute on an invoice. Routes to HiveLaw arbitration if buyer and supplier cannot resolve. Settlement is held in escrow until resolution.
| Name | Type | Req | Description |
|---|---|---|---|
| claimant_did | string | yes | DID of the disputing party (buyer or supplier) |
| evidence_url | string | – | Optional URL to supporting documents |
| invoice_id | string | yes | Invoice ID |
| reason | string | yes | Dispute reason |
No output schema declared.
No examples provided.
trade_get_fees ~37
Get the cross-border invoice fee schedule and SWIFT wire comparison (Hive vs. typical SMB wire fees, FX spreads, settlement times).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trade_get_invoice ~36
Retrieve invoice status, settlement transaction hash, and dispute history.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | Invoice ID returned from trade_create_invoice |
No output schema declared.
No examples provided.
trade_get_listing ~32
Get the public listing metadata (target user, fee schedule, settlement currencies/chains, cumulative volume, council origin).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Hive Trade MCP server?
Hive Trade is an MCP server listed in the public MCP registry as io.github.srotzin/hive-mcp-trade. MCP server: cross-venue spread + yield drivers, ROI radar telemetry · Hive Civilization. This page covers its hosted endpoint (https://hive-mcp-gateway.onrender.com/trade/mcp).
Is the Hive Trade MCP server safe to use?
Hive Trade scores 76 out of 100 on VerifyMCP. 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 Hive Trade MCP server expose?
Hive Trade exposes 5 tools: trade_get_fees, trade_get_listing, trade_create_invoice, trade_get_invoice, trade_dispute_invoice. Their descriptions and schemas cost roughly 349 tokens of context every time the server is loaded.
Does the Hive Trade MCP server require authentication?
No. We connected to Hive Trade without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Hive Trade MCP server still maintained?
Hive Trade is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.