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 verifiable AI agents

REMOTE · AGENTS.WRITERSLOGIC.COM

262 deterministic, x402-paid agents for audit, research, patents, and dev review.

64 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 262 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 Usability55
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 59137 tokens (~225/item across 262 items; 262 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 Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 82% 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 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "storage-charge-clock" implies "charge" 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 263 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 262 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
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 20 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 19 Nov 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 18 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 17 Nov 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 16 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day 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

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 Verified 200
http (plaintext) http://agents.writerslogic.com/mcp HTTPS enforced 301 https://agents.writerslogic.com/mcp
MCP tools · 262 exposed · ~59,084 tokens partial

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
contract-terminator ~290

No description provided.

NameTypeReqDescription
accountIdentifierstring––
annualFeenumber––
contractStartDatestring––
contractTextstring––
customerNamestring––
customerTypestring––
earlyTerminationFeeUsdnumber––
monthlyFeenumber––
reasonForExitstringyes–
signupMethodstring––
termsUrlstring––
userJurisdictionstringyes–
vendorNamestringyes–

No output schema declared.

No examples provided.

contrast-fix ~342

No description provided.

NameTypeReqDescription
cvdMinDeltaEnumber––
cvdSeveritynumber––
fixTargetstring––
levelstring––
pairsarrayyes–
thresholdnumber––

No output schema declared.

No examples provided.

conversation-prune ~244

No description provided.

NameTypeReqDescription
cacheBreakpointintegeryes–
keepRecentinteger––
messagesarrayyes–
strategystring––
targetTokensintegeryes–
tokenizerstring––

No output schema declared.

No examples provided.

cors-preflight ~122

No description provided.

NameTypeReqDescription
policyobjectyes–
requestobjectyes–

No output schema declared.

No examples provided.

cover-claim ~276

No description provided.

NameTypeReqDescription
claimDatestring––
claimantstringyes–
claimedLossobject––
coverobjectyes–
deductibleobject––
incidentobject––
transactionsarray––
wordingobjectyes–

No output schema declared.

No examples provided.

cra-exploit-clock ~453

No description provided.

NameTypeReqDescription
awareness_timestring––
fix_available_atstring––
issue_recordboolean––
productobject––
purlsarray––
sbom–––

No output schema declared.

No examples provided.

cra-readiness ~368

No description provided.

NameTypeReqDescription
awareness_timestring––
ecosystemsarray––
filesarray––
fix_available_atstring––
productobject––
refstring––
repostring––
repoLicensestring––

No output schema declared.

No examples provided.

credential-coverage ~169

No description provided.

NameTypeReqDescription
checkpointsarray––
credentialsarrayyes–
requiredobjectyes–
toleratedGapDaysinteger––

No output schema declared.

No examples provided.

cron-explain ~264

No description provided.

NameTypeReqDescription
afterstring––
countinteger––
expressionstringyes–
flavorstring––
timezonestring––

No output schema declared.

No examples provided.

cross-field-rules ~174

No description provided.

NameTypeReqDescription
data–yes–
onMissingstring––
rulesarrayyes–

No output schema declared.

No examples provided.

cross-reference-check ~154

No description provided.

NameTypeReqDescription
textstringyes–

No output schema declared.

No examples provided.

crosstalk-deliberate ~222

No description provided.

NameTypeReqDescription
contextstring––
maxHypothesesinteger––
papersarray––
questionstringyes–

No output schema declared.

No examples provided.

csp-audit ~143

No description provided.

NameTypeReqDescription
deployTargetstring––
policystringyes–

No output schema declared.

No examples provided.

csv-dialect ~145

No description provided.

NameTypeReqDescription
textstringyes–

No output schema declared.

No examples provided.

csv-roundtrip ~256

No description provided.

NameTypeReqDescription
dialectobject––
nullTokenstring––
spreadsheetboolean––
textstringyes–
types–––

No output schema declared.

No examples provided.

date-claim-check ~147

No description provided.

NameTypeReqDescription
fromYearinteger––
itemsarrayyes–
toYearinteger––

No output schema declared.

No examples provided.

deadline-feasibility ~157

No description provided.

NameTypeReqDescription
overheadMsinteger––
remainingMsintegeryes–
stepsarrayyes–

No output schema declared.

No examples provided.

dedup-window ~164

No description provided.

NameTypeReqDescription
historyarrayyes–
incomingobjectyes–
windowModestring––
windowSecondsintegeryes–

No output schema declared.

No examples provided.

deictic-check ~173

No description provided.

NameTypeReqDescription
anchorobject––
candidatesarray––
textstringyes–

No output schema declared.

No examples provided.

delegation-contract-check ~206

No description provided.

NameTypeReqDescription
acceptanceCriteriaarray––
budgetobject––
evidenceRequiredarray––
objectivestring––
outputFormatstring––
requirearray––
stopConditionsarray––

No output schema declared.

No examples provided.

dependency-advisor ~282

No description provided.

NameTypeReqDescription
ecosystemsarray––
filesarray––
modestring––
refstring––
repostring––
repoLicensestring––

No output schema declared.

No examples provided.

dev-pipeline-toolkit ~208

No description provided.

NameTypeReqDescription
argsobjectyes–
toolstringyes–

No output schema declared.

No examples provided.

dice-roll ~251

No description provided.

NameTypeReqDescription
expectRollsarray––
expectTotalinteger––
includeTranscriptboolean––
notationstringyes–
seedstringyes–

No output schema declared.

No examples provided.

diff-gatekeeper ~269

No description provided.

NameTypeReqDescription
contextstring––
filesarray––
gitDiffstring––
packageJsonDiffstring––
prUrlstring––

No output schema declared.

No examples provided.

dispute-ev ~196

No description provided.

NameTypeReqDescription
evidenceUrlsarray––
marketstringyes–
paramsobject––
positionobject––
pricesobject––
proposalobject––

No output schema declared.

No examples provided.

doc-to-markdown ~290

No description provided.

NameTypeReqDescription
content_base64string––
describeboolean––
filenamestring––
formatstring––
max_charsinteger––
pagesstring––
urlstring––

No output schema declared.

No examples provided.

dockerfile-cache-lint ~178

No description provided.

NameTypeReqDescription
basePinstring––
dockerfilestringyes–
includearray––

No output schema declared.

No examples provided.

document-supersession ~191

No description provided.

NameTypeReqDescription
asOfstringyes–
documentsarrayyes–
listCompleteboolean––
targetstringyes–

No output schema declared.

No examples provided.

doi-check ~146

No description provided.

NameTypeReqDescription
doisarrayyes–

No output schema declared.

No examples provided.

dom-recipe-match ~140

No description provided.

NameTypeReqDescription
htmlstringyes–
recipeobjectyes–
savedarrayyes–

No output schema declared.

No examples provided.

dom-skeleton ~162

No description provided.

NameTypeReqDescription
dedupeboolean––
htmlstringyes–
maxElementsinteger––

No output schema declared.

No examples provided.

dst-check ~130

No description provided.

NameTypeReqDescription
itemsarrayyes–
transitionsInobject––

No output schema declared.

No examples provided.

duplicate-key-audit ~139

No description provided.

NameTypeReqDescription
textstringyes–

No output schema declared.

No examples provided.

edit-anchor-check ~164

No description provided.

NameTypeReqDescription
contextLinesinteger––
filestringyes–
oldStringstringyes–

No output schema declared.

No examples provided.

electrical-calc ~617

No description provided.

NameTypeReqDescription
areaMm2number––
bandCountinteger––
bandsarray––
claimobject––
claimTolerancePctnumber––
currentnumber––
forwardVoltagenumber––
lengthMnumber––
maxDropPercentnumber––
opstringyes–
powernumber––
r1number––
r2number––
rLoadnumber––
resistancenumber––
resistancesarray––
resistivityOhmMnumber––
roundTripboolean––
seriesstring––
supplyVoltagenumber––
tcrPpmnumber––
tolerancePctnumber––
vinnumber––
voltagenumber––

No output schema declared.

No examples provided.

enum-canonicalize ~205

No description provided.

NameTypeReqDescription
aliasesarray––
allowedarrayyes–
caseSensitiveboolean––
maxDistanceinteger––
valuesarrayyes–

No output schema declared.

No examples provided.

evidence-bundle-check ~215

No description provided.

NameTypeReqDescription
asOfstring––
claimsarrayyes–
evidencearrayyes–
maxAgeDaysinteger––
requireQuotesboolean––

No output schema declared.

No examples provided.

evidence-scope-mismatch ~184

No description provided.

NameTypeReqDescription
claimobjectyes–
evidenceobjectyes–
taxonomyarray––

No output schema declared.

No examples provided.

exif-report ~178

No description provided.

NameTypeReqDescription
datastringyes–
forbidarray––

No output schema declared.

No examples provided.

exposure-calc ~204

No description provided.

NameTypeReqDescription
aperturenumber––
ev100number––
isonumber––
shutterSecondsnumber––
toleranceStopsnumber––

No output schema declared.

No examples provided.

farmland-soil-report ~174

No description provided.

NameTypeReqDescription
addressstring––
latnumber––
lonnumber––
usestring––

No output schema declared.

No examples provided.

filing-integrity-check ~296

No description provided.

NameTypeReqDescription
accessionstring––
checksarray––
cikstring––
fiscal_yearinteger––
periodstring––
rounding_modestring––
tickerstring––

No output schema declared.

No examples provided.

fiscal-period ~345

No description provided.

NameTypeReqDescription
endMonthinteger––
endRulestring––
endWeekdayinteger––
itemsarrayyes–
patternstring––
startMonthinteger––
typestringyes–
yearLabelstringyes–

No output schema declared.

No examples provided.

fleet-memory ~313

No description provided.

NameTypeReqDescription
namespacestringyes–
observationsarray––
opstringyes–
requestIdstring––
sinceHoursinteger––
subjectstringyes–
tenantIdstring––

No output schema declared.

No examples provided.

float-stability ~257

No description provided.

NameTypeReqDescription
alternativestring––
expressionstringyes–
maxDigitsLostinteger––
precisionstring––
variablesarrayyes–

No output schema declared.

No examples provided.

font-convert ~194

No description provided.

NameTypeReqDescription
fontBase64stringyes–
tostringyes–

No output schema declared.

No examples provided.

font-coverage ~203

No description provided.

NameTypeReqDescription
fontBase64stringyes–
fontSizePxnumber––
maxWidthPxnumber––
textstringyes–

No output schema declared.

No examples provided.

font-face-css ~248

No description provided.

NameTypeReqDescription
familystring––
fontBase64stringyes–
fontDisplaystring––
includeUnicodeRangeboolean––
sourcesarrayyes–

No output schema declared.

No examples provided.

font-glyph-svg ~201

No description provided.

NameTypeReqDescription
fontBase64stringyes–
fontSizePxnumber––
textstringyes–

No output schema declared.

No examples provided.

footnote-attach ~177

No description provided.

NameTypeReqDescription
allowNextPageboolean––
markersarrayyes–
notesarrayyes–
yAxisstring––

No output schema declared.

No examples provided.

Install

How do I install the WritersLogic verifiable AI agents MCP server?

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

What is the WritersLogic verifiable AI agents MCP server?

WritersLogic verifiable AI agents is an MCP server listed in the public MCP registry as com.writerslogic.agents/writerslogic-agents. 262 deterministic, x402-paid agents for audit, research, patents, and dev review. This page covers its hosted endpoint (https://agents.writerslogic.com/mcp).

Is the WritersLogic verifiable AI agents MCP server safe to use?

WritersLogic verifiable AI 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.

Does the WritersLogic verifiable AI agents MCP server require authentication?

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

Is the WritersLogic verifiable AI agents MCP server still maintained?

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

VerifyMCP ran 12 checks on WritersLogic verifiable AI 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 verifiable AI 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.