---
name: hiveround-marketplace
description: Browse live startup raises on Hiveround and request intros to founders through the Hiveround MCP server.
version: 1.0.0
author: Hiveround
license: MIT
metadata:
  hermes:
    tags: [VC, Dealflow, Investing, MCP, Marketplace]
required_environment_variables:
  - name: HIVEROUND_API_KEY
    prompt: Hiveround API key (hr_sk_...)
    help: Generate one at https://hiveround.com/mcp. Read-only tools work without it.
    required_for: Requesting intros, managing watches, and reading intro threads
---

# Hiveround

Hiveround is a marketplace for live startup raises. Founders post their pitch
as markdown; investors point their agents at the marketplace and let them do
the first read.

This skill wires Hermes into the public Hiveround MCP server so the agent can
search the marketplace, watch deals, and queue intros on the user's behalf.

## When to use

Load this skill when the user:
- asks to find a startup raising on Hiveround
- mentions a Hiveround project slug or a `hiveround.com` URL
- wants to watch or track a Hiveround project in their pipeline
- wants to request an intro to a founder on Hiveround
- asks for stats about the Hiveround marketplace

## Setup (one-time)

Add this block to `~/.hermes/config.yaml`:

```yaml
mcp_servers:
  hiveround:
    url: https://hiveround.com/api/mcp
    headers:
      Authorization: "Bearer ${HIVEROUND_API_KEY}"
```

Then run `/reload-mcp` (or restart Hermes). The Hiveround tools will appear
under the `mcp_hiveround_*` namespace.

`HIVEROUND_API_KEY` is optional — read-only tools (`list`, `search`,
`get`) work without auth. Generate a key at https://hiveround.com/mcp to unlock writes
(intros, watches, threads).

## Quick reference

| Task | Tool | Auth |
|---|---|---|
| Newest live raises | `mcp_hiveround_list_projects` | none |
| Filter by stage / keyword / max raise | `mcp_hiveround_search_projects` | none |
| Full pitch by slug | `mcp_hiveround_get_project` | none |
| Open a thread with a founder | `mcp_hiveround_request_intro` | API key |
| Add to your pipeline | `mcp_hiveround_watch_project` | API key |
| Move stage / append a note | `mcp_hiveround_update_watch` | API key |
| List your pipeline | `mcp_hiveround_list_watches` | API key |
| List intro threads | `mcp_hiveround_list_intros` | API key |
| Read a thread | `mcp_hiveround_read_intro_thread` | API key |
| Follow up in a thread | `mcp_hiveround_send_intro_message` | API key |

## Procedure

### Browse the marketplace

1. Use `mcp_hiveround_search_projects` with the user's filters (stage, max
   raise, keywords). Use `mcp_hiveround_list_projects` for the newest live
   raises if no filter is specified.
2. For each project that looks relevant, call `mcp_hiveround_get_project`
   with the slug to read the full pitch markdown.
3. Summarize in the user's preferred format. Always include the slug and the
   live URL: `https://hiveround.com/p/<slug>`.

### Watch a project

1. Confirm the user wants to add the project to their pipeline.
2. Call `mcp_hiveround_watch_project` with the slug and an initial stage
   (e.g. `tracking`, `meeting_set`, `passed`).
3. Use `mcp_hiveround_update_watch` to move stages or append notes later.

### Request an intro

1. Read the project first (`mcp_hiveround_get_project`) so the opening
   message can reference specifics from the pitch.
2. Call `mcp_hiveround_request_intro` with the slug and a short, specific
   first message: who the user is, why they're a fit for this round, and the
   next step they're proposing.
3. Track follow-ups with `mcp_hiveround_read_intro_thread` and
   `mcp_hiveround_send_intro_message`.

## Pitfalls

- **Slug, not URL.** Pass the slug (e.g. `hiveround`) to the tools — not
  the full URL. Strip `https://hiveround.com/p/` if it's all you have.
- **Anonymous limits.** Without an API key, write tools (`request_intro`,
  `watch_*`, `*_intro_*`) will fail with an auth error. Point the user at
  https://hiveround.com/mcp to generate one.
- **Never send a generic intro.** `request_intro` creates a thread the
  founder reads. If the user hasn't given you a specific reason for the
  intro, ask before sending.
- **Live data.** The marketplace is live — projects can close between
  calls. Re-fetch with `mcp_hiveround_get_project` before acting on stale
  info.

## Verification

After a write, confirm it landed:
- `request_intro` → `mcp_hiveround_list_intros` shows the new thread.
- `watch_project` / `update_watch` → `mcp_hiveround_list_watches`
  shows the project at the expected stage.

## Fallback: raw JSON-RPC

If MCP isn't wired up, the same tools are reachable as JSON-RPC 2.0 over
HTTP at `https://hiveround.com/api/mcp`. Use the `terminal` tool with curl:

```bash
curl -X POST https://hiveround.com/api/mcp \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $HIVEROUND_API_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_projects","arguments":{"limit":5}}}'
```

## More

- Setup guide: https://hiveround.com/mcp
- Marketplace summary for agents: https://hiveround.com/llms.txt
- API catalog: https://hiveround.com/.well-known/api-catalog
- MCP server card: https://hiveround.com/.well-known/mcp/server-card.json