Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add hive-intel/hive-sdk --skill hive-mcpgit clone --depth 1 https://github.com/hive-intel/hive-sdkWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hive-intel/hive-sdk/hive-mcp)<a href="https://agentmods.dev/skills/hive-intel/hive-sdk/hive-mcp"><img src="https://agentmods.dev/badge/skills/hive-intel/hive-sdk/hive-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hive-intel/hive-sdk/hive-mcp"><img src="https://agentmods.dev/badge/skills/hive-intel/hive-sdk/hive-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 44 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 129 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 60 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Excessive Agency · line 108 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium MCP Rug Pull · line 126 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00106 | $0.02082 |
| Opus 5.5 | $0.00042 | $0.00833 |
| Sonnet 5.5 | $0.00021 | $0.00416 |
| Haiku 4.5 | $0.00011 | $0.00208 |
Grade A, and why
hive-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hive-mcp — Add Hive to an MCP Client
Walk the user through adding Hive's MCP endpoint to whichever AI client they're using. The endpoint is the same everywhere; only the config file path and shape vary per client.
Universal facts
- MCP URL —
https://mcp.hiveintelligence.xyz/mcp - Transport — Streamable HTTP (single endpoint, supports both POST and GET; SSE is legacy)
- Auth — after hosted OAuth activation, interactive remote clients use
URL-only OAuth 2.1 discovery and browser consent. Headless backends may send
Authorization: Bearer <HIVE_API_KEY>from secret storage;x-api-keyis a legacy fallback. Check protected-resource metadata before claiming the interactive path is live. - Cost — discovery tools are free; every other tool costs one credit.
Keyed lanes debit only after validation and client resolution, so a
validation error or missing provider key costs 0, and a call that fails
after the debit is refunded, so only a call that succeeds costs 1. The
keyless lane takes one allowance call per material request and gives it back
when the call fails. Every material response reports
credit_cost,credits_used, andcredits_remaining.
After hosted OAuth activation, interactive MCP setup does not require the user
to create or paste an API key. Route to hive-build-onboarding for direct CLI,
REST, headless access, or the temporary fallback while OAuth metadata is not
available.
Fast path — one command
If the user is on a machine with multiple MCP-capable clients and just wants Hive everywhere:
npx -y -p hive-intelligence@latest hive init --all --skip-verify
--skip-verify keeps it non-interactive; add --browser to sign in too.
This writes URL-only config for supported local clients and prints the native
UI steps for clients such as Claude and ChatGPT. When protected-resource
metadata is live, each interactive client opens Hive browser authorization on
first connect. Until then, do not present that path as installed; use the
trusted API-key fallback or wait for activation. Codex and headless OpenAI
Responses API setups remain explicit: Codex uses codex mcp add followed by
codex mcp login, while the headless Responses API uses an environment-backed
credential.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago Changed · +7 lines f4124722ec30
- 1mo ago Changed · +1 lines cf8ece0fb7f7
- 1mo ago Changed · +4 lines 63967c5e327d
- 1mo ago First seen · 170 lines · 106 tokens per session scan A f721df978830
hive-mcp is a skill published in the GitHub repository hive-intel/hive-sdk (20 stars, last pushed yesterday), licensed MIT. It adds 106 tokens to every session and 2,082 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
palisade-security-scanner
Onchain security scanner on Robinhood Chain — scan token approvals, detect honeypots, analyze contracts for rugpull indicators, check liquidity locks, and score contract safety. Use when a user asks an agent to evaluate, scan, or check a token or wallet before trading, swapping, signing an approval, or investing. 18…
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.clientCapabilities, ctx.enrich, ctx.content), and when to use each.
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.