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

REMOTE · AGENTS.WRITERSLOGIC.COM

Smart-contract audit, token due diligence, prediction-market EV, vault exit analysis.

65 Trust /100

Last scanned (12 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

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 12 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 Usability53
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2751 tokens (~229/item across 12 items; 12 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
  • 83% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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 12 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 62

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

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/crypto Verified 200
http (plaintext) http://agents.writerslogic.com/mcp/crypto HTTPS enforced 301 https://agents.writerslogic.com/mcp/crypto
MCP tools · 12 exposed · ~2,698 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
arbitrage-lawyer ~221

Cross-Platform Arbitrage & Resolution Rules Lawyer — Finds fine-print divergences between two prediction markets (e.g. Polymarket vs Kalshi), prices basis risk after fees, and returns verdict.action ARBITRAGE_SAFE / LOW_ANNUALIZED_YIELD / BASIS_RISK_TRAP / NO_EDGE / INSUFFICIENT_EVIDENCE with edge in bps, the probability both legs lose, days to resolution, annualized return and Kelly hedge size capped by top-of-book depth. Each market can be given a

NameTypeReqDescription
bankrollUsdnumber–Used to convert the Kelly fraction to USD.
marketAobjectyes–
marketBobjectyes–
minAnnualizedReturnPctnumber–Minimum annualized risk-adjusted return, in percent, for verdict.action ARBITRAGE_SAFE (default 5). Below it the action is LOW_ANNUALIZED_YIELD. Applied only when both end dates are known.
minEdgeBpsnumber–Default 100 (1%).

No output schema declared.

No examples provided.

clarification-impact ~395

Prediction-Market Clarification Impact Pricer — Prices a prediction-market rules clarification as a trade. Given an open Polymarket market (slug, URL or conditionId; Kalshi ticker supported), reads the posted clarification (Additional context) from the UMA adapter on Polygon, or takes your clarificationText to price a pending or hypothetical one. Finds the real-world outcomes whose resolution changed, quotes each changed clause verbatim, shifts

NameTypeReqDescription
bankrollUsdnumber–Used to turn the Kelly fraction into dollars.
clarificationTextstring–The clarification / Additional context text. Overrides the on-chain read.
feeRatenumber–Taker fee coefficient: fee = shares * feeRate * p * (1 - p). Defaults to the market's Gamma feeSchedule rate (0 when fees are disabled); Kalshi defaults to 0.07 times the series fee_multiplier from /…
kellyFractionnumber–Fraction of full Kelly to stake (default 0.25).
marketstringyesPolymarket market slug, polymarket.com URL or conditionId; or a Kalshi market ticker (rules from the public trade-api v2).
minEdgeBpsnumber–Minimum edge after fees and slippage, in bps of cost (default 100).
minMoveBpsnumber–Fair-value move below which the answer is NO_MATERIAL_CHANGE (default 100).
positionobject––
priorYesnumber–Override for the pre-clarification fair P(YES); default is the Polymarket CLOB price history just before the clarification, falling back to the current YES order-book mid.
rulesBeforestring–Rules text before the change. Overrides the on-chain read; defaults to the creation-time rules plus earlier updates.
sizeUsdnumber–Intended order size in USD (default 100).

No output schema declared.

No examples provided.

contract-auditor ~250

Smart Contract Auditor — Source-level security review of Solidity: pass/warn/fail verdict, 0-100 risk score, severity-ranked findings with exact file:line, exploit scenario and a fix, plus a SARIF 2.1.0 log. Accepts raw code, a list of files, or an on-chain address (verified source is read from Sourcify). A deterministic detector pass (reentrancy ordering, tx.origin, delegatecall, unchecked calls, weak randomness, pre-0.8

NameTypeReqDescription
addressstring–Alternative to code: an on-chain contract address. Its verified source is read from Sourcify (no API key); unverified contracts return 404.
chainIdinteger–EVM chain id for address; default 1 (Ethereum mainnet).
codestring–Raw Solidity source (one or more files concatenated). Provide exactly one of code, files or address.
contractNamestring–Contract to focus on when several are present.
filesarray–Alternative to code: Solidity files with repository-relative paths. Findings report the file and line, and the SARIF log points at them.

No output schema declared.

No examples provided.

cover-claim ~276

DeFi Cover Claim Adjudicator — Predicts whether a DeFi cover claim (Nexus Mutual or any provider's wording) will be approved and for how much. Reads the wording, postmortems and the claimant's transactions, quantifies net token loss with Chainlink prices at the loss block, maps facts to covered events, exclusions and conditions with verbatim verified clauses, cites similar past claims, and returns verdict.action (FILE / FILE_WI

NameTypeReqDescription
claimDatestring–ISO 8601 date the claim is (to be) filed; default now.
claimantstringyesAddress that suffered the loss (the Impacted Account).
claimedLossobject–Loss the claimant asserts, in cover-asset units. Used for the payout only when no on-chain loss can be established; always reported as unverified.
coverobjectyes–
deductibleobject–Overrides any deductible found in the wording. Amount in cover-asset units; percentages 0-100.
incidentobject––
transactionsarray–Transactions in which the claimant lost (or deposited, or recovered) funds.
wordingobjectyesThe cover wording: a Nexus Mutual product (id or name), a URL (HTML or PDF), or pasted text. At least one.

No output schema declared.

No examples provided.

dispute-ev ~196

UMA Dispute EV Desk — For a Polymarket market inside its roughly two-hour UMA challenge window, reads the live proposal on Polygon (adapter, optimistic oracle, bond, finalFee, expiry), judges P(proposal wrong or too early) against the literal rules with an ensemble plus red-team pass and verified quotes (full-game sports markets are decided by code with no model when Gamma's timestamps show the answer came before the g

NameTypeReqDescription
evidenceUrlsarray–Public pages to treat as evidence.
marketstringyesPolymarket slug, market/event URL, conditionId or questionID.
paramsobject––
positionobject–Your holding in this market.
pricesobject–Current prices of the first and second listed outcomes, USD per share.
proposalobject–Overrides for on-chain proposal fields (what-if or replay). Omit to read the live proposal.

No output schema declared.

No examples provided.

market-predictor ~376

Prediction Market Analyzer — Independent probability that a Polymarket or Kalshi market resolves Yes, checked against the live book. Pass a market (slug, URL, conditionId or Kalshi ticker) and/or news text: the agent reads the rules, end date and best asks, estimates 0-100 with live web search (falling back to model knowledge if search is slow), and returns verdict.action BUY_YES / BUY_NO / NO_TRADE with edge in bps after tak

NameTypeReqDescription
bankrollUsdnumber–Converts the quarter-Kelly fraction into verdict.size_usd.
marketstring–Polymarket slug, market URL or conditionId, or a Kalshi ticker or URL. Reads the question, rules, end date and live best asks; marketPriceYes then defaults to the book mid. A resolved market returns…
marketPriceScalestring–Force the unit of marketPriceYes: percent (35 = 35%) or fraction (0.35 = 35%).
marketPriceYesnumber–Current implied Yes probability, used to compute edge. Percent (0-100) by default; a value strictly between 0 and 1 is read as a 0-1 market price (Polymarket/Kalshi style) unless marketPriceScale say…
minEdgePctnumber–Minimum edge after taker fees, in percentage points, before verdict.action is BUY_YES or BUY_NO (default 5). A low-confidence estimate never produces a BUY.
questionstring–Exact market question; inferred when omitted (read from the market when market is given).
textstring–News excerpt or event description. Required unless market is given; with market, extra evidence you want weighed.

No output schema declared.

No examples provided.

milestone-verifier ~139

Grant Milestone Verifier with Signed Release Attestation — Decides whether a grantee met a milestone before a DAO releases the next tranche or stream. Checks GitHub as of the due date (commits, tags, releases, CI, files), npm/PyPI/crates.io publish times, Snapshot proposal state, on-chain deployments (bytecode selector scan through proxies, Sourcify, creation transaction), and URLs; judges the rest with an ensemble plus a skeptical reviewer, reads Sablier

NameTypeReqDescription
evidenceobjectyes–
milestoneobjectyes–
payoutobject––
releasePolicyobject––

No output schema declared.

No examples provided.

screen-tokens ~85

Batch Token Trap Screen — Runs the on-chain bytecode honeypot / rug screen on up to 10 Base tokens in one paid call, at 40% less than 10 single calls. Tokens the screen rejects as invalid input are reported per token; a chain or upstream outage fails the whole call so the payment is not settled.

NameTypeReqDescription
tokenAddressesarrayyes–

No output schema declared.

No examples provided.

token-due-diligence ~164

Token Due Diligence Pack — Honeypot / rug screening from live Base bytecode plus a Solidity audit of the token's verified source. Source is fetched from Sourcify (following EIP-1967/zeppelinos proxies to the implementation) when not supplied; unverified tokens are refused before any charge. Runs token-trap-detector ($0.25) + contract-auditor ($1.00) in one paid call for 20% less than buying them separately. Charged only whe

NameTypeReqDescription
contractNamestring–Contract to focus on when several are present.
sourceCodestring–Solidity source; fetched from Sourcify when omitted.
tokenAddressstringyesToken contract address on Base.

No output schema declared.

No examples provided.

token-trap-detector ~159

On-Chain Bytecode & Unverified Token Trap Detector — Reads live Base bytecode, proxy slots (EIP-1967/beacon/zeppelinos/EIP-1822/EIP-1167), ERC-20 state, and privileged selectors to score honeypot and rug risk in code: SAFE | CAUTION | HONEYPOT_RUG | INSUFFICIENT_EVIDENCE. Adds honeypot.is buy/sell simulation and GoPlus tax and honeypot flags, disclosed per source, and degrades to a lower-confidence bytecode-only score when they fail.

NameTypeReqDescription
sourceCodestring–Optional Solidity source claimed for the token.
tokenAddressstringyesToken contract address on Base.

No output schema declared.

No examples provided.

token-vault-ladder ~223

Token and Vault Exit Ladder — One decision on holding a Base token and a vault position: token-trap-detector (live bytecode, proxy slots, honeypot simulation) and vault-exit-lawyer (redeem limits, queue, admin powers, eth_call simulation) run in parallel; contract-auditor then audits the token's verified source at the proxy implementation the trap step read, and is skipped on a honeypot or unverified source. Returns the worst

NameTypeReqDescription
chainstringyesChain the vault lives on.
docsUrlsarray–Public documentation pages whose redemption claims are checked against the contract.
exitobjectyesExactly one of shares or assets, as base-unit integer strings. shares may be "max" (needs holder).
holderstring–Address that holds the shares. Enables an exact eth_call redeem simulation and per-holder limits.
tokenAddressstringyesToken contract address on Base.
vaultstringyesERC-4626 or ERC-7540 vault address.

No output schema declared.

No examples provided.

vault-exit-lawyer ~214

Vault Exit Lawyer — Before moving treasury funds out of an ERC-4626 or ERC-7540 vault: reads the chain at one pinned block and returns how much can exit now, the haircut vs convertToAssets, partial-exit maximum, liquidity coverage, queue/cooldown timing, admin-power flags (upgrade, pause, multisig threshold, timelock), and a verdict EXIT_NOW_FULL / EXIT_PARTIAL / QUEUED / BLOCKED / UNKNOWN. With a holder it simulates

NameTypeReqDescription
chainstringyesChain the vault lives on.
docsUrlsarray–Public documentation pages whose redemption claims are checked against the contract.
exitobjectyesExactly one of shares or assets, as base-unit integer strings. shares may be "max" (needs holder).
holderstring–Address that holds the shares. Enables an exact eth_call redeem simulation and per-holder limits.
vaultstringyesERC-4626 or ERC-7540 vault address.

No output schema declared.

No examples provided.

Install

How do I install the WritersLogic crypto agents MCP server?

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

What is the WritersLogic crypto agents MCP server?

WritersLogic crypto agents is an MCP server listed in the public MCP registry as com.writerslogic.agents/writerslogic-crypto. Smart-contract audit, token due diligence, prediction-market EV, vault exit analysis. This page covers its hosted endpoint (https://agents.writerslogic.com/mcp/crypto).

Is the WritersLogic crypto agents MCP server safe to use?

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

WritersLogic crypto agents exposes 12 tools: contract-auditor, market-predictor, arbitrage-lawyer, token-trap-detector, clarification-impact, and 7 more. Their descriptions and schemas cost roughly 2,698 tokens of context every time the server is loaded.

Does the WritersLogic crypto agents MCP server require authentication?

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

Is the WritersLogic crypto agents MCP server still maintained?

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

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