← writerslogic.com

INDIVIDUAL MCP TOOL

hash-receipt

Signed hash receipt (Merkle batch, RFC 9162) — Timestamped, signed receipt for up to 256 SHA-256 hashes in one call: an RFC 9162 Merkle root, a per-hash inclusion proof, and the hub's W3C VC + EIP-191 signatures over both.

writerslogic.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://agents.writerslogic.com/mcp/agent-infra

No auth detected

Connect to this endpoint to inspect the live schema for hash-receipt and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

writerslogic.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.writerslogic-verifiable-ai-agent-hub-agent-infra]
url = "https://agents.writerslogic.com/mcp/agent-infra"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "writerslogic-verifiable-ai-agent-hub-agent-infra": {
      "type": "http",
      "url": "https://agents.writerslogic.com/mcp/agent-infra"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: writerslogic-verifiable-ai-agent-hub-agent-infra
Remote MCP URL: https://agents.writerslogic.com/mcp/agent-infra

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "writerslogic-verifiable-ai-agent-hub-agent-infra": {
      "url": "https://agents.writerslogic.com/mcp/agent-infra"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "writerslogic-verifiable-ai-agent-hub-agent-infra": {
      "type": "http",
      "url": "https://agents.writerslogic.com/mcp/agent-infra"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "writerslogic-verifiable-ai-agent-hub-agent-infra",
  "transport": "streamable-http",
  "url": "https://agents.writerslogic.com/mcp/agent-infra"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • warm-memory — WARM verifiable agent memory — Persistent memory for AI agents as a pay-per-call API, no database to run.
  • unicode-check — Unicode smuggling check for strings (prompts, tool args, URLs) — Checks up to 100 strings in one call against the 19 deterministic rules of unicode-safety-check: bidi controls (Trojan Source), invisible and zero-width characters, tag-character and variation-selector payloads, homoglyph and mixed-script hosts or names.
  • mcp-tool-pin — MCP tool pin: detect changed tool definitions (rug pulls) and hidden Unicode — Send an MCP server's tools/list result (up to 200 tools) and, after the first call, the hashes you approved.
  • doi-check — DOI check: exists, retracted, or fabricated (batch of 20) — Checks up to 20 DOIs in one call against Crossref (including its Retraction Watch notices), OpenAlex and the doi.
  • patch-anchor — Apply a unified-diff hunk or search/replace edit to a file by content, refusing ambiguity — Applies unified-diff hunks (wrong line numbers are fine) or search/replace blocks to a supplied file text and returns the patched text, for an agent whose edit tool failed or whose diff has drifted line numbers.
  • edit-anchor-check — Check that an edit's old-string occurs exactly once in a file, with match contexts — Counts how many times an old-string occurs in a supplied file text (as a replace-in-file tool would see it) and returns each match's offset, line, column and surrounding lines, for an agent about to issue an edit.
  • retry-admissibility — Decide whether a failed HTTP call may be retried, must be reconciled, or must not be repeated — Given a request's method, how it ended (response status, timeout, reset, refused), idempotency-key evidence and optional caller policy, returns retry / do-not-retry / reconcile / unknown for an agent deciding what to do after a failed tool or API call.
  • http-outcome — Classify an HTTP response as success, retry, reconcile or stop, with the wait it asks for — Classifies one HTTP response (method, status, headers) as success / retry / reconcile / stop for an agent that just called an API, and reads the wait from Retry-After (RFC 9110: delay-seconds or any of the three HTTP-date formats) or from a vendor delay header whose dialect the caller declares (seconds, milliseconds, epoch seconds, epoch milliseconds, HTTP-date).