ActionDock
REMOTE · ACTIONDOCK.APP · SCANNED SEP 24
Supervised API-write gateway for AI agents with policy, human approval and execution receipts.
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 → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1256 tokens (~139/item across 9 items; 8 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the ActionDock MCP server?
ActionDock is a hosted endpoint at https://actiondock.app/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.
remote · actiondock.app
claude mcp add --transport http app-actiondock-actiondock 'https://actiondock.app/mcp'
{
"mcpServers": {
"app-actiondock-actiondock": {
"url": "https://actiondock.app/mcp"
}
}
} {
"servers": {
"app-actiondock-actiondock": {
"type": "http",
"url": "https://actiondock.app/mcp"
}
}
} [mcp_servers.app-actiondock-actiondock] url = "https://actiondock.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-actiondock-actiondock": {
"type": "remote",
"url": "https://actiondock.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-actiondock-actiondock --url 'https://actiondock.app/mcp' --transport streamable-http
mcp_servers:
app-actiondock-actiondock:
url: "https://actiondock.app/mcp" {
"McpServers": {
"app-actiondock-actiondock": {
"Transport": "http",
"Url": "https://actiondock.app/mcp"
}
}
} assistant mcp add app-actiondock-actiondock -t streamable-http -u 'https://actiondock.app/mcp'
{
"mcpServers": {
"app-actiondock-actiondock": {
"type": "http",
"url": "https://actiondock.app/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.
- 24 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 22 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- 21 Sept 26 +41
- HSTS header: pass → fail ▼ security
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- 10 Sept 26 36
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 24 Sept 2026 · Probed https://actiondock.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=actiondock.app | CN=YE2,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 508f4770c1157c9211ff9b59ada4c175052 |
| SANs: actiondock.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of actiondock.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| actiondock.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="actiondock"
Bearer realm="actiondock"Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://actiondock.app/mcp | Verified | 200 | |
| http (plaintext) | http://actiondock.app/mcp | HTTPS enforced | 301 | https://actiondock.app/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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_job Get job ~33
Get the current status and result of an action job.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Job identifier returned by run_action. |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Catalog action name, for example integration.execute. |
| approvedAt | – | yes | – |
| approvedBy | – | yes | Owner who approved the write. |
| createdAt | string | yes | Creation time. |
| error | – | yes | Failure or execution_unknown message; null otherwise. |
| id | string | yes | Job identifier. |
| idempotencyKey | – | yes | Idempotency key that deduplicates this submission within the workspace. |
| input | object | yes | Validated action input exactly as submitted. |
| output | – | yes | While awaiting_approval: the exact approval preview bound to the owner's decision. After succeeded: the action result. After execution_unknown: the approved write plus the ambiguous provider response… |
| rejectedAt | – | yes | – |
| rejectedBy | – | yes | Owner who rejected the write. |
| sideEffect | boolean | yes | True when the action writes to an external system and therefore required owner approval. |
| status | string | yes | awaiting_approval, queued, and running are non-terminal; succeeded, failed, rejected, and execution_unknown are terminal. |
| updatedAt | string | yes | Last status change. |
| workflowId | – | yes | Caller-supplied workflow identifier shared across related jobs. |
| workflowName | – | yes | Caller-supplied workflow name shown in the dashboard. |
| workspaceId | string | yes | Workspace that owns the job. |
No examples provided.
list_actions List actions ~24
List every action available to the agent, including input schemas and side-effect flags.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | yes | Catalog entries with name, description, input schema, and side-effect flag. |
No examples provided.
list_connections List connections ~27
List the workspace-approved HTTPS API connections and their method/path allowlists. Credentials are never returned.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| connections | array | yes | Workspace-approved API connections with their method and path allowlists; credentials are never included. |
No examples provided.
list_events List events ~35
List recent job and callback events for workflow continuation and audit.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of most recent events to return. |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | Most recent job and callback events, newest first. |
No examples provided.
list_job_reconciliations Read owner reconciliation evidence ~95
Read the owner's append-only observations about an unknown write. These are owner reports, not verified provider facts, a changed job status, or permission to retry. Agents cannot record observations.
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | nextBefore from the previous page; omit for the newest observations. |
| job_id | string | yes | Job identifier returned by run_action. |
| limit | integer | – | Maximum observations per page, newest first. |
| Name | Type | Req | Description |
|---|---|---|---|
| nextBefore | – | yes | Pass as before to read older records; null means the end of history. |
| records | array | yes | Owner observations, newest first; corrections append to history. |
No examples provided.
list_usage List usage ~38
List metered action debits and the current UTC-month usage total.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of most recent usage records to return. |
| Name | Type | Req | Description |
|---|---|---|---|
| records | array | yes | Most recent metered action debits, newest first. |
| summary | object | yes | Current UTC-month usage total and plan limit. |
No examples provided.
run_action Submit action job ~145
Create an action job. External writes always wait for workspace-owner approval in the dashboard; the owner is emailed, and wait_for_job blocks until the decision.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Catalog action name from list_actions, for example integration.execute. |
| idempotency_key | string | – | Caller-chosen key; resubmitting the same key and input returns the existing job instead of creating another. |
| input | object | – | Action input matching the schema advertised by list_actions. |
| workflow_id | string | – | Stable identifier of the agent workflow this job belongs to, for grouping events. |
| workflow_name | string | – | Human-readable workflow name shown to the workspace owner during review. |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Catalog action name, for example integration.execute. |
| approvedAt | – | yes | – |
| approvedBy | – | yes | Owner who approved the write. |
| createdAt | string | yes | Creation time. |
| error | – | yes | Failure or execution_unknown message; null otherwise. |
| id | string | yes | Job identifier. |
| idempotencyKey | – | yes | Idempotency key that deduplicates this submission within the workspace. |
| input | object | yes | Validated action input exactly as submitted. |
| output | – | yes | While awaiting_approval: the exact approval preview bound to the owner's decision. After succeeded: the action result. After execution_unknown: the approved write plus the ambiguous provider response… |
| rejectedAt | – | yes | – |
| rejectedBy | – | yes | Owner who rejected the write. |
| sideEffect | boolean | yes | True when the action writes to an external system and therefore required owner approval. |
| status | string | yes | awaiting_approval, queued, and running are non-terminal; succeeded, failed, rejected, and execution_unknown are terminal. |
| updatedAt | string | yes | Last status change. |
| workflowId | – | yes | Caller-supplied workflow identifier shared across related jobs. |
| workflowName | – | yes | Caller-supplied workflow name shown in the dashboard. |
| workspaceId | string | yes | Workspace that owns the job. |
No examples provided.
wait_for_job Wait for job ~113
Wait for an action job to reach a decision or a final state: approved and executed, rejected, failed, or execution_unknown. A job still awaiting owner approval when the timeout elapses is returned as awaiting_approval; call again to keep waiting. Keep timeout_seconds below your client's tool timeout.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Job identifier returned by run_action. |
| timeout_seconds | integer | – | How long to wait for a decision or final state before returning the current job; keep it below your client's tool timeout. |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Catalog action name, for example integration.execute. |
| approvedAt | – | yes | – |
| approvedBy | – | yes | Owner who approved the write. |
| createdAt | string | yes | Creation time. |
| error | – | yes | Failure or execution_unknown message; null otherwise. |
| id | string | yes | Job identifier. |
| idempotencyKey | – | yes | Idempotency key that deduplicates this submission within the workspace. |
| input | object | yes | Validated action input exactly as submitted. |
| output | – | yes | While awaiting_approval: the exact approval preview bound to the owner's decision. After succeeded: the action result. After execution_unknown: the approved write plus the ambiguous provider response… |
| rejectedAt | – | yes | – |
| rejectedBy | – | yes | Owner who rejected the write. |
| sideEffect | boolean | yes | True when the action writes to an external system and therefore required owner approval. |
| status | string | yes | awaiting_approval, queued, and running are non-terminal; succeeded, failed, rejected, and execution_unknown are terminal. |
| updatedAt | string | yes | Last status change. |
| workflowId | – | yes | Caller-supplied workflow identifier shared across related jobs. |
| workflowName | – | yes | Caller-supplied workflow name shown in the dashboard. |
| workspaceId | string | yes | Workspace that owns the job. |
No examples provided.
What is the ActionDock MCP server?
ActionDock is an MCP server listed in the public MCP registry as app.actiondock/actiondock. Supervised API-write gateway for AI agents with policy, human approval and execution receipts. This page covers its hosted endpoint (https://actiondock.app/mcp).
Is the ActionDock MCP server safe to use?
ActionDock scores 77 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 ActionDock MCP server expose?
ActionDock exposes 8 tools: list_actions, run_action, get_job, list_job_reconciliations, wait_for_job, and 3 more. Their descriptions and schemas cost roughly 510 tokens of context every time the server is loaded.
Does the ActionDock MCP server require authentication?
Yes. ActionDock asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the ActionDock MCP server still maintained?
ActionDock is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.