Skip to content

Hydracept MCP server

com.hydracept/hydracepthydracept.comstreamable-httpv0.5.7Scanned

Directory-safe MCP: quote and run text/domain jobs with OAuth, receipts, BYOK.

11 tools: 1 can delete or cancel things, 2 change things and 8 only read.

Tools: 1 delete, 0 irreversible, 2 write, 8 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • 1 finding

Sign-in required, OAuth metadata published. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Hydracept MCP server can do

The Hydracept MCP server is published by hydracept.com, a domain the MCP Registry verified. It has 11 tools. It can delete or cancel things (1 tool: hydracept_cancel_job) and create or change data (2 tools: hydracept_run and hydracept_submit_job). 8 tools only read.

4 tools bring in text other people can write (hydracept_capabilities, hydracept_run, hydracept_submit_job and 1 more).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint asks for sign-in and publishes OAuth metadata.

Last scanned Nov 10, 2026, version 0.5.7.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Deletes or cancels 1Claude Code: deny
  • hydracept_cancel_jobRequest cancellation of one job.Reads text others write1 finding

    Why it is in this group

    • The name "hydracept_cancel_job" says "cancel": a word for removing or ending something.
    • The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "hydracept_cancel_job" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "hydracept_cancel_job" says "cancel": a word for removing or ending something.

      What this check looks for
    Description, as the server wrote it
    Request cancellation of one job. Use only when the user explicitly asks to cancel the job itself; stopping a local polling loop is not a cancellation. Returns whether the request was accepted, whether the job is already terminal, and the next action. Never promise that upstream provider work stopped or that already-incurred cost is refunded. Safe to retry: a terminal job reports its terminal state. Requires bearer key. Returns: Cancellation outcome envelope with job status, terminal flag, and next action. Errors: WORKSPACE_KEY_REQUIRED, NOT_FOUND, INVALID_ARGUMENT.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: false
    • title: Cancel a job
Changes things 2Claude Code: ask
  • hydracept_runRun a capability (paid).Reads text others writeNo findings

    Why it is in this group

    • The name "hydracept_run" says "run": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Run a capability (paid). Use when the user wants execution — not for quotes (hydracept_quote_capability), status (hydracept_job_status), or receipts (hydracept_get_receipt). Default wait=true waits until the job finishes; use hydracept_submit_job when this call must return immediately. Picks invoke vs durable job from the capability descriptor. Requires bearer key. Settles at actual provider cost plus any managed service fee; no per-call minimum. May create jobs, artifacts, and provider usage. Returns: Terminal hydracept.run-result.v1 or job envelope when wait=false. Errors: WORKSPACE_KEY_REQUIRED, INVALID_ARGUMENT, FundingRequired, EXECUTION_FAILED, job timeout when wait exhausts.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
    • title: Run a capability
  • hydracept_submit_jobStart a capability job and return its id immediately (paid).Reads text others writeNo findings

    Why it is in this group

    • The name "hydracept_submit_job" says "submit": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Start a capability job and return its id immediately (paid). Use when execution is required but this MCP call must not block — not for quotes or status checks. Prefer hydracept_run when waiting is acceptable. Poll with hydracept_job_status. Same billing as hydracept_run. Requires bearer key. Returns: Job admission envelope with jobId and nextAction poll. Errors: WORKSPACE_KEY_REQUIRED, INVALID_ARGUMENT, FundingRequired, EXECUTION_FAILED.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
    • title: Submit a durable job
