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 developer agents

REMOTE · AGENTS.WRITERSLOGIC.COM

Diff gatekeeper, pre-merge review, unicode safety, SMT prover, dependency advisor.

64 Trust /100

Last scanned (15 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

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 69 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 Usability56
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 14895 tokens (~215/item across 69 items; 69 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 Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 86% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "lockfile-merge" implies "merge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 70 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 69 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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 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 61

    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/developer

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/developer Verified 200
http (plaintext) http://agents.writerslogic.com/mcp/developer HTTPS enforced 301 https://agents.writerslogic.com/mcp/developer
MCP tools · 69 exposed · ~14,842 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
robots-check ~333

robots.txt (RFC 9309) rule reading with llms.txt and AI-use signals — Reads a supplied robots.txt the RFC 9309 way for an agent deciding whether to fetch up to 25 paths as one product-token user agent: group selection (merged groups, "*" fallback), longest-match with the Allow-wins-tie rule, "*" and "$" patterns, percent-encoding normalization, fetch-status handling (4xx = no rules, 5xx = disallow all), the rule and line that decided each path. It also lints a suppl

NameTypeReqDescription
fetchStatusinteger–HTTP status the robots.txt fetch ended with (after at most 5 redirects). Omit when robotsTxt is supplied and was a 2xx.
headersarray–Response headers of the page: X-Robots-Tag, tdm-reservation, tdm-policy.
llmsTxtstring––
metaTagsarray–HTML meta elements: robots, googlebot, tdm-reservation, tdm-policy.
pathsarrayyesPath plus optional query beginning with /, or a full http(s) URL (path and query are used).
purposestring–ai-training also treats noai, noimageai and tdm-reservation: 1 as restrictions. Default crawl.
robotsTxtstring–robots.txt body, at most 512,000 UTF-8 bytes (500 KiB).
userAgentstringyesProduct token only (letters, underscore, hyphen), e.g. "Googlebot"; no version.

No output schema declared.

No examples provided.

schema-compat ~217

Breaking-change diff between two JSON Schemas or OpenAPI documents, and whether cached calls still validate — Compares an old and a new JSON Schema 2020-12 (or two OpenAPI 3.0/3.1 documents) and lists each change with its path, keyword, old and new value, whether it narrows or widens what is accepted, and whether it breaks clients: newly required properties, removed or retyped properties, removed enum values, tightened limits, additionalProperties flips, removed operations, removed or newly required param

NameTypeReqDescription
after–yesThe new schema, or new OpenAPI document. Full JSON Schema 2020-12 (local $ref only).
before–yesThe old schema, or old OpenAPI document. Full JSON Schema 2020-12 (local $ref only).
callsarray––
kindstringyes–
rolestring–json-schema only: request (default) or response; OpenAPI compares each side in its own role.

No output schema declared.

No examples provided.

schema-repair ~169

Repair a JSON value toward a schema using only the coercions the caller declares — Validates a JSON value against a caller-supplied JSON Schema 2020-12 and applies only the coercions you list (for example string-to-integer for "42", trim-strings, enum-case, apply-defaults, drop-additional) when each one strictly reduces the number of schema errors. Every change is returned with its JSON pointer, the rule, the old and new value; every error that remains is returned with its exact

NameTypeReqDescription
coercionsarrayyesCoercions you allow. Empty means validate only.
schema–yesThe schema the value must satisfy. Full JSON Schema 2020-12 (local $ref only).
value–yesThe JSON value to repair.

No output schema declared.

No examples provided.

schema-witness ~154

One valid and one invalid example for each constraint in a JSON Schema — Walks a caller-supplied JSON Schema 2020-12 and, for every constraint keyword (type, enum, const, minimum, maximum, exclusiveMinimum, exclusiveMaximum, multipleOf, minLength, maxLength, pattern, format, minItems, maxItems, uniqueItems, required, minProperties, maxProperties, additionalProperties false, dependentRequired), returns the JSON pointer of the constraint, an example that satisfies it and

NameTypeReqDescription
maxConstraintsinteger–Stop after this many constraints (default 100).
schema–yesThe schema to generate examples for. Full JSON Schema 2020-12 (local $ref only).

No output schema declared.

No examples provided.

semver-check ~225

Version range check: npm, PEP 440, Cargo, Maven — Parses a dependency version range in npm (node-semver), PEP 440 specifier, Cargo requirement or Maven range syntax and tests up to 100 candidate versions against it, for agents that write or review manifests. Returns per-version satisfies/violates with the failing comparator, the normalized range, the sorted versions and the highest match; pre-release, caret on 0.x, epoch and local-version rules f

NameTypeReqDescription
ecosystemstringyesWhich range syntax and version ordering to apply.
prereleasesboolean–npm includePrerelease / PEP 440 prereleases=true. Default false (ecosystem default exclusion applies).
rangestringyesThe range: npm '^1.2.3 || >=2', PEP 440 '>=1.0,<2', Cargo '>=1.2, <1.5', Maven '[1.0,2.0)'.
versionsarray–Candidate versions to test; omit to only validate the range.

No output schema declared.

No examples provided.

sentinel-values ~123

Placeholder values hiding as data: caller-declared sentinels and likely candidates — Scans columns of values for sentinels. Values you declare in a dictionary (for example -1 means unknown in column age) are reported as asserted hits with their row paths. Other values that look like missing-data markers are reported separately as candidates, never asserted: the pandas default NA strings, spreadsheet error values, whitespace-only text, placeholder words, zero and epoch dates, fixed

NameTypeReqDescription
columnsarrayyes–
dictionaryarray–Values you know are sentinels.

No output schema declared.

No examples provided.

shell-quote ~159

Shell quoting for bash, PowerShell and cmd.exe with a parse-back check — Turns up to 50 literal strings into a safely quoted argument for bash/sh (POSIX single-quote method), PowerShell (single-quoted literal) and cmd.exe, for agents that build a command line from untrusted or free-form text, and parses each result back with a model of that shell's rules to prove it yields the original string. It returns `unsupported` for strings cmd.exe cannot carry safely (line break

NameTypeReqDescription
targetsarray–Shells to quote for; default all three. Status is unsupported when any requested target cannot carry a value.
valuesarrayyesLiteral argument values; at most 100000 characters in total.

No output schema declared.

No examples provided.

smt-contract-prover ~381

SMT Contract & Policy Logic Prover — Answers a yes/no logic question about contract clauses, IAM/OPA policies or business rules with a solver-backed result and a plain-language headline and next step. Takes clauses or pasted text (or a formal IR directly with zero LLM calls), formalizes them into typed Boolean, integer and rational constraints, then answers "is P possible", "does invariant I always hold" or "are any clauses contradic

NameTypeReqDescription
budgetobject–Optional lower step budgets.
clausesarray–Natural-language contract clauses, IAM/OPA policy statements or business rules, each with a caller-chosen id. Mutually exclusive with ir.
irobject–Formal IR, solved with zero LLM calls: {variables:[{name,type:bool|int|real,min?,max?}], constraints:[{id,expr,source?}], query:{mode:possible|always|consistency,formula?,source?}}. Expressions are J…
querystring–The question, e.g. "Can an unauthorized user ever approve a payout over $10,000?" or "Are any clauses mutually contradictory?". Required with clauses.
textstring–Alternative to clauses: the contract, policy or rules pasted as plain text. It is split into clauses by blank lines and numbered or bulleted lines (ids C1.2 or S3). Use clauses when you need your own…

No output schema declared.

No examples provided.

spdx-policy ~349

SPDX license expression parse and policy check — Parses up to 50 SPDX license expressions (AND, OR, WITH exceptions, + or-later, LicenseRef) and evaluates each against a caller policy (allow list, deny list, allowed exceptions, OSI/FSF flags, copyleft tier) for agents vetting dependency licenses. Returns the canonical expression, per-license flags from the pinned SPDX License List, the verdict, and which licenses satisfy an OR. Does not detect l

NameTypeReqDescription
allowarray–If non-empty, only these SPDX ids pass (GPL-2.0-only and GPL-2.0 are the same entry; GPL-2.0+ means or-later and must be listed as such).
allowDeprecatedboolean–Default true: deprecated ids only add a witness. false: they fail.
allowExceptionsarray–If non-empty, only these WITH exception ids pass.
allowLicenseRefsarray–LicenseRef-* ids the caller has reviewed; other refs yield unknown.
denyarray–SPDX ids that always fail.
denyCopyleftstring–Id-family heuristic: strong = GPL/AGPL/SSPL/EUPL/OSL/CC-BY-SA; any adds LGPL/MPL/EPL/CDDL and similar.
expressionsarrayyesSPDX expressions, e.g. 'MIT OR (GPL-2.0-only WITH Classpath-exception-2.0)'.
requireFsfLibreboolean–Fail licenses without isFsfLibre in the SPDX list.
requireOsiApprovedboolean–Fail licenses without isOsiApproved in the SPDX list.

No output schema declared.

No examples provided.

sql-check ~193

SQL guard: single statement, read-only, table allowlist — Checks one SQL string (up to 20000 characters; PostgreSQL, MySQL, SQLite or generic) before an agent executes it: exactly one statement, read-only (SELECT/VALUES/SHOW/EXPLAIN without side effects), and every table it reads or writes on a caller allowlist. Tokenizer-level: comments, string literals, quoted identifiers and dollar quoting cannot hide a second statement; reports statement kind, refere

NameTypeReqDescription
allowedTablesarray–Allowed tables, lower-cased match: 'users', 'public.users' or 'public.*'. Unqualified and qualified names are different entries.
dialectstring–Lexical rules; default ansi.
readOnlyboolean–Default true: anything but a plain read fails.
sqlstringyes–
transpileTostring–Always answered unsupported.

No output schema declared.

No examples provided.

state-model-checker ~366

State Machine Model Checker — Returns PASS, FAIL or INCONCLUSIVE for a finite state machine, protocol, or concurrent routine, with the shortest failing path as readable process.transition steps and a next step. Accepts a formal spec (no LLM), a plain-language workflow, or source code (translated to a spec by an LLM, with every transition quoted from the source and two independent translations compared). A pure TypeScript expli

NameTypeReqDescription
codestring–Source code of a state machine, protocol, or concurrent routine; translated to a spec by an LLM, with each transition carrying its verbatim source span.
descriptionstring–Natural-language workflow or protocol; translated to a spec by an LLM, with each transition quoted from the text.
optionsobject––
propertiesarray–Properties to check, in plain language (with description or code only).
specobject–Formal spec (zero LLM calls). {vars:{name:{type:'bool'|'int'|'enum'|'array',min,max,values,size|keys,of,init}}, processes:[{name,instances?,fairness?:'none'|'weak'|'strong',transitions:[{name,guard?,…

No output schema declared.

No examples provided.

svg-geometry ~313

SVG layout check: clipping, overlaps and empty shapes from supplied geometry — Checks up to 200 SVG shapes you describe (rect, circle, ellipse, line, polygon, polyline, text, or a path's bounding box) against the viewBox and viewport the way an SVG renderer would: finds shapes clipped or entirely outside the drawn region, shapes that render nothing (zero or negative size, unstroked line), partial overlaps between shapes, and a zero, negative or malformed viewBox, for agents

NameTypeReqDescription
checksarray–Subset of clip, empty, overlap; default all. Overlap reports partial overlaps only; a shape fully inside another (a label on a card) is listed as nested and never fails.
heightnumber–Viewport height in px.
preserveAspectRatiostring–Default xMidYMid meet.
shapesarrayyesShapes in user coordinates (no transform). rect: x,y,width,height. circle: cx,cy,r. ellipse: cx,cy,rx,ry. line: x1,y1,x2,y2,strokeWidth. polygon/polyline: points. text: x,y,text,fontSize,textAnchor.…
viewBoxstring–The viewBox attribute value, e.g. "0 0 800 600".
widthnumber–Viewport width in px (the svg width attribute).

No output schema declared.

No examples provided.

symbol-exists ~179

Is this export in the npm package's published type declarations — Checks that up to 20 named exports (functions, classes, constants, types, default) exist in the .d.ts files published for an exact npm package version, read from jsDelivr, for coding agents that may be calling an API that does not exist. Follows export lists and relative export-star re-exports within the package (at most 7 files) and reports when the export surface cannot be fully enumerated. Neve

NameTypeReqDescription
entrystring–package.json exports key, default '.'.
packagestringyesnpm package name.
symbolsarrayyes–
typesPathstring–Declaration file path inside the package, overriding package.json resolution.
versionstringyesExact version or dist-tag (jsDelivr resolves it).

No output schema declared.

No examples provided.

unicode-safety-gate ~367

Adversarial Unicode & Trojan Source gatekeeper — Scans a public GitHub repo, a pull request, a unified diff or a list of files for adversarial Unicode with the 19 rules (USC001-USC019) of dcondrey/unicode-safety-check: bidi controls (Trojan Source), invisible and default-ignorable characters, variation-selector and tag-character payloads (Glassworm), private-use code points, homoglyph and mixed-script identifiers, confusable collisions, misplace

NameTypeReqDescription
diffstring–Unified diff (git diff output). Only added lines are scanned; findings carry new-file line numbers.
filesarray–Files to scan in full. Provide exactly one of files, diff, repo or prUrl; total content is capped at 1000000 characters.
identifierPolicystring–Default ascii-only: any non-ASCII identifier is flagged (USC019).
permittedScriptsarray–Used with permitted-scripts. Default Latin, Common, Inherited.
prUrlstring–Alternative to files and diff: a public GitHub pull request, commit or compare URL. Only added lines are scanned.
refstring–Branch, tag or commit for repo; defaults to the default branch.
repostring–Alternative to files and diff: a public GitHub repository, owner/repo or https://github.com/owner/repo[/tree/ref]. Read from its source archive; files are scanned shallowest first up to the character…
scanExcludedboolean–Also scan paths the upstream scanner skips (node_modules/, vendor/, dist/, build/, .lock, .min.js, images, archives). Default false.

No output schema declared.

No examples provided.

union-branch ~204

Which oneOf / anyOf branch a JSON value matches, or why several or none do — Evaluates a JSON value against every branch of a oneOf or anyOf in a caller-supplied JSON Schema 2020-12 (or OpenAPI schema converted to it) and reports which branches match, the exact errors of each branch that fails with the JSON pointer of each offending value, the closest branch, and which branch an OpenAPI `discriminator` points to. For agents debugging why a tool or API payload is rejected w

NameTypeReqDescription
atstring–JSON pointer to the subschema holding the union ("" for the root, "/properties/pet" for a nested one).
keywordstring–Required only when the subschema has both.
schema–yesThe root schema; $ref targets are resolved inside it. Full JSON Schema 2020-12 (local $ref only).
value–yesThe JSON value to classify.

No output schema declared.

No examples provided.

url-canonicalize ~197

URL canonicalizer and lookalike-host check — Canonicalizes up to 50 absolute http(s) URLs for an agent about to fetch, dedupe or click them: WHATWG-parsed lowercase host, default port and fragment and userinfo removed, dot segments and unreserved percent-escapes normalized, tracking parameters (utm_*, gclid, fbclid and the Mozilla strip list plus yours) removed, and flags userinfo@host tricks, backslash and multiple-@ authorities, obfuscated

NameTypeReqDescription
extraTrackingParamsarray–Extra query parameter names to strip (case-insensitive).
publicSuffixesarray–Extra public suffixes (e.g. "co.xx") used for registrable-domain decisions.
sortQueryboolean–Sort remaining query segments for a dedupe key. Off by default: order can matter to servers.
urlsarrayyesAbsolute URLs including the scheme.

No output schema declared.

No examples provided.

web-search ~181

Web search: licensed Exa/Brave results with snippets — Runs a web search through a licensed search API (Exa or Brave) and returns up to 10 ranked results with title, URL, snippet, highlights and published date, for agents that need current links. Does not scrape search engines, does not fetch or summarize the result pages (use page-contents for that), and does not use a model.

NameTypeReqDescription
date_fromstring–Only results published on or after this date, YYYY-MM-DD.
include_textboolean–Ask the provider for highlights/extra snippet text per result.
num_resultsinteger––
providerstring–auto uses Exa when configured, else Brave.
querystringyesSearch query.
sitestring–Restrict to a domain, for example example.com.

No output schema declared.

No examples provided.

webhook-verify ~272

Verify webhook signatures from 8 providers — Constant-time verification of inbound webhook signatures from Stripe, GitHub, Shopify, Slack, Twilio, Linear, Clerk (Svix) and SendGrid HMAC, each using the exact signing string that provider documents. Every scheme uses Web Crypto HMAC with a timing-safe compare and, where the provider signs a timestamp, a configurable clock-skew tolerance (default 300s) to block replay. Returns the verdict and t

NameTypeReqDescription
formParamsobject–Form parameters parsed from a Twilio POST (string values); order does not matter.
headersobjectyesRequest headers as sent by the provider (string values). Names are case-insensitive.
nowIsostring–Override 'now' for deterministic tests; ISO-8601 instant.
rawBodystringyesThe exact request body bytes as a string. Reparsed JSON will not match; send the raw bytes.
secretstringyesThe signing secret; for Clerk/Svix a 'whsec_<base64>' value is accepted.
sourcestringyes–
toleranceSecondsinteger–Max allowed |now - signed timestamp|. Default 300s.
urlstring–Full request URL. Required for Twilio, ignored elsewhere.

No output schema declared.

No examples provided.

wheel-availability ~188

Is there a compatible PyPI wheel for this Python and platform — Lists the wheels PyPI offers for a package release and picks those compatible with a given CPython version, OS, CPU architecture and libc (glibc or musl version, or macOS version), best match first, for agents choosing base images or debugging 'building from source' installs. Applies PEP 425/600/656 tag ordering, abi3, legacy manylinux aliases, Requires-Python and yanked files. CPython only (no Py

NameTypeReqDescription
freeThreadedboolean–Free-threaded build (cp313t): abi3 wheels do not apply.
packagestringyesPyPI project name.
platformobjectyes–
pythonstringyesCPython major.minor, e.g. 3.12.
versionstring–Release; default latest.

No output schema declared.

No examples provided.

Install

How do I install the WritersLogic developer agents MCP server?

WritersLogic developer agents is a hosted endpoint at https://agents.writerslogic.com/mcp/developer, 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-developer 'https://agents.writerslogic.com/mcp/developer'
Common questions

What is the WritersLogic developer agents MCP server?

WritersLogic developer agents is an MCP server listed in the public MCP registry as com.writerslogic.agents/writerslogic-developer. Diff gatekeeper, pre-merge review, unicode safety, SMT prover, dependency advisor. This page covers its hosted endpoint (https://agents.writerslogic.com/mcp/developer).

Is the WritersLogic developer agents MCP server safe to use?

WritersLogic developer agents scores 64 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 developer agents MCP server expose?

WritersLogic developer agents exposes 69 tools: heal-scraper, diff-gatekeeper, unicode-safety-gate, smt-contract-prover, ai-bom-license-resolver, and 64 more. Their descriptions and schemas cost roughly 14,842 tokens of context every time the server is loaded.

Does the WritersLogic developer agents MCP server require authentication?

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

Is the WritersLogic developer agents MCP server still maintained?

WritersLogic developer agents 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 developer agents MCP server?

VerifyMCP ran 12 checks on WritersLogic developer agents, 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 developer agents: 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.