Hiveround
REMOTE · HIVEROUND.COM · SCANNED AUG 3
Marketplace MCP server for live venture-capital raises and agent-mediated dealflow.
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 →
Endpoint Security60
- 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 14 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1135 tokens (~81/item across 14 items; 14 tools + 0 resources), lean.Pass
- 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 Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 55% of tool parameters carry a description.Partial
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
remote · hiveround.com
claude mcp add --transport http stevemilton-marketplace https://hiveround.com/api/mcp
[mcp_servers.stevemilton-marketplace] url = "https://hiveround.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"stevemilton-marketplace": {
"type": "remote",
"url": "https://hiveround.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add stevemilton-marketplace --url https://hiveround.com/api/mcp --transport streamable-http
mcp_servers:
stevemilton-marketplace:
url: "https://hiveround.com/api/mcp" {
"mcpServers": {
"stevemilton-marketplace": {
"type": "http",
"url": "https://hiveround.com/api/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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 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
- 30 Jul 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
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 55
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 · Probed https://hiveround.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hiveround.com | CN=YE1,O=Let's Encrypt,C=US | 13 Jul 2026 | 11 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 561b775130f49ce4074b3f121165b1c51d6 |
| SANs: *.hiveround.com, hiveround.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC secure
Validation of hiveround.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hiveround.com. | present | 2371 | 13 | Verified |
| hiveround.com. | Verified address RRset verified with the apex keys |
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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hiveround.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://hiveround.com/api/mcp | HTTPS enforced | 301 | https://hiveround.com/api/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.
acknowledge_commitment ~82
Acknowledge a commitment as the founder or the investor. When both sides have acknowledged, status auto-promotes from soft_circled/term_sheet to 'committed' and the amount is added to the project's public round progress. Calling twice from the same side is a no-op. (requires API key)
| Name | Type | Req | Description |
|---|---|---|---|
| commitment_id | string | yes | Commitment UUID. |
No output schema declared.
No examples provided.
get_project ~31
Get the full project listing by slug, including the founder's GitHub handle.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | — |
No output schema declared.
No examples provided.
list_commitments ~77
List commitments where you're either the investor or the founder. Filter by project slug, your role, or status. (requires API key)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | — |
| role | string | — | Only commits where you're acting in this role. |
| slug | string | — | Filter to a single project. |
| status | string | — | — |
No output schema declared.
No examples provided.
list_intros ~113
List the intro threads you're a party to (sent as an investor or received as a founder). Each entry includes the counterparty, message count, last-message preview, and whether you have unread messages. Optionally filter by your role or unread-only. (requires API key)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | — |
| role | string | — | Filter to intros where you are the investor or the founder. Omit to see both. |
| unread_only | boolean | — | Only return threads with unread messages from the counterparty. |
No output schema declared.
No examples provided.
list_projects ~39
List the newest open projects raising on Hiveround. Returns at most 25.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | — |
| stage | string | — | — |
No output schema declared.
No examples provided.
list_watches ~66
Return your pipeline — every project you're watching, with stage, tags, raise size, and last-updated timestamp. Optionally filter by stage or tag. (requires API key)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | — |
| stage | string | — | — |
| tag | string | — | — |
No output schema declared.
No examples provided.
read_intro_thread ~55
Read all messages in a specific intro thread you're a party to. Marks the thread as read for you. (requires API key)
| Name | Type | Req | Description |
|---|---|---|---|
| intro_id | string | yes | Intro UUID, as returned by list_intros or request_intro. |
No output schema declared.
No examples provided.
request_intro ~69
Request an intro to a project's founder on behalf of the API key's owner. The founder receives an email with the investor's GitHub handle. (requires API key)
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Intro message from the investor (max 2000 chars) |
| slug | string | yes | Project slug |
No output schema declared.
No examples provided.
search_projects ~76
Search open projects by keyword across name, one-liner, description, and sector. Optional filters: stage, max raise size in USD.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | — |
| max_raise_usd | number | — | Maximum raise size in USD |
| query | string | yes | Free-text search query |
| stage | string | — | — |
No output schema declared.
No examples provided.
send_intro_message ~80
Append a message to an existing intro thread you're a party to. The other party gets an email notification linking back to the thread. Use this to follow up after request_intro or to keep a conversation moving. (requires API key)
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Message body (1–4000 chars). |
| intro_id | string | yes | Intro UUID. |
No output schema declared.
No examples provided.
submit_commitment ~207
Record an investor's intent-to-fund a project. Without terms it starts at 'soft_circled'; attach a terms object and it starts at 'term_sheet'. The founder still has to acknowledge — a commitment doesn't count as 'committed' (and doesn't show in the public round progress) until both sides have acked. (requires API key)
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | number | yes | Commitment amount in USD (whole dollars). |
| instrument | string | — | — |
| intro_id | string | — | Optional intro UUID to link this commitment to an existing conversation. |
| notes | string | — | Free-form note (max 4000 chars). |
| slug | string | yes | Project slug. |
| terms | object | — | Optional structured terms, e.g. { cap: 8000000, discount: 0.20, mfn: true, valuation: 4000000, pro_rata: true }. Presence promotes initial status from soft_circled to term_sheet. |
No output schema declared.
No examples provided.
update_commitment_status ~97
Change a commitment's status. Role-gated: only the investor can 'withdraw' a commitment, only the founder can mark it 'funded' (after the wire lands). Either side can move between soft_circled/term_sheet/committed. (requires API key)
| Name | Type | Req | Description |
|---|---|---|---|
| commitment_id | string | yes | — |
| notes | string | — | Optional note (max 4000 chars). |
| status | string | yes | — |
No output schema declared.
No examples provided.
update_watch ~60
Move a watched project to a new pipeline stage and/or append a note. The project must already be in your pipeline. (requires API key)
| Name | Type | Req | Description |
|---|---|---|---|
| notes | string | — | — |
| slug | string | yes | Project slug |
| stage | string | — | — |
No output schema declared.
No examples provided.
watch_project ~83
Add a project to your pipeline (or update its stage). Stages: interested, diligence, intro_requested, passed, invested. Optional notes are appended to the watch's note log. (requires API key)
| Name | Type | Req | Description |
|---|---|---|---|
| notes | string | — | Optional note to append (max 4000 chars) |
| slug | string | yes | Project slug |
| stage | string | — | — |
No output schema declared.
No examples provided.