Only reads 8Show 8 read-only tools
  • hydracept_capabilitiesBrowse or fetch capability descriptors (keys, modes, schemas).Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "browse": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Browse or fetch capability descriptors (keys, modes, schemas). Use hydracept_resolve_capability when routing from intent alone. List/resolve is keyless; a bearer key may add project-scoped fields. No charge. Read-only. Returns: Capability list or single CapabilityDescriptor when key is set. Errors: NOT_FOUND for unknown key; INVALID_ARGUMENT for conflicting query parameters.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: List capabilities
  • hydracept_download_artifactFetch artifact metadata (and SHA-256 on hosted MCP) for a succeeded job output.No findings

    Why it is in this group

    • The description's first verb is "fetch": a word for reading.
    Description, as the server wrote it
    Fetch artifact metadata (and SHA-256 on hosted MCP) for a succeeded job output. Stdio may also write bytes when output_path is set. Requires bearer key. No charge on hosted. Returns: Artifact downloadUrl, mediaType, sha256 (hosted does not write local files). Errors: WORKSPACE_KEY_REQUIRED, NOT_FOUND, DIRECTORY_CAPABILITY_DENIED when policy blocks.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Read artifact metadata
  • hydracept_get_receiptRead billing and provenance for a finished job.No findings

    Why it is in this group

    • The name "hydracept_get_receipt" says "get": a word for reading.
    Description, as the server wrote it
    Read billing and provenance for a finished job. Does not run capabilities or spend money. Use after terminal success; use hydracept_job_status while still running. Hosted MCP accepts job_id only. Requires bearer key. No charge. Returns: HydraceptReceipt JSON for a terminal job. Errors: WORKSPACE_KEY_REQUIRED, NOT_FOUND when job or receipt is missing.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Read a receipt
  • hydracept_job_statusRead one job's current status.No findings

    Why it is in this group

    • The name "hydracept_job_status" says "status": a word for reading.
    Description, as the server wrote it
    Read one job's current status. Use after hydracept_submit_job or hydracept_run with wait=false; use hydracept_get_receipt after success. If the job id is unknown, use hydracept_jobs_find first. Requires bearer key. No charge. Returns: HydraceptJob status projection for the jobId. Errors: WORKSPACE_KEY_REQUIRED, NOT_FOUND.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Read job status
  • hydracept_jobs_findFind a prior job in the bound project when you do not have its id.No findings

    Why it is in this group

    • The name "hydracept_jobs_find" says "find": a word for reading.
    Description, as the server wrote it
    Find a prior job in the bound project when you do not have its id. intent is recent, failed, or reusable. The list never includes prompt text. Use after context loss, for failure triage, or to recover a job to cancel. Requires bearer key. No charge. Read-only. Returns: Matching job summaries for the filter. Errors: WORKSPACE_KEY_REQUIRED, INVALID_ARGUMENT.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Find a prior job
  • hydracept_quote_capabilityPreview what a run would cost — does not execute, create a job, or charge the wallet.No findings

    Why it is in this group

    • The description's first verb is "preview": a word for reading.
    Description, as the server wrote it
    Preview what a run would cost — does not execute, create a job, or charge the wallet. Use before spending when the user asks about price; use hydracept_run or hydracept_submit_job only to execute. Not the same as request_capability_quote (POST /mcp/full) on the full profile (human-paid capability commission). Requires bearer API key. No charge for the quote itself. Returns: Quote envelope with customerTotal and currency (no wallet charge). Errors: WORKSPACE_KEY_REQUIRED, INVALID_ARGUMENT, NOT_FOUND, FundingRequired when quote cannot be priced.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Quote a capability
  • hydracept_resolve_capabilityMatch the user's goal to a capability key using natural language.No findings

    Why it is in this group

    • The name "hydracept_resolve_capability" says "resolve": a word for reading.
    Description, as the server wrote it
    Match the user's goal to a capability key using natural language. Use when the key is unknown; use hydracept_capabilities when you already have a key or need the catalog. Keyless. No charge. Read-only. Returns: CapabilityResolutionResponse with ranked keys and rationale. Errors: INVALID_ARGUMENT when intent is empty; UNAUTHORIZED when bearer is invalid.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Resolve a capability
  • hydracept_workspace_statusCheck workspace/session authentication and readiness, plus common setup errors.No findings

    Why it is in this group

    • The name "hydracept_workspace_status" says "status": a word for reading.
    Description, as the server wrote it
    Check workspace/session authentication and readiness, plus common setup errors. Use when setup, auth, or project binding is in doubt; use hydracept_job_status for a specific execution. Does not execute capabilities or spend money. Hosted requires bearer (WORKSPACE_KEY_REQUIRED when missing); stdio checks local project binding. Not a substitute for hydracept_capabilities. Returns: Workspace/session authentication and readiness diagnostics for the authenticated principal. Errors: WORKSPACE_KEY_REQUIRED when bearer is missing on hosted MCP.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Workspace status

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 20, 2026, 18:40 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://api.hydracept.com/.well-known/oauth-protected-resource/mcp/claude
RFC 9728 protected resource metadata
https://api.hydracept.com/.well-known/oauth-protected-resource/mcp/claude
Authorization servers
https://api.hydracept.com/oauth/claude
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no

