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 (12 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
acceptance-receipt ~154

Signed acceptance receipt: which deterministic tests a delivered output passed — Runs your deterministic acceptance tests (equals, exists, absent, type, contains, length and number ranges, one-of, sha256, a JSON Schema subset) against a sub-agent's or vendor's JSON output at JSON Pointer paths, and returns per-test results plus a hub-signed receipt over the output hash, the tests hash and the results. Use it before paying for delegated work or releasing the next step. It certi

NameTypeReqDescription
labelstring–Free text bound into the receipt, e.g. the task id.
output–yesThe delivered JSON (at most 262144 bytes as JCS).
testsarrayyes–

No output schema declared.

No examples provided.

approval-invalidation ~243

Does a change to the approved thing invalidate the approval under a materiality policy? — Compares what a human or system approved with what is about to be executed (a quote, order, plan, diff summary: any JSON) under a caller-supplied materiality policy: per-path rules exact / ignore / numeric tolerance (absolute or percent) / no-increase / no-decrease, with the longest matching path winning and a default for unlisted paths. Also covers quote revisions (approved revision number must e

NameTypeReqDescription
approved–yesThe approved snapshot (JSON).
approvedAtstring–RFC 3339 instant.
approvedRevisioninteger––
asOfstring–RFC 3339 instant for the expiry check; no clock is read.
current–yesThe version about to be executed (JSON).
currentRevisioninteger––
policyobject––
requireSameRevisionboolean–Default true when either revision is given (a missing partner gives unknown): an approval for another revision does not cover this one. Send false to ignore the revisions.
validForSecondsinteger––

No output schema declared.

No examples provided.

artifact-invalidator ~123

Which derived artifacts must be rechecked after these inputs changed? (bounded dependency graph) — Given a dependency graph of artifacts (each lists the artifact ids it was derived from) and the ids that changed, returns every artifact that transitively depends on a change, in an order safe to recompute (inputs before dependents), and the artifacts that are unaffected. A cycle or an unknown input id is a defect in the graph and returns fail with the cycle path. Changed ids that are unknown fail

NameTypeReqDescription
artifactsarrayyes–
changedarrayyes–

No output schema declared.

No examples provided.

assumption-conflict ~142

Find assumptions that disagree across agents (currency, timezone, version, customer id, ...) — Takes assumptions that several agents or steps hold about the same fact (key, value, who) and reports every key where the values differ, naming the conflicting pairs and whether they differ only by case or whitespace (a formatting difference) or in substance (USD vs EUR, a different id, a different version). Optionally requires each listed agent to state each required key; a missing statement is u

NameTypeReqDescription
agentsarray–Agents expected to state the required keys.
assumptionsarrayyes–
requiredKeysarray–Keys every listed agent must state.

No output schema declared.

No examples provided.

attachment-references ~134

Check that what a message says is attached matches the attachments actually supplied — Compares a message's wording with its attachment list: 'see attached' with nothing attached, a named file (report.pdf) that is not in the list, a kind of file mentioned (the spreadsheet, a screenshot, the PDF) that no attachment matches by extension or MIME type, and a stated count ('two files') that differs from the list; attachments the text never mentions are listed. Mentions inside a negation

NameTypeReqDescription
attachmentsarrayyesThe attachments actually present; may be empty.
textstringyesMessage body.

No output schema declared.

No examples provided.

cache-key-check ~186

Check that a result-cache key contains every input that changes the result, and nothing volatile — Given the inputs of a cached computation (each declared as influencing the output or not, optionally volatile) and the list of inputs the cache key is built from, finds influential inputs missing from the key (stale or wrong hits), volatile inputs inside it (the cache never hits), unknown-influence inputs left out, and, for private results, a missing tenant dimension (cross-tenant leak). When valu

NameTypeReqDescription
inputsarrayyes–
keyPartsarrayyesNames of the inputs the key is built from.
privateboolean–The result is per-tenant or per-user.
scopestring–Namespace mixed into the digest.
tenantInputstring–Name of the input that identifies the tenant or user; required in the key when private.

No output schema declared.

No examples provided.

chat-deep ~294

Chat completion, deep tier (12k in, 2k out) — OpenAI-style chat completion served by the hub's provider router (strongest available model, up to 12000 input tokens and 2048 output tokens per call), with a signed receipt that binds the provider, model, token usage and the hashes of your messages and the reply. Supports optional strict json_schema output returned both parsed and as a string. Does not stream, call tools or functions, accept imag

NameTypeReqDescription
max_tokensinteger–Upper bound on the reply in tokens; defaults to 1024. A value above the tier cap is rejected with 400.
messagesarrayyesConversation, oldest first; the last message must have role user. At most 200000 characters in total. System messages are joined into the instructions.
modelstring–Accepted and ignored: the hub routes by tier (the resource you paid for). Echoed as requested_model.
response_formatobject–Either {"type":"text"} (default) or {"type":"json_schema","json_schema":{name,schema}}. The schema is always enforced strictly: root object, every property required, additionalProperties false, keywo…
temperaturenumber–Accepted and ignored.
top_pnumber–Accepted and ignored.

No output schema declared.

No examples provided.

chat-fast ~296

Chat completion, fast tier (8k in, 1k out) — OpenAI-style chat completion served by the hub's provider router (small, fast model, up to 8000 input tokens and 1024 output tokens per call), with a signed receipt that binds the provider, model, token usage and the hashes of your messages and the reply. Supports optional strict json_schema output returned both parsed and as a string. Does not stream, call tools or functions, accept images, or us

NameTypeReqDescription
max_tokensinteger–Upper bound on the reply in tokens; defaults to 1024. A value above the tier cap is rejected with 400.
messagesarrayyesConversation, oldest first; the last message must have role user. At most 200000 characters in total. System messages are joined into the instructions.
modelstring–Accepted and ignored: the hub routes by tier (the resource you paid for). Echoed as requested_model.
response_formatobject–Either {"type":"text"} (default) or {"type":"json_schema","json_schema":{name,schema}}. The schema is always enforced strictly: root object, every property required, additionalProperties false, keywo…
temperaturenumber–Accepted and ignored.
top_pnumber–Accepted and ignored.

No output schema declared.

No examples provided.

chat-standard ~293

Chat completion, standard tier (12k in, 2k out) — OpenAI-style chat completion served by the hub's provider router (mid-size general model, up to 12000 input tokens and 2048 output tokens per call), with a signed receipt that binds the provider, model, token usage and the hashes of your messages and the reply. Supports optional strict json_schema output returned both parsed and as a string. Does not stream, call tools or functions, accept images,

NameTypeReqDescription
max_tokensinteger–Upper bound on the reply in tokens; defaults to 1024. A value above the tier cap is rejected with 400.
messagesarrayyesConversation, oldest first; the last message must have role user. At most 200000 characters in total. System messages are joined into the instructions.
modelstring–Accepted and ignored: the hub routes by tier (the resource you paid for). Echoed as requested_model.
response_formatobject–Either {"type":"text"} (default) or {"type":"json_schema","json_schema":{name,schema}}. The schema is always enforced strictly: root object, every property required, additionalProperties false, keywo…
temperaturenumber–Accepted and ignored.
top_pnumber–Accepted and ignored.

No output schema declared.

No examples provided.

chunk-boundaries ~202

Split text into chunks under a hard token cap without cutting a table, sentence or code fence — Plans chunk boundaries for text an agent must feed to a model in pieces: every chunk is at most maxTokens in the named tokenizer (o200k_base or cl100k_base, verified by counting each finished chunk), boundaries fall only between sentences, blocks, whole Markdown or HTML tables and whole code fences, headings stay with the text that follows, and the chunks tile the input exactly (concatenating the

NameTypeReqDescription
includeTextboolean–Also return each chunk's text. Default false (slice by span).
maxTokensintegeryesHard cap per chunk.
textstringyesText to chunk (Markdown, plain text or HTML tables).
tokenizerstringyeso200k_base or cl100k_base. Any other name (including Claude models) returns status unsupported for items that need counting; caller token counts are always accepted.

No output schema declared.

No examples provided.

citation-span ~253

Locate quoted text in a source with exact offsets, or classify it as normalized, elided, paraphrased or absent — Finds each quote an agent attributes to a source text and returns where it sits: exact offsets in UTF-16, code points, UTF-8 bytes and graphemes, so the span slices back to the matched text. Tries an exact match, then a match tolerant of whitespace, curly vs straight quotes, dash types, ellipses, invisible characters and Unicode forms (NFC/NFD, ligatures), naming which normalizations were needed,

NameTypeReqDescription
exactOnlyboolean–Count only byte-identical matches as pass; normalized matches become fail. Default false.
ignoreCaseboolean–Also tolerate case differences (reported as a normalization). Default false.
minLengthinteger–Quotes shorter than this many characters (after trimming quote marks) are too-short and give unknown. Default 8.
quotesarrayyesUp to 50 quotes, 40000 characters in total.
sourcestringyesText the quotes are claimed to come from.
toleratearray–Normalizations that still count as a match. Default: all six.

No output schema declared.

No examples provided.

compensation-coverage ~158

Check that every write step in a multi-step plan has an undo step, and give the rollback order — For an agent plan made of steps with declared effects (read or write), checks every write in the plan, run or not, has a compensation step that exists, is itself a write, is not its own compensation, and that the dependencies have no cycle; flags writes declared irreversible; and, given which steps have completed, returns the compensations to run in reverse completion order. Does not judge whether

NameTypeReqDescription
completedarray–Step ids completed so far, in completion order. Only used for rollbackOrder and to say an irreversible write has already run; coverage is always checked for the whole plan.
stepsarrayyes–

No output schema declared.

No examples provided.

confirmation-state ~187

Classify a confirmation message as submitted, pending, reserved or completed from caller or default phrases — Reads a confirmation page, email or API message and decides which state it states: submitted, pending, reserved or completed, using phrase lists the caller supplies (preferred, because wording is provider-specific) plus an optional default English list. Matches are whole-word, case- and typography-insensitive, returned with offsets in UTF-16, code points, UTF-8 bytes and graphemes, and a match ins

NameTypeReqDescription
precedencearray–When several states match, the first one listed wins. Without it a conflict is unknown.
rulesarray–Caller phrase lists; with these present the defaults are off unless useDefaults is true.
textstringyesConfirmation text.
useDefaultsboolean–Include the default English phrases. Default true only when rules is absent.

No output schema declared.

No examples provided.

constraint-carryover ~153

Check that earlier constraints (numbers, dates, codes, quoted terms, negations) survive into a later plan or summary — Takes the constraints an agent was given (budget caps, deadlines, identifiers, prohibitions) and a later artifact (plan, summary, handoff, tool arguments) and reports for each constraint whether its concrete atoms still appear: numbers with their unit or currency, ISO dates, codes, quoted terms, or caller-listed anchor strings, with offsets. For a negated constraint it also reports whether the clo

NameTypeReqDescription
constraintsarrayyesUp to 50; 20000 characters of constraint text in total.
targetstringyesThe later artifact that must still honor the constraints.

No output schema declared.

No examples provided.

context-pack ~207

Pick context blocks that fit a token budget, keeping mandatory blocks and their dependencies — Chooses which context items an agent should put into a prompt without exceeding a token budget: every mandatory item and everything it depends on is always included, then optional items by descending priority (each with the dependencies it pulls in) while they fit. Token counts come from the caller or from o200k_base / cl100k_base; any other tokenizer name returns unsupported (there is no Claude t

NameTypeReqDescription
budgetintegeryesMaximum total tokens (including perItemOverhead per included item).
itemsarrayyesUp to 500 items, 300000 characters of text in total.
perItemOverheadinteger–Tokens added per included item for separators or wrappers. Default 0.
tokenizerstring–o200k_base or cl100k_base. Any other name (including Claude models) returns status unsupported for items that need counting; caller token counts are always accepted.

No output schema declared.

No examples provided.

conversation-prune ~244

Choose which old messages to drop to hit a token target without touching the cached prompt prefix — Given a conversation, the index of the last message inside the provider's cached prefix, and a token target, returns which messages to drop: whole tool call plus tool result pairs (so no result is left without its call) and messages the caller marked droppable, oldest first or largest first, never inside the cached prefix, never the most recent keepRecent messages, never pinned ones. Everything up

NameTypeReqDescription
cacheBreakpointintegeryesIndex of the last message inside the cached prefix; -1 when nothing is cached.
keepRecentinteger–Most recent messages that are never dropped. Default 4.
messagesarrayyesUp to 500; 400000 characters of content in total.
strategystring–Order in which droppable units are removed. Default oldest-first.
targetTokensintegeryesTotal tokens to get at or under.
tokenizerstring–o200k_base or cl100k_base. Any other name (including Claude models) returns status unsupported for items that need counting; caller token counts are always accepted.

No output schema declared.

No examples provided.

cross-reference-check ~154

Find dangling and duplicated cross-references (Section 3.2, Table 4, Figure 2, [7]) in a document — Scans a document for the targets it defines (numbered headings, Table/Figure/Listing/Equation captions at line start, Appendix/Annex headings, [n] bibliography entries, [^id] footnote definitions) and the references it makes to them ('see Section 3.2', 'Tables 2 and 4', 'Figures 3 to 5', '[7]', '[^note]'), and reports references with no target, targets defined twice, and targets never referenced,

NameTypeReqDescription
textstringyesDocument text (plain text or Markdown).

No output schema declared.

No examples provided.

deadline-feasibility ~157

Can this plan of steps finish inside the remaining time, in the expected case and the worst case? — Takes steps with expected and worst-case durations, dependencies (steps with no dependency between them run in parallel), retries with backoff, and the time remaining, and computes the critical path for both cases. Verdict guaranteed (worst case fits: pass), likely (only the expected case fits: unknown) or infeasible (even the expected case does not fit: fail), with the slack and the critical-path

NameTypeReqDescription
overheadMsinteger–Fixed time to reserve for settlement, serialization, etc.
remainingMsintegeryesTime left to the hard deadline, measured by the caller.
stepsarrayyes–

No output schema declared.

No examples provided.

dedup-window ~164

Group webhook deliveries by identity within a time window and decide: process, dedupe, retry, reconcile or abstain — Given previously seen deliveries (identity, receivedAt, payload or digest, handling outcome) and a new incoming one, finds earlier deliveries with the same identity inside the window and returns process (none), dedupe (same payload already processed), retry (earlier ones all failed), reconcile (an earlier one is in flight or unknown, or the same identity arrives with a different payload) or abstai

NameTypeReqDescription
historyarrayyes–
incomingobjectyes–
windowModestring–from-first (default): a group's window starts at its first delivery. sliding: each delivery extends the window.
windowSecondsintegeryes–

No output schema declared.

No examples provided.

deictic-check ~173

Find unresolved references (that one, the former, tomorrow, next week) and return clarification questions — Scans a user or tool message for phrases that cannot be understood without context: demonstratives ('that one', 'the latter'), back-references ('as before', 'the usual'), and relative dates or times ('tomorrow', 'next Friday', 'end of month', 'soon'), each with offsets and a clarification question. Given a caller anchor (asOf instant plus IANA time zone) it resolves only unambiguous day offsets (t

NameTypeReqDescription
anchorobject–Reference time for resolving unambiguous relative dates.
candidatesarray–Items recently in play; echoed on reference slots for the caller to ask with. Never chosen automatically.
textstringyesMessage to check.

No output schema declared.

No examples provided.

delegation-contract-check ~206

Check that a sub-agent delegation states objective, acceptance criteria, budget, evidence and stop conditions — Checks the brief an agent is about to hand to another agent: the required parts are present and non-empty (objective, acceptance criteria, a budget with at least one positive numeric bound, required evidence, stop conditions; output format if required), nothing is duplicated, and acceptance criteria are not made only of vague wording (a small labelled word list: good, appropriate, if possible ...)

NameTypeReqDescription
acceptanceCriteriaarray––
budgetobject––
evidenceRequiredarray–What the delegate must return as proof (links, test output, file paths).
objectivestring––
outputFormatstring––
requirearray–Parts that must be present. Default: objective, acceptanceCriteria, budget, evidenceRequired, stopConditions.
stopConditionsarray–When the delegate must stop and report (done, blocked, budget spent).

No output schema declared.

No examples provided.

doi-check ~146

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.org Handle registry. Per DOI: FOUND with title and year, RETRACTED, EXPRESSION_OF_CONCERN, CORRECTED, REGISTERED_NOT_INDEXED, NOT_REGISTERED (no such DOI anywhere: likely fabricated), INVALID_DOI or UNVERIFIED. For research agents and RAG pipelines that cite papers: run every DOI throug

NameTypeReqDescription
doisarrayyesBare DOIs, doi: prefixes or https://doi.org/ URLs.

No output schema declared.

No examples provided.

dom-recipe-match ~140

Check whether a saved interaction recipe still applies to the current version of a page — Compares a recipe (ordered steps naming selectors from an earlier dom-skeleton call), the saved skeleton elements those selectors came from, and the current page HTML. Per step it reports matched (same selector, same tag, type, role and name), changed (selector still exists but the element differs), moved (the same element now has a different selector, given as newSelector), ambiguous (several cur

NameTypeReqDescription
htmlstringyesCurrent page HTML.
recipeobjectyes–
savedarrayyeselements from an earlier dom-skeleton response.

No output schema declared.

No examples provided.

dom-skeleton ~162

List the interactive elements of an HTML page with stable CSS selectors — Reduces an HTML document to the elements an agent can act on: links with href, buttons, inputs (not type=hidden), selects, textareas, [role], [onclick], contenteditable, each with tag, type, role, best-effort accessible name (including label associations) and a CSS selector that matches exactly that element, preferring a stable id, then a data-testid-style attribute, name, aria-label, then a struc

NameTypeReqDescription
dedupeboolean–Collapse elements with identical tag, type, role, name and href. Default true.
htmlstringyesHTML source.
maxElementsinteger–Maximum elements returned. Default 100.

No output schema declared.

No examples provided.

edit-anchor-check ~164

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. pass: exactly one literal match, even counting overlapping ones. unknown: several matches, or one match that overlaps another occurrence of the same text (ambiguous; contexts show how to

NameTypeReqDescription
contextLinesinteger–Lines of context before and after each listed match. Default 2.
filestringyesFile text, at most 524288 UTF-8 bytes and 100000 lines.
oldStringstringyes–

No output schema declared.

No examples provided.

evidence-bundle-check ~215

Check that every claim in an evidence bundle has enough independent, fresh, quote-verified support — Checks a bundle an agent assembled before answering: each claim must be backed by at least N evidence items from distinct source groups, each item's quote must actually appear in the supplied text (with offsets), publication dates must be within the caller's maximum age relative to a caller-supplied asOf, and duplicates are collapsed. Does not fetch URLs or judge whether a source is reliable or wh

NameTypeReqDescription
asOfstring–Reference instant (ISO 8601) for age checks; required with maxAgeDays. The check never reads the clock.
claimsarrayyesClaims to support.
evidencearrayyesUp to 300 items; 300000 characters of text in total.
maxAgeDaysinteger–Evidence published longer ago than this (relative to asOf) is stale.
requireQuotesboolean–Evidence without a verifiable quote does not count as support. Default true.

No output schema declared.

No examples provided.

evidence-scope-mismatch ~184

Check that evidence covers the scope of the claim it is used for (geography, population, period, version, basis, unit) — Compares the scope descriptors of a claim and of the evidence offered for it, per dimension: geography and population (every claimed item must be equal to, or contained in a broader evidence item according to the caller's taxonomy), period (the evidence period must contain the claimed period; partial or no overlap is a mismatch), and version, basis and unit (must be equal after normalization). Des

NameTypeReqDescription
claimobjectyesScope of the claim being made.
evidenceobjectyesScope of the evidence offered.
taxonomyarray–Containment facts for geography and population (40,000 characters in total), e.g. {broader:'United States', narrower:['California','Texas']}. Transitive.

No output schema declared.

No examples provided.

fleet-memory ~313

Fleet memory: your agents' shared observations of endpoints, rate limits, IVR paths and ambiguous submissions — Lets every agent in your fleet record what it observed and read what the others saw, with freshness: endpoint brownouts and latency, rate-limit behaviour, IVR menu paths that worked, whether an ambiguous submission was later accepted or rejected, fixes for an error signature, stale feeds, page recipes, merchant workflow failures, document reputation. record() appends timestamped observations for a

NameTypeReqDescription
namespacestringyes–
observationsarray––
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…
sinceHoursinteger–query window; default 168 (7 days).
subjectstringyesWhat was observed, e.g. api.stripe.com:POST:/v1/refunds, +18005551234:billing, or an error fingerprint.
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.

footnote-attach ~177

Attach footnote texts to their in-text markers from page layout coordinates — Given footnote markers (label, page, x, y) and footnote texts (label, page, x, y) extracted from a laid-out document, pairs each marker with its note by label and page, pairing repeated labels on one page in reading order, optionally letting a note continue on the next page, and reports unattached markers, orphan notes, ambiguous groups (different counts for the same label) and notes placed above

NameTypeReqDescription
allowNextPageboolean–A note may sit on the page after its marker. Default false.
markersarrayyes–
notesarrayyes–
yAxisstring–Direction of increasing y: down (PDF.js, screen) or up (PDF user space). Default down.

No output schema declared.

No examples provided.

hash-receipt ~193

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. For agents that need third-party evidence of what they did and when (action logs, generated files, prompts, tool outputs) without sending the data itself. Pure code, no model; verify free at /api/v1/verify-provenance.

NameTypeReqDescription
hashesarrayyesSHA-256 digests, 64 hex characters each. Hash your data locally; only the digests are sent.
labelstring–Optional caller label (run id, job id) included in the signed receipt.
proofsboolean–Return an inclusion proof per hash. Default true.

No output schema declared.

No examples provided.

hedge-extract ~149

Extract hedging and certainty cues (may, probably, clearly, approximately) from text with offsets — Finds hedge and booster cues in an agent's or source's text using a fixed English lexicon (modals, epistemic verbs, adverbs and adjectives, approximators, shield phrases, certainty boosters) plus caller-supplied phrases, and returns each cue with its category, the sentence it sits in, and offsets in UTF-16, code points, UTF-8 bytes and graphemes. Rule-based and English only: a cue is a word match,

NameTypeReqDescription
extraCuesarray–Caller cues added to the lexicon.
textstringyesText to scan.

No output schema declared.

No examples provided.

http-outcome ~229

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). Caller-supplied vendor rules (stat

NameTypeReqDescription
asOfstring–RFC 3339 instant; needed to turn an HTTP-date or epoch delay into seconds.
delayHeaderobject–Which header carries the wait and in what dialect. Default is Retry-After under RFC 9110.
headersarray–Response headers as name/value pairs (names compared case-insensitively).
idempotencyKeyobject––
methodstringyes–
statusintegeryes–
vendorRulesarray–First matching rule wins.

No output schema declared.

No examples provided.

id-block ~305

Monotonic id blocks: the next invoice or ticket numbers for a fleet of agents — Hands out strictly increasing integer blocks from a named sequence (1-1000 ids per call) so parallel agents never issue the same invoice, ticket or order number. Numbers are never reused. Not gapless: a block an agent reserves and never uses stays a gap, and if your call's payment fails after the block is written the same requestId returns that same block on retry. Legally gapless series must be a

NameTypeReqDescription
countinteger–Ids to reserve; default 1.
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…
sequencestringyesSequence name, e.g. invoice:2026.
startinteger–First id of a new sequence; ignored once it exists. Default 1.
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.

idempotency-fingerprint ~187

Derive a stable idempotency fingerprint from declared identity fields and flag volatile fields — Hashes the fields you declare as the identity of an operation (JSON Pointers into each request) with RFC 8785 canonical JSON and SHA-256, so retries of the same operation get the same fingerprint regardless of key order, and flags the ways that breaks: an identity field missing, an identity field also declared volatile, identity values that look like timestamps, epoch times or UUIDs (heuristic), a

NameTypeReqDescription
identityarrayyesJSON Pointers whose values define the operation's identity.
requestsarrayyes–
scopestring–Mixed into the hash (for example operation name and tenant) so equal bodies in different scopes get different fingerprints.
volatilearray–JSON Pointers declared to change per attempt (timestamps, nonces, request ids).

No output schema declared.

No examples provided.

idempotency-registry ~377

Idempotency registry: has key K already been done? Claim it, complete it, read the stored result — Shared memory for side-effecting operations across agents and retries. begin(key) answers proceed (you hold a short claim), wait (another owner is mid-flight), already_completed (returns the stored result pointer), or fingerprint_mismatch (same key, different operation). complete(key) records the result pointer; abandon(key) lets someone retry. The claim expires, so a crashed worker does not block

NameTypeReqDescription
claimSecondsinteger–How long a begin claim lasts; default 300.
fingerprintstring–Hash of the operation's identity fields; a later begin with a different fingerprint is refused.
keystringyesIdempotency key, e.g. refund:ch_123:2026-11-04.
opstringyes–
ownerstring–Worker id; required for begin, complete and abandon.
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…
resultobject–complete: where the outcome lives (do not store payloads here).
retentionHoursinteger–How long a completed key is remembered; default 24.
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.

inbox-create ~152

Receive-only inbox for agents without a public endpoint — Creates a receive-only inbox for an AI agent that has no public endpoint: a webhook URL that accepts POST or PUT, and (when the operator has configured inbound email) a unique email address. Pair with inbox-poll to read what arrived. It never sends email or calls out, does not store attachments, does not verify senders (no SPF/DKIM), and message content is untrusted third-party data. Inboxes live

NameTypeReqDescription
labelstring–Optional name for your own bookkeeping.
tenantIdstring–Required for API-key callers (namespace as key:<tenantId>; keep it unguessable). Ignored when a wallet paid.

No output schema declared.

No examples provided.

inbox-poll ~238

Read messages from a receive-only agent inbox — Returns the emails and webhook deliveries that arrived in an inbox you created with inbox-create, oldest first, with sender, subject, selected headers, a plain-text body (up to 64 KB per message in the response) and a sha256 of the stored body. Filter by since (inclusive), kind, limit up to 100; mark_consumed hides the returned messages from later polls unless include_consumed is true. It does not

NameTypeReqDescription
inbox_idstringyes–
include_consumedboolean–Also return consumed messages. Default false.
kindstring–Default all.
limitinteger–Default 50.
mark_consumedboolean–Mark the returned messages consumed. Default false.
since––Only messages received at or after this time: epoch milliseconds or ISO 8601 (UTC when no offset). Inclusive, so dedupe by id or use mark_consumed.
tenantIdstring–Required for API-key callers (namespace as key:<tenantId>; keep it unguessable). Ignored when a wallet paid.

No output schema declared.

No examples provided.

instruction-data-split ~149

Label spans of a prompt as pasted data or instructions, and flag instruction-like text inside the data — Splits an agent's input into data regions (code fences, block quotes, XML-style wrappers such as <document>, BEGIN/END markers, triple quotes, email headers with body, JSON blocks) and the text around them, labels each sentence outside the data as instruction (leading imperative verb or polite request) or unknown, and lists injection-style phrases found anywhere in the text ('ignore previous instr

NameTypeReqDescription
dataTagsarray–Extra XML-style tag names (letters, digits, underscore) whose content is data.
textstringyesThe full prompt or tool result to split.

No output schema declared.

No examples provided.

lease ~322

Short lease with fencing tokens: claim a task for N seconds, renew, release — Lets many agents agree which one works on a task: acquire a named resource for 1-3600 s, renew it while working, release it when done. Every new acquisition returns a strictly larger fencing token; pass it to the downstream store and reject writes carrying a smaller one, so a paused holder whose lease expired cannot clobber its successor. Re-acquiring as the current holder extends the lease with t

NameTypeReqDescription
holderstring–Your worker id. Required for acquire, renew and release.
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…
resourcestringyesTask or resource name, e.g. invoice:INV-1009 or deploy:prod.
tenantIdstring–Required for API-key callers (namespaced as key:<tenantId>; keep it unguessable). Ignored when a wallet paid: the payer address is the tenant.
tokeninteger–Fencing token from acquire; required for renew and release.
ttlSecondsinteger–Lease length; default 30.

No output schema declared.

No examples provided.

llm-watermark-detector ~332

Detect LLM text watermark evidence: green-list z-test for a key you hold, plus invisible-character markers — Tests whether text carries watermark evidence, for a pipeline that must decide whether to trust or label content. Two independent checks: (1) a green-list z-test (Kirchenbauer et al. 2023) over green flags you supply, or over token ids and a key using this endpoint's own HMAC-SHA256 scheme, returning the z-score and exact binomial p-value; (2) an invisible-character scan of the text for zero-width

NameTypeReqDescription
gammanumber–Expected green fraction under no watermark. Default 0.25.
greenFlagsarray–One 0/1 per scored token: 1 when your own detector's green list contains the token. Deduplicate repeated n-grams yourself if your scheme requires it.
keystring–Secret key for tokenIds. Used for this call only and never stored or echoed.
minTokensinteger–Fewer scored tokens than this is unknown. Default 25.
schemestring–Scheme for tokenIds; default and only value.
textstring–Text to scan for invisible markers.
tokenIdsarray–Token ids in order (at most 5000). Green membership is computed from the key with the hmac-sha256-green-1 scheme; each distinct consecutive pair is scored once.
zThresholdnumber–z at or above which the result is fail. Default 4 (Kirchenbauer et al.).

No output schema declared.

No examples provided.

log-collapse ~184

Collapse a log into error signatures with counts and first/last occurrence — Groups the records of a log or CI output by signature: timestamps, UUIDs, IPs, hex ids, quoted values and numbers are replaced by placeholders, stack-trace continuation lines are attached to their record and contribute their first frames, and each signature reports its count, severity, first and last line, first and last timestamp (as written, when the line starts with an ISO 8601 timestamp) and a

NameTypeReqDescription
minSeveritystring–Ignore records below this severity. Default: keep all.
signatureFramesinteger–Continuation lines (stack frames) that are part of the signature. Default 3.
textstringyesLog text, at most 8000 lines.
topNinteger–Signatures returned, by count. Default 20.

No output schema declared.

No examples provided.

markdown-syntax-shaper ~279

Normalize sloppy model-generated Markdown to one house style, leaving code untouched — Rewrites Markdown from a language model into a consistent style and reports each edit by line: restores the space in '##Title', converts '*', '+' and '•' bullets to your chosen marker, strips trailing whitespace (keeping two-space hard breaks), collapses runs of blank lines, puts blank lines around headings and fenced blocks, closes a fence left open at the end, and ends the file with one newline.

NameTypeReqDescription
blankLinesAroundBlocksboolean–Insert a blank line around headings and top-level fenced blocks. Default true.
bulletstring–Marker for unordered lists. Default '-'.
closeUnclosedFenceboolean–Append the closing fence when the document ends inside one. Default true.
collapseBlankLinesboolean–Collapse runs of blank lines and drop leading and trailing blanks. Default true.
finalNewlineboolean–End with exactly one newline. Default true.
fixHeadingSpaceboolean–Restore the space in '##Title'. A lowercase '#tag' at level 1 is treated as a hashtag and left alone. Default true.
markdownstringyesMarkdown to normalize.
stripTrailingWhitespaceboolean–Default true; a two-space hard break before more paragraph text is kept.

No output schema declared.

No examples provided.

mcp-tool-pin ~174

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. Returns a reproducible manifest hash, a per-tool hash, which tools were added, removed or changed since approval (silent description and schema edits are how MCP rug pulls and tool poisoning land), and Unicode smuggling findings in every name, description and schema string. Call it at sessi

NameTypeReqDescription
approvedManifestHashstring–manifestHash from the call you approved.
approvedToolsobject–Map of tool name to the per-tool hash you approved; enables the added/removed/changed diff.
toolsarrayyesThe tools array from an MCP tools/list response, as received.

No output schema declared.

No examples provided.

micro-batch ~127

Run up to 20 micro checks under one payment ($0.02) — Bundles up to 20 calls to any pure micro check (catalog entries that are neither stateful nor network-reading, e.g. checksum, patch-anchor, allocate, business-deadline) into one x402 settlement, so a full batch costs $0.001 per check. Every call is validated before payment; one invalid call rejects the batch with its index. The request is capped at 128kb and a CPU weight of 40 (an ordinary check w

NameTypeReqDescription
callsarrayyes–

No output schema declared.

No examples provided.

mutation-intent ~194

Diff a before/after JSON write for deletes, null-vs-omit and emptied arrays against protected paths — Compares the JSON document an agent read (before) with the one it is about to write (after) and lists every change by JSON Pointer: removed members, null turned into omitted (and the reverse), arrays emptied or shrunk, objects emptied, type changes. Fails when a change touches a protected path or is destructive and not listed in allowDestructive; use it before a PUT, PATCH or bulk update. Arrays a

NameTypeReqDescription
after–yesJSON value about to be written.
allowDestructivearray–JSON Pointers ("*" wildcard) under which deletes, emptied containers and type changes are intended.
before–yesJSON value as last read.
protectedPathsarray–JSON Pointers that must not change at all; a "*" token matches any one key or index.

No output schema declared.

No examples provided.

negation-scope ~181

Find negation cues and the words they cover; report whether given terms fall inside a negation scope — Applies NegEx-style rules (the English termset of negspacy, MIT, derived from NegEx) to text: finds negation cues, pseudo-negations such as 'not only', and scope terminators such as 'but', and returns each cue's scope window with offsets in UTF-16, code points, UTF-8 bytes and graphemes. Given target terms, reports per occurrence whether it is negated, not negated by the rules, or unknown (near a

NameTypeReqDescription
targetsarray–Terms to classify (literal, case-insensitive, whole words).
textstringyesText to analyze.
windowinteger–Words a cue covers (NegEx uses 5). Default 5.

No output schema declared.

No examples provided.

pacing-intensity-evaluator ~277

Plot a prose intensity curve per sentence and flag where a tense passage loses velocity — Scores each sentence of narrative prose for pace from sentence length, share of one-syllable words, exclamation and question marks and, if you supply a word list, action-word share; smooths the scores into an intensity curve; and reports stalls, the spans where intensity falls well below an earlier peak. For a writing tool or editor agent checking an action or tension scene. A fixed-weight heurist

NameTypeReqDescription
actionWordsarray–Your own action-word list. Without it the action component is left out and the other weights are renormalized.
expectstring–tense: fail if the curve never reaches peakThreshold. any (default): only stalls after a peak can fail.
minSentencesinteger–Fewer scored sentences is unknown. Default 8.
peakThresholdnumber–Smoothed intensity a passage must reach before a later fall can be a stall. Default 0.55.
stallDropnumber–Fall below the running peak that counts as a stall. Default 0.25 on the 0-1 intensity scale.
textstringyesProse to score.
windowinteger–Sentences in the trailing moving average. Default 3.

No output schema declared.

No examples provided.

pagination-loop ~121

Detect repeated cursors, duplicate-only pages and no progress in a pagination scan — Takes the pages an agent has fetched so far (cursor used, next cursor returned, item ids) and finds the failures that make a scan loop or lie: a next cursor already used, a page whose items were all seen before, a page that returned nothing new yet offers another cursor, a scan that has not ended. Optionally takes declared ordering and cursor assumptions and lists the omission risks they imply (of

NameTypeReqDescription
declaredobject––
pagesarrayyes–

No output schema declared.

No examples provided.

patch-anchor ~216

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. Each hunk is located by its content against the original file, trying exact, trailing-whitespace, outer-whitespace then collapsed-whitespace matching; the rung used is reported per hunk. I

NameTypeReqDescription
diffstring–Single-file unified diff, at most 64 hunks and 400 anchor lines each. Header counts and line numbers are ignored except as a reported hint. Give either diff or edits.
editsarray–Search/replace blocks, matched as whole lines against the original file; all are located before any is applied.
filestringyesCurrent file text, at most 524288 UTF-8 bytes and 100000 lines. A leading BOM is preserved.

No output schema declared.

No examples provided.

permission-intersection ~171

Effective permissions of a delegated agent: requested ∩ user ∩ parent, minus explicit denials — Computes what a sub-agent may actually do: the permissions it requested, intersected with what the end user holds and what its parent agent holds, minus any explicit deny list, and says for each denied permission which party lacks it. Permission names are compared exactly (no wildcards); caller-declared implications (for example 'admin' grants 'read') can be given and are expanded transitively wit

NameTypeReqDescription
deniedarray–Explicit denials; they win over any grant.
impliesarray––
parentarrayyesPermissions held by the delegating agent.
requestedarrayyesPermissions the delegate asks for.
userarrayyesPermissions held by the end user.

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.