# Hydracept (remote · api.hydracept.com)

Execution control plane for agents: capabilities, durable jobs, budgets, receipts, and BYOK.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `api.hydracept.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/com-hydracept-hydracept/api.md), [page](https://verifymcp.io/servers/com-hydracept-hydracept/api)
- pypi · `hydracept`: 53/100, [markdown](https://verifymcp.io/servers/com-hydracept-hydracept/hydracept.md), [page](https://verifymcp.io/servers/com-hydracept-hydracept/hydracept)

## Channel facts

- Endpoint: `https://api.hydracept.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.4`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 35 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 2311 tokens (~64/item across 36 items; 35 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 35 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 37 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Hydracept MCP server?

Hydracept is a hosted endpoint at https://api.hydracept.com/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.

### Claude

```bash
claude mcp add --transport http com-hydracept-hydracept 'https://api.hydracept.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-hydracept-hydracept": {
      "url": "https://api.hydracept.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-hydracept-hydracept": {
      "type": "http",
      "url": "https://api.hydracept.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-hydracept-hydracept]
url = "https://api.hydracept.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hydracept-hydracept": {
      "type": "remote",
      "url": "https://api.hydracept.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-hydracept-hydracept --url 'https://api.hydracept.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-hydracept-hydracept:
    url: "https://api.hydracept.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-hydracept-hydracept": {
      "Transport": "http",
      "Url": "https://api.hydracept.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-hydracept-hydracept -t streamable-http -u 'https://api.hydracept.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-hydracept-hydracept": {
      "type": "http",
      "url": "https://api.hydracept.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-29 (score 67, +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.

### 2026-09-28 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-26 (score 65)

First indexed and scored.

## MCP tools (35)

### `hydracept_status` (~25 tokens)

Session diagnostics for the authenticated API key.

Input parameters:

- `refresh` (boolean)

### `hydracept_capabilities` (~57 tokens)

List, find, or describe capabilities. Includes one-shot readiness facts. Text job_async descriptors may include features.deferredProcessing (50% off standard token rates).

Input parameters:

- `key` (string)
- `query` (string)

### `resolve_capability` (~37 tokens)

Determine whether Hydracept already provides a suitable capability. Does not spend money.

Input parameters:

- `intent` (string, required)
- `requirements`

### `hydracept_quote_capability` (~59 tokens)

POST /v1/capabilities/{key}/quote. Does not reserve or charge funds. 'input' is an alias for 'body'.

Input parameters:

- `body`
- `capability_key` (string, required)
- `input`

### `estimate_capability` (~55 tokens)

HTTP alias of hydracept_quote_capability. Same 0.3 retail quote. 'input' is an alias for 'body'.

Input parameters:

- `body`
- `capability_key` (string, required)
- `input`

### `hydracept_invoke` (~52 tokens)

Invoke a synchronous capability (read-only domain/DNS and text). 'input' is an alias for 'body'.

Input parameters:

- `body`
- `capability_key` (string, required)
- `input`

### `hydracept_run` (~87 tokens)

hydracept.run-result.v1 over hosted HTTP. Artifact persist requires stdio MCP in a checkout. 'input' is an alias for 'body'.

Input parameters:

- `body`
- `capability_key` (string, required)
- `idempotency_key` (string)
- `input`
- `max_cost`
- `timeout`
- `wait` (boolean)

### `request_capability_quote` (~35 tokens)

Create a capability REQUEST. Commission quotes are human-paid and must not be used as execution.quoteId.

Input parameters:

- `body`

### `get_capability_request_quote` (~38 tokens)

Read the human-paid commission quote for a capability request.

        Never an execution.quoteId.

Input parameters:

- `request_id` (string, required)

### `hydracept_submit_job` (~86 tokens)

Submit a capability job. Omit quoteId; the API seals pricing at admission. Eligible durable text jobs use deferred processing at 50% of standard token rates. Returns nextAction. 'input' is an alias for 'body'.

Input parameters:

- `body`
- `capability_key` (string, required)
- `idempotency_key` (string)
- `input`

### `hydracept_job_status` (~44 tokens)

GET /v1/jobs/{jobId} once. If nextAction is poll, wait pollAfterSeconds and call again.

Input parameters:

- `job_id` (string, required)

### `hydracept_get_receipt` (~28 tokens)

Fetch sealed receipt summary for a job.

Input parameters:

- `job_id` (string, required)

### `hydracept_download_artifact` (~45 tokens)

Return artifact download metadata and content hash (hosted MCP does not write local files).

Input parameters:

- `artifact_id` (string, required)
- `job_id` (string, required)

### `hydracept_smoke` (~64 tokens)

Explicit managed-trial smoke. Same contract as stdio: generation, pricing, SHA-256, PNG alpha.

Input parameters:

- `capability` (string)
- `output_path` (string)
- `poll_seconds` (integer)
- `prompt` (string)

### `hydracept_pinned_run` (~81 tokens)

POST /v1/inference/pinned — exact pin, scientific receipt. Standard processing by default. Opt in with processing=deferred on eligible OpenAI Responses pins (50% Flex). One logical model execution, no truncation rewrite, no Flex→Standard fallback. Pre-inference capacity 429s may retry.

Input parameters:

- `body`

### `hydracept_pinned_bulk` (~37 tokens)

POST /v1/inference/pinned/bulk — concurrent pinned items, one logical execution each.

Input parameters:

- `body`

### `hydracept_pinned_get` (~32 tokens)

GET /v1/inference/pinned/{receipt_id}.

Input parameters:

- `receipt_id` (string, required)

### `hydracept_pinned_bulk_get` (~51 tokens)

GET /v1/inference/pinned/bulk/{bulk_id} once. If nextAction is poll, wait pollAfterSeconds and call again.

Input parameters:

- `bulk_id` (string, required)

### `hydracept_manifest_create` (~27 tokens)

POST /v1/provenance/manifests.

Input parameters:

- `body`

### `hydracept_manifest_verify` (~35 tokens)

POST /v1/provenance/manifests/{manifest_id}/verify.

Input parameters:

- `manifest_id` (string, required)

### `hydracept_lockfile_emit` (~35 tokens)

GET /v1/provenance/lockfile?receipt_id=.

Input parameters:

- `receipt_id` (string, required)

### `hydracept_verify_lockfile` (~30 tokens)

POST /v1/provenance/lockfile/verify.

Input parameters:

- `body`

### `hydracept_jobs_find` (~59 tokens)

Find recent, failed, or reusable project jobs without asking the human for a job id.

Input parameters:

- `capability_key` (string)
- `intent` (string)
- `limit` (integer)
- `project_id` (string)

### `hydracept_job_inspect` (~38 tokens)

Inspect error, diagnostics, receipt summary, request snapshot, and reuse candidate for one job.

Input parameters:

- `job_id` (string, required)

### `hydracept_project_request_operation` (~66 tokens)

POST a project operation. Hosted MCP does not run the customer repo; a local watcher must execute it.

Input parameters:

- `action_key` (string)
- `command` (string, required)
- `context`
- `input`
- `project_id` (string)

### `hydracept_project_get_operation` (~45 tokens)

Poll a project operation. Execution happens in the game checkout, not on this host.

Input parameters:

- `operation_id` (string, required)
- `project_id` (string)

### `hydracept_model_adapters` (~104 tokens)

Choose model adapters

List the bound project's registered model adapters, semantic aliases, image-generation default, and static routing readiness. Omitted project/environment arguments inherit the authenticated workspace binding. A registered adapter is not necessarily executable; require routingReadiness.routeCompatible before selecting it for generation. credentialAvailability=not_checked means credentials/capacity are still quote-time concerns. New agents should inspect project aliases before searching externally.

Input parameters:

- `environment` (string)
- `project_id` (string)

### `hydracept_prepare_adapter_selection` (~57 tokens)

Use adapter selection

Normalize a LoRA picker selection into the exact image.generate.v1 input.adapters contract. This does not submit or spend money. Use hydracept_model_adapters first and select only route-compatible entries.

Input parameters:

- `adapters`

### `hydracept_create_adapter_alias` (~87 tokens)

Create adapter alias

Create a stable semantic project alias for a registered adapter. Omitted project/environment arguments inherit the authenticated workspace binding. Catalog aliases may reference registrations that are not yet executable. Does not generate or spend money.

Input parameters:

- `adapter_id` (string, required)
- `alias` (string, required)
- `environment` (string)
- `project_id` (string)
- `weight`

### `hydracept_promote_adapter_alias` (~106 tokens)

Promote adapter alias

Explicitly move a semantic alias to a new registered adapter/weight by creating a new immutable alias version. Omitted project/environment arguments inherit the authenticated workspace binding. Existing recipe bindings do not move. An alias serving as an active generation default must remain route-compatible unless the default is cleared first.

Input parameters:

- `adapter_id` (string, required)
- `alias` (string, required)
- `environment` (string)
- `project_id` (string)
- `weight`

### `hydracept_bind_adapter_alias` (~97 tokens)

Pin adapter alias for recipe

Resolve a project alias to an immutable alias-version binding for persistence in a project recipe. Omitted project/environment arguments inherit the authenticated workspace binding. Omit version_id to pin the current version. Recipe pinning is allowed for catalog-only adapters; generation still requires a compatible route.

Input parameters:

- `alias` (string, required)
- `environment` (string)
- `project_id` (string)
- `version_id` (string)

### `hydracept_set_adapter_default` (~88 tokens)

Set project adapter default

Set a route-compatible semantic alias preselected for future image.generate.v1 work. Omitted project/environment arguments inherit the authenticated workspace binding. The default is not silently injected by the API; agents still send the resolved adapters[] selection.

Input parameters:

- `alias` (string, required)
- `capability_key` (string)
- `environment` (string)
- `project_id` (string)

### `hydracept_clear_adapter_default` (~77 tokens)

Clear project adapter default

Clear the project/environment image adapter default. Omitted project/environment arguments inherit the authenticated workspace binding. This does not alter the alias or its immutable history; clearing an environment override may reveal an inherited project-wide default.

Input parameters:

- `capability_key` (string)
- `environment` (string)
- `project_id` (string)

### `hydracept_register_model_adapter` (~245 tokens)

Register model adapter

Register a reusable project LoRA without generating or spending money. source_kind must be provider_ref, huggingface, or hydracept_artifact. For huggingface, source_ref is namespace/repository; source_file_path may identify an explicit public .safetensors file. If file path is omitted the repository is cataloged but remains non-executable. When a file path is supplied, Hydracept validates it and freezes the Hub commit. For hydracept_artifact, source_ref is a project artifactId and Hydracept binds its immutable content hash. For provider_ref, source_provider is required. Omitted project/environment arguments inherit the authenticated workspace binding. Inspect sourceHealth and routingReadiness.routeCompatible in the result before quoting generation.

Input parameters:

- `base_model_family` (string)
- `display_name` (string, required)
- `environment` (string)
- `project_id` (string)
- `recommended_weight`
- `source_file_path` (string)
- `source_kind` (string, required)
- `source_provider` (string)
- `source_ref` (string, required)
- `source_revision` (string)
- `trigger_words`

### `hydracept_revalidate_model_adapter` (~97 tokens)

Revalidate model adapter source

Re-check the frozen source identity for a registered adapter without generating or spending money. For Hugging Face this checks the already-pinned commit and file; it never advances a branch or tag. For Hydracept artifacts it rechecks immutable content and safetensors structure. Provider-native refs are opaque and remain declared. Use this when sourceHealth is stale, unavailable, or invalid.

Input parameters:

- `adapter_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-hydracept-hydracept/api#diagnostics

## Score history

- 2026-09-29: 67
- 2026-09-28: 66
- 2026-09-27: 66
- 2026-09-26: 65

## Common questions

### What is the Hydracept MCP server?

Hydracept is an MCP server listed in the public MCP registry as com.hydracept/hydracept. Execution control plane for agents: capabilities, durable jobs, budgets, receipts, and BYOK. This page covers its hosted endpoint (https://api.hydracept.com/mcp).

### Is the Hydracept MCP server safe to use?

Hydracept scores 67 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 Hydracept MCP server expose?

Hydracept exposes 35 tools: hydracept_status, hydracept_capabilities, resolve_capability, hydracept_quote_capability, estimate_capability, and 30 more. Their descriptions and schemas cost roughly 2,206 tokens of context every time the server is loaded.

### Does the Hydracept MCP server require authentication?

No. We connected to Hydracept without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Hydracept MCP server still maintained?

Hydracept is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.hydracept.com/mcp
- Repository: https://github.com/zencodeinc/hydracept-public
- Website: https://hydracept.com/plugin
- Changelog RSS feed: https://verifymcp.io/servers/com-hydracept-hydracept/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hydracept-hydracept/api.json
- HTML version of this page: https://verifymcp.io/servers/com-hydracept-hydracept/api