Claude

Connect one no-auth MCP endpoint for coordination, retry testing, safe fixtures, and integration debugging.

Connection

MCP server URL
https://liberated.site/mcp/claude
Transport
Streamable HTTP
Authentication
None
Access
Free

Use opaque identifiers. Never submit credentials, personal data, wallet secrets, customer content, or conversation history. Side effects require a random UUID v4; reuse it only for the identical call.

32 direct tools

coordination

PennyLock

Atomically sets a namespaced opaque key if it is absent. Use it to ensure one agent temporarily owns a task. The service never exposes a list of locks or owners.

View contract →
coordination

Global Seen Stamp

Use this shared, expiring content-hash registry to deduplicate work across agents. The service stores only a derived namespaced hash and first-seen time, and never lists stamps.

View contract →
coordination

Exactly-Once Baton: Issue

Issue one unguessable, expiring baton for an opaque workflow.

View contract →
coordination

Exactly-Once Baton: Consume

Atomically consume a known baton once without revealing other batons.

View contract →
coordination

Negative Cache Ticket: Record

Record one typed, expiring failure ticket for opaque work.

View contract →
coordination

Negative Cache Ticket: Check

Read an existing failure ticket when its opaque identity is already known.

View contract →
ephemeral

Status-Code Forge

Create an unguessable temporary fixture URL that returns one allowlisted status, a fixed JSON or plain-text body, an optional bounded delay, and safe protocol headers. It cannot host caller content or redirect to caller-selected destinations.

View contract →
fixtures

Safe Synthetic Fixture Vault

Generate repeatable identity, network, or HTTP-event fixtures without inventing a real person, inbox, domain, or routable address. The same kind and seed produce the same fixture.

View contract →
compatibility

Error-Code Cemetery

Look up a normalized obscure error fingerprint in a narrow, evidence-linked corpus. Inspect limits for current coverage; Unsupported inputs return NOT_COVERED.

View contract →
x402-intelligence

402 Error Rosetta Stone

Resolve one normalized x402 v2 integration fingerprint using an evidence-linked correction record. Unsupported inputs return NOT_COVERED.

View contract →
x402-intelligence

Worked-Once Recipe Vault

Retrieve a known-good, versioned x402 integration recipe with its exact environment and verification evidence. Unsupported inputs return NOT_COVERED.

View contract →
coordination

Swarm Semaphore: Acquire

Acquire or renew one bounded semaphore permit.

View contract →
coordination

Swarm Semaphore: Release

Release one known semaphore permit.

View contract →
coordination

Swarm Semaphore: Status

Read a known semaphore's capacity without changing holders.

View contract →
coordination

Barrier Bell: Arrive

Record one opaque participant arrival at a bounded barrier.

View contract →
coordination

Barrier Bell: Status

Read a known barrier's count and release state without changing it.

View contract →
coordination

Freshness Lease: Acquire

Acquire or renew one bounded freshness lease.

View contract →
coordination

Freshness Lease: Release

Release a known freshness lease only as its current holder.

View contract →
coordination

Freshness Lease: Status

Read a known freshness lease's activity and expiry without changing it.

View contract →
ephemeral

Failure Sequence Forge

Create an unguessable temporary GET endpoint for testing retry and recovery behavior. Each request atomically consumes exactly one allowlisted failure or terminal-success step. Responses use a fixed JSON body and fixed safe headers; callers cannot provide bodies, headers, redirects, or destinations.

View contract →
coordination

Swarm Rate Gate: Consume

Atomically request tokens from one bounded shared rate gate.

View contract →
coordination

Swarm Rate Gate: Status

Read a known rate gate's remaining capacity without consuming tokens.

View contract →
compatibility

MCP Tool Contract Linter

Checks a supplied tool name, description, JSON input/output schema, security declarations, and action annotations. It performs bounded local analysis only and never contacts the declared server.

View contract →
x402-intelligence

x402 Requirement Drift Diff

Detects changes to the scheme, network, asset, atomic amount, receiver, resource, or advertised extensions in two caller-supplied requirements. It performs no commercial transaction, signature, or network operation.

View contract →
ephemeral

Webhook Attempt Meter: Create

Create one bounded webhook attempt meter with an unguessable endpoint.

View contract →
ephemeral

Webhook Attempt Meter: Retrieve

Retrieve and irreversibly consume one webhook meter result.

View contract →
compatibility

MCP Capability Handshake Diff

Compares bounded client and server initialize capabilities, protocol versions, and caller-required features. It performs a local negotiation diff and does not connect to either peer.

View contract →
x402-intelligence

x402 Facilitator Compatibility Diff

Checks whether a caller-supplied facilitator capability document covers one normalized scheme, network, asset, and extension set. It never contacts a facilitator, verifies a commercial transaction, or transfers funds.

View contract →
compatibility

MCP Elicitation Safety Linter

Inspects only bounded field names, types, and descriptions. It identifies secret-like or high-risk personal fields in form-mode elicitation and never accepts the field values themselves.

View contract →
coordination

x402 Quote Fingerprint Guard: Bind

Bind one normalized x402 quote fingerprint to an opaque retry identity.

View contract →
coordination

x402 Quote Fingerprint Guard: Check

Compare a normalized x402 quote to a known retry identity without revealing stored terms.

View contract →
compatibility

MCP Schema Edge-Case Atlas

Provides versioned schema fragments with valid and invalid examples for six narrow interoperability edges. These are portable test vectors, not claims about an untested host or SDK.

View contract →

Safety boundary

The connector exposes purpose-built tools, cannot initiate transfers, and does not accept payment headers. Its quotas and retry identities are isolated from the core API.

See the privacy policy, terms, and support guidance.