Agent Enhancer Utilities
REMOTE · LIBERATED.SITE · SCANNED OCT 10
Workflow planning, recovery checkpoints, coordination, fixtures, and compatibility tools for agents.
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 408 tokens (~68/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage69
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 6% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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 Agent Enhancer Utilities MCP server?
Agent Enhancer Utilities is a hosted endpoint at https://liberated.site/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 · liberated.site
claude mcp add --transport http site-liberated-agent-utility-lab 'https://liberated.site/mcp'
{
"mcpServers": {
"site-liberated-agent-utility-lab": {
"url": "https://liberated.site/mcp"
}
}
} {
"servers": {
"site-liberated-agent-utility-lab": {
"type": "http",
"url": "https://liberated.site/mcp"
}
}
} [mcp_servers.site-liberated-agent-utility-lab] url = "https://liberated.site/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"site-liberated-agent-utility-lab": {
"type": "remote",
"url": "https://liberated.site/mcp",
"enabled": true
}
}
} openclaw mcp add site-liberated-agent-utility-lab --url 'https://liberated.site/mcp' --transport streamable-http
mcp_servers:
site-liberated-agent-utility-lab:
url: "https://liberated.site/mcp" {
"McpServers": {
"site-liberated-agent-utility-lab": {
"Transport": "http",
"Url": "https://liberated.site/mcp"
}
}
} assistant mcp add site-liberated-agent-utility-lab -t streamable-http -u 'https://liberated.site/mcp'
{
"mcpServers": {
"site-liberated-agent-utility-lab": {
"type": "http",
"url": "https://liberated.site/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.
- 10 Oct 26 +55
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- HTTPS: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Authorization: fail → partial ▲ security
- HSTS header: fail → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +5
- Endpoint reachability: not serving MCP → behind authorisation ▼ security
- Authorization: unverified → fail ▼ security
- Transport: fail → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- 19 Sept 26 −53
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.53 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 17 Sept 26 −7
- Stability: pass → 0.50 functional
- 2 Sept 26 0
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Destructive annotations: pass functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 10 Oct 2026 · Probed https://liberated.site/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=liberated.site | CN=WE1,O=Google Trust Services,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f9f987ebe023918c139024a5aa411a29 |
| SANs: liberated.site, *.liberated.site | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of liberated.site. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| site. | present | 31826 | 13 | Verified |
| liberated.site. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; base-uri 'self'; connect-src 'self'; form-action 'self'; frame-ancestors 'none'; img-src 'self' data:; media-src 'self'; object-src 'none'; script-src 'self' 'unsafe-inline'; script-src-attr 'none'; style-src 'self' 'unsafe-inline'; worker-src 'self' blob:; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://liberated.site/mcp | Verified | 200 | |
| http (plaintext) | http://liberated.site/mcp | HTTPS enforced | 308 | https://liberated.site/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 →
lab.describe_tool Describe an agent utility ~37
Get the exact schema, price, limits, side effects, retention, and HTTP endpoint for one utility.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
lab.get_capability_request Get capability request status ~39
Poll a previously submitted capability request with its private status token.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
| status_token | string | yes | – |
No output schema declared.
No examples provided.
lab.invoke_tool Invoke an agent utility ~73
Invoke a free utility directly. For paid utilities, returns the HTTP endpoint and payment requirement so an x402-capable client can complete the call.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Stable identifier required for side-effecting tools and safe retries. |
| input | object | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
lab.list_tools List agent utilities ~26
List all currently discoverable utilities. Prefer search_tools when a concrete intent is known.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lab.request_capability Request a missing capability ~105
Submit a free, private backlog request when no existing utility solves a concrete problem. Do not include secrets, personal data, or full conversation history.
| Name | Type | Req | Description |
|---|---|---|---|
| client_request_id | string | – | – |
| constraints | object | – | – |
| desired_outcome | string | yes | – |
| evidence_urls | array | – | – |
| example_input | object | – | – |
| expected_output | object | – | – |
| problem | string | yes | – |
| why_existing_tools_fail | string | yes | – |
No output schema declared.
No examples provided.
lab.search_tools Search agent utilities ~41
Find Agent Enhancer Utilities tools that match a concrete intent. Returns compact machine-readable manifests.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| intent | string | yes | – |
No output schema declared.
No examples provided.
What is the Agent Enhancer Utilities MCP server?
Agent Enhancer Utilities is an MCP server listed in the public MCP registry as site.liberated/agent-utility-lab. Workflow planning, recovery checkpoints, coordination, fixtures, and compatibility tools for agents. This page covers its hosted endpoint (https://liberated.site/mcp).
Is the Agent Enhancer Utilities MCP server safe to use?
Agent Enhancer Utilities scores 83 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 Agent Enhancer Utilities MCP server expose?
Agent Enhancer Utilities exposes 6 tools: lab.search_tools, lab.describe_tool, lab.invoke_tool, lab.request_capability, lab.get_capability_request, lab.list_tools. Their descriptions and schemas cost roughly 321 tokens of context every time the server is loaded.
Does the Agent Enhancer Utilities MCP server require authentication?
No. We connected to Agent Enhancer Utilities without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Enhancer Utilities MCP server still maintained?
Agent Enhancer Utilities is still listed as active in the MCP registry. We last reached this channel on 10 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.