Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

WritersLogic agent-infra

REMOTE · AGENTS.WRITERSLOGIC.COM

Micro agents for parsing, validation, encoding, scoring, and structured I/O pipelines.

65 Trust /100

Last scanned (13 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

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 Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 65 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 13753 tokens (~211/item across 65 items; 65 tools + 0 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 Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 80% 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 65 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 66 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 65 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1
    • Tool “spend-ledger” rewrote its description, which is the text the model reads security
    • “token-bucket” reworded the description of “capacity” cosmetic
    • “token-bucket” reworded the description of “refillPerSecond” cosmetic
  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 26 63

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://agents.writerslogic.com/mcp/agent-infra

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=writerslogic.com CN=WE1,O=Google Trust Services,C=US 4 Nov 2026 2 Feb 2027 ECDSA 256 ECDSA-SHA256 802305745c0c9ae0139546a9e543dd74
SANs: writerslogic.com, agents.writerslogic.com, *.agents.writerslogic.com
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 secure

Validation of agents.writerslogic.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
writerslogic.com. DS published 2371 13 Verified
agents.writerslogic.com. Verified address RRset verified with the apex keys
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=15552000; includeSubDomains
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agents.writerslogic.com/mcp/agent-infra Verified 200
http (plaintext) http://agents.writerslogic.com/mcp/agent-infra HTTPS enforced 301 https://agents.writerslogic.com/mcp/agent-infra
MCP tools · 65 exposed · ~13,700 tokens

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 →

Tool Tokens
policy-gate ~234

Policy gate with a signed receipt: your JsonLogic rules vs a proposed tool call or payment — Evaluates your own policy (JsonLogic rules, each allow or deny, deny-overrides or first-match, default deny) against a proposed tool call, payment or action, and returns allow or deny, the rule id that decided, and a receipt signed by the hub over the hashes of the policy, the request and the decision. The receipt is the product: another agent or an auditor can verify offline which rule allowed th

NameTypeReqDescription
languagestring–Default jsonlogic. cedar and rego return unsupported.
policy–yesJsonLogic: { rules: [{ id, effect: allow|deny, when: <JsonLogic>, description? }] (at most 100), combining?: deny-overrides|first-match, defaultEffect?: deny|allow }. A string for cedar/rego.
request–yesThe proposed action as JSON (at most 65536 bytes), e.g. { tool, args, amountUsd, payee }. Rules read it with { "var": "args.amountUsd" }.

No output schema declared.

No examples provided.

quota-reservation-check ~183

Would this request fit in the remaining quota, given a snapshot and pending reservations? (snapshot-bound) — Computes available quota from a caller-supplied snapshot (limit, used, reserved) minus the unexpired pending reservations and says whether a requested amount fits. This is a read of the numbers you supply as of snapshotAt: it reserves nothing, so concurrent consumers can still use the quota before you do, and every response says so. A stale snapshot gives unknown, not pass; a window that ended at

NameTypeReqDescription
asOfstringyesRFC 3339 instant of the decision (no clock is read).
maxSnapshotAgeSecondsinteger––
pendingarray––
quotaobjectyes–
requestobjectyes–
snapshotAtstringyesRFC 3339 instant the quota numbers were read.

No output schema declared.

No examples provided.

result-cache ~210

Content-addressed result cache shared by your agents (short TTL) — Caches a result under the SHA-256 of the canonical (JCS) request, so every agent in your fleet that makes the same request reuses one answer for up to an hour. get returns hit with the value and age, or a miss (status unknown). Scoped to your wallet or tenantId, never shared across customers, so nobody else can poison your cache.

NameTypeReqDescription
namespacestring–Default: default.
opstringyes–
request–yesAny JSON identifying the computation; it is canonicalized (RFC 8785) and hashed.
tenantIdstring–Required for API-key callers (namespaced as key:<tenantId>; keep it unguessable). Ignored when a wallet paid: the payer address is the tenant.
ttlSecondsinteger–put: default 300.
value––put: the JSON result, at most 16384 bytes serialized.

No output schema declared.

No examples provided.

retry-admissibility ~328

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. Encodes RFC 9110 method idempotency, the proxy and retry-of-a-retry rules and Retry-After parsing; a timeout or reset is never read as success or a

NameTypeReqDescription
actorstring––
asOfstring–RFC 3339 instant; needed only to turn a Retry-After HTTP-date into seconds.
attemptinteger–1-based number of the attempt that just ended. Default 1.
automaticboolean–True when the retry would be issued automatically (library or proxy) rather than by a deliberate decision.
endedstringyesHow the attempt ended.
idempotencyKeyobject–Caller-asserted evidence: the engine knows no vendor's key semantics.
methodstringyesHTTP method, case-sensitive (GET, POST, ...).
policyobject––
previousAttemptWasAutomaticRetryboolean––
requestSentstring–Whether request bytes reached the network. connection-refused and dns-failure imply not-sent.
retryAfterstring–Retry-After header value.
statusinteger–Required when ended is 'response'.

No output schema declared.

No examples provided.

spend-ledger ~348

Spend ledger with reservations: one budget for a tree of agents — A budget shared by a task tree, in integer minor units. Call open(currency, budgetMinor) once per ledger first; every other op answers unknown NO_LEDGER until then. reserve() atomically holds an amount if the remaining budget covers it (expired holds are freed automatically); commit() records what was actually spent, up to the hold; release() frees a hold. These are real reservations, not a snapsh

NameTypeReqDescription
amountMinorinteger–reserve: amount to hold. commit: amount actually spent (at most the hold).
budgetMinorinteger–open: total budget in minor units.
currencystring–open: currency or token code, e.g. USD or USDC.
ledgerstringyesLedger name, e.g. task:research-42.
opstringyes–
requestIdstring–Caller-chosen id for this mutation. A retry with the same id and same input returns the stored response (24 h) instead of applying twice; the same id with different input is rejected. Send one on eve…
reservationIdstring––
tenantIdstring–Required for API-key callers (namespaced as key:<tenantId>; keep it unguessable). Ignored when a wallet paid: the payer address is the tenant.
ttlSecondsinteger–reserve: hold lifetime; default 600.

No output schema declared.

No examples provided.

syndication-hint ~212

Detect near-duplicate passages (syndicated or copied text) so repeated sources are not counted as independent — Compares up to 30 passages an agent collected and reports which pairs share word-shingle content (Jaccard and containment), grouping them into clusters of probable copies so the number of independent sources can be stated honestly. Does not establish who copied whom, does not detect paraphrase or translation, and does not fetch anything; a high similarity is a hint that sources are not independent

NameTypeReqDescription
containmentThresholdnumber–Pairs where this share of the smaller passage's shingles appear in the other are flagged (catches an excerpt of a longer copy). Default 0.8.
jaccardThresholdnumber–Pairs at or above this Jaccard similarity are flagged. Default 0.5.
passagesarrayyesUp to 30; 300000 characters in total.
shingleWordsinteger–Words per shingle. Default 5.

No output schema declared.

No examples provided.

test-exit-interpret ~298

Interpret a test run: pass, no-tests, skipped, flaky, infra-failure from runner, exit code and counts — Reads a finished test run (runner, exit code, optional version, flags, caller-parsed counts, optional go test output, optional per-attempt exit codes) and says whether tests actually passed, ran nothing, were all skipped, passed only on retry, or never ran properly (timeout, signal, internal error). Encodes only exit-code semantics the runners document: pytest 0-5, node:test, mocha (failure count

NameTypeReqDescription
attemptExitCodesarray–Exit codes of repeated runs of the same tests, to detect flakiness. Interpreted with the same runner rules.
countsobject–Counts parsed by the caller from the runner's own report.
exitCodeinteger–Process exit status. Omit when the process was killed by a signal or timed out.
flagsobject––
outputstring–go test output (only ok, FAIL, --- FAIL and panic: lines are read).
runnerstringyes–
signalstring–Terminating signal name, e.g. SIGKILL.
timedOutboolean–True when the harness gave up waiting.
versionstring–Runner version, e.g. 10.4.0. Needed only for version-gated flags.

No output schema declared.

No examples provided.

text-offsets ~186

Convert text offsets between UTF-16, code points, UTF-8 bytes and graphemes, and locate hidden Unicode — Reports the length of a string in UTF-16 code units, Unicode code points, UTF-8 bytes and extended grapheme clusters (Intl.Segmenter), converts up to 200 ranges given in any one of those units into all four, and flags ranges that fall inside a surrogate pair, a multi-byte UTF-8 character or a grapheme cluster. It also runs the unicode-check rules (bidi controls, zero-width and invisible characters

NameTypeReqDescription
kindstring–How the unicode rules treat the string. Default text.
rangesarray–Half-open ranges to convert; each is read in its own unit.
scanboolean–Run the hidden-Unicode rules. Default true.
textstringyesThe string.

No output schema declared.

No examples provided.

token-bucket ~343

Shared token bucket: many agents, one upstream rate limit — One rate limiter shared by every agent in your fleet. take(cost) atomically spends tokens if available and returns allowed plus remaining, or refuses with retryAfterMs until enough tokens refill. capacity and refillPerSecond are fixed when the bucket is first used; a call with different settings is refused so two fleets cannot silently disagree. Use a requestId so a retried take is not charged twi

NameTypeReqDescription
bucketstringyesBucket name, e.g. openai:org-123:rpm.
capacitynumberyesBucket size in tokens. Required on every call, peek included, and must equal the value the bucket was created with.
costnumber–Tokens to spend; default 1.
opstringyes–
refillPerSecondnumberyesTokens added per second (0.5 = one every 2 s). Required on every call; must equal the value the bucket was created with.
requestIdstring–Caller-chosen id for this mutation. A retry with the same id and same input returns the stored response (24 h) instead of applying twice; the same id with different input is rejected. Send one on eve…
tenantIdstring–Required for API-key callers (namespaced as key:<tenantId>; keep it unguessable). Ignored when a wallet paid: the payer address is the tenant.

No output schema declared.

No examples provided.

transcript-validator ~171

Check tool-call / tool-result pairing and ordering in an LLM transcript (Anthropic, OpenAI Chat, OpenAI Responses) — Validates a message list before it is sent to Anthropic Messages, OpenAI Chat Completions or OpenAI Responses: every tool call paired with its result, results in the right place and role, ids present and unique. Built for an agent that edits, truncates or replays its own history and would otherwise get a 400. Only rules stated in the providers' documentation fail the check; anything else suspiciou

NameTypeReqDescription
expectCompleteboolean–Default true: a trailing tool call without a result is a defect. Set false when the transcript is mid-loop and results are still pending.
messagesarrayyes–
providerstringyes–

No output schema declared.

No examples provided.

translation-invariants ~188

Check that numbers, units, part numbers, tolerance signs, dates, placeholders and URLs survive translation — For aligned source and target segments, extracts the tokens a translation must not change (numbers with attached units or %, ISO dates, part numbers and versions, tolerance and comparison operators such as ± ≤ ≥, placeholders like {0} or %s, URLs and emails) and reports any that are missing, added or altered, with offsets in both texts in UTF-16, code points, UTF-8 bytes and graphemes. Numbers are

NameTypeReqDescription
kindsarray–Token kinds to check. Default all.
segmentsarrayyesUp to 200; 100000 characters in total.
sourceDecimalstring–Decimal mark of the source locale. Default auto (both readings tried).
targetDecimalstring–Decimal mark of the target locale. Default auto.

No output schema declared.

No examples provided.

unicode-check ~158

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. Built for an agent's hot path: run it on a prompt, a tool argument, a URL or a model output before acting on it. Returns BLOCK / REVIEW / NO_FIND

NameTypeReqDescription
kindstring–text (default): prose, only critical findings block. identifier or url: high findings such as mixed-script names also block.
stringsarrayyesUp to 200000 characters in total.

No output schema declared.

No examples provided.

update-dialect ~225

What do omitted, null, [] and "" mean in this PATCH body under merge-patch, JSON Patch or a declared dialect? — For an agent about to send a PATCH or update body: states, per field, what omitted / null / [] / "" mean under the declared dialect (RFC 7396 merge patch, RFC 6902 JSON Patch, or caller-declared semantics) and checks the body against stated intents such as 'clear this field', 'leave this alone' or 'set to empty array'. With a target document it applies the patch and compares the result; without on

NameTypeReqDescription
callerSemanticsobject–Required when dialect is 'caller': what each payload form means in that API.
dialectstringyesmerge-patch = RFC 7396, json-patch = RFC 6902 (payload is an array of operations), caller = semantics in callerSemantics.
intentsarray––
payload–yesThe PATCH body.
target––Current document, if available. Enables applying the patch and exact checks.

No output schema declared.

No examples provided.

warm-memory ~280

WARM verifiable agent memory — Persistent memory for AI agents as a pay-per-call API, no database to run. op=remember stores subject-predicate-object facts (or extracts them from free text; only facts whose subject and object appear verbatim are kept); a newer value for the same subject and predicate supersedes the old one, and the history stays queryable. op=recall searches by BM25 keyword ranking or exact triple pattern, now

NameTypeReqDescription
asOf––Epoch milliseconds or an ISO 8601 date/time (UTC when no offset).
factsarray––
historystring–recall: only facts current at asOf (default) or every status.
limitinteger––
opstringyes–
patternobject–Exact (case- and whitespace-insensitive) match on any of subject, predicate, object.
querystring––
saidstring––
sourcestring–remember: provenance label for facts extracted from text.
tenantIdstring–Required for API-key callers (namespace as key:<tenantId>; keep it unguessable). Ignored when a wallet paid.
textstring–remember: free text; facts are extracted by a fast model and kept only if subject and object occur verbatim.

No output schema declared.

No examples provided.

workflow-transition ~155

Is this state transition allowed by the caller's workflow definition, and what is allowed instead? — Given a caller-supplied state machine (transitions with optional event names and required facts), the current state and a requested event or target state, says whether the transition is allowed, which required facts are false or unknown, and which transitions are available from the current state. For an agent about to move an order, ticket, deployment or approval to its next state. Terminal states

NameTypeReqDescription
currentstringyes–
factsarray––
requestobjectyesGive event, to, or both.
terminalarray–States with no outgoing transitions allowed even if listed.
transitionsarrayyes–

No output schema declared.

No examples provided.

Install

How do I install the WritersLogic agent-infra MCP server?

WritersLogic agent-infra is a hosted endpoint at https://agents.writerslogic.com/mcp/agent-infra, 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 · agents.writerslogic.com

# add to Claude Code
claude mcp add --transport http com-writerslogic-agents-writerslogic-agent-infra 'https://agents.writerslogic.com/mcp/agent-infra'
Common questions

What is the WritersLogic agent-infra MCP server?

WritersLogic agent-infra is an MCP server listed in the public MCP registry as com.writerslogic.agents/writerslogic-agent-infra. Micro agents for parsing, validation, encoding, scoring, and structured I/O pipelines. This page covers its hosted endpoint (https://agents.writerslogic.com/mcp/agent-infra).

Is the WritersLogic agent-infra MCP server safe to use?

WritersLogic agent-infra scores 65 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 WritersLogic agent-infra MCP server expose?

WritersLogic agent-infra exposes 65 tools: warm-memory, hash-receipt, unicode-check, mcp-tool-pin, doi-check, and 60 more. Their descriptions and schemas cost roughly 13,700 tokens of context every time the server is loaded.

Does the WritersLogic agent-infra MCP server require authentication?

No. We connected to WritersLogic agent-infra without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the WritersLogic agent-infra MCP server still maintained?

WritersLogic agent-infra is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the WritersLogic agent-infra MCP server?

VerifyMCP ran 12 checks on WritersLogic agent-infra, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about WritersLogic agent-infra: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.