Posture changes

  1. Nov 13, 2026
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://api.hydracept.com/.well-known/oauth-protected-resource/mcp/claude
    • RFC 9728 protected resource metadata: none to https://api.hydracept.com/.well-known/oauth-protected-resource/mcp/claude
    • Authorization servers: none to https://api.hydracept.com/oauth/claude
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "hydracept_cancel_job" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "hydracept_cancel_job" says "cancel": a word for removing or ending something.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 3 -> 0 (and 7 more).View diff
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://api.hydracept.com/.well-known/oauth-protected-resource/mcp/claude
    • RFC 9728 protected resource metadata: none to https://api.hydracept.com/.well-known/oauth-protected-resource/mcp/claude
    • Authorization servers: none to https://api.hydracept.com/oauth/claude
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

Install

Pinned to version 0.5.7. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__hydracept__hydracept_workspace_status",
      "mcp__hydracept__hydracept_capabilities",
      "mcp__hydracept__hydracept_resolve_capability",
      "mcp__hydracept__hydracept_quote_capability",
      "mcp__hydracept__hydracept_job_status",
      "mcp__hydracept__hydracept_get_receipt",
      "mcp__hydracept__hydracept_download_artifact",
      "mcp__hydracept__hydracept_jobs_find"
    ],
    "ask": [
      "mcp__hydracept__hydracept_run",
      "mcp__hydracept__hydracept_submit_job"
    ],
    "deny": [
      "mcp__hydracept__hydracept_cancel_job"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as hydracept. Review it before you use it.

Capability tags behind 4 rules
  • mcp__hydracept__hydracept_capabilities untrusted-input
  • mcp__hydracept__hydracept_run untrusted-input
  • mcp__hydracept__hydracept_submit_job untrusted-input
  • mcp__hydracept__hydracept_cancel_job untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.hydracept/hydracept/verify?hash=eb6fd62515dd9cb2cfa46c9d370d9ffd9ba6d57f47be87ef21f1d330ddfd86b9" | jq -e '.changed == false'

Pinned hash eb6fd62515dd, from Nov 10, 2026, 01:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.hydracept/hydracept/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.hydracept/hydracept
[![Anlyon Radar](https://radar.anlyon.com/badge/com.hydracept/hydracept.svg)](https://radar.anlyon.com/servers/com.hydracept/hydracept)

Source: MCP Registry · repository. Synced Nov 13, 2026, 03:17 UTC.

Hydracept MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Hydracept MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Hydracept MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: hydracept_cancel_job.

Can the Hydracept MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Hydracept MCP server have?

11 tools: 1 destructive, 2 write, 8 read. hydracept_cancel_job, hydracept_run, hydracept_submit_job, hydracept_workspace_status, hydracept_capabilities, hydracept_resolve_capability, hydracept_quote_capability, hydracept_job_status and 3 more.

Does the Hydracept MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.

Does the Hydracept MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Hydracept MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.