Skip to content

WritersLogic crypto agents MCP server

com.writerslogic.agents/writerslogic-cryptoagents.writerslogic.comstreamable-httpv1.0.0Scanned

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

12 tools: 1 do something that can't be undone and 11 change things.

Tools: 0 delete, 1 irreversible, 11 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the WritersLogic crypto agents MCP server can do

The WritersLogic crypto agents MCP server is published by agents.writerslogic.com, a domain the MCP Registry verified. It has 12 tools. It can do things that cannot be undone, such as sending, paying or publishing (milestone-verifier) and create or change data (11 tools: contract-auditor, market-predictor, arbitrage-lawyer, token-trap-detector and 7 more), but cannot delete data. None of its tools only reads.

2 tools can send data out of your system (milestone-verifier and cover-claim).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Can't be undone 1Claude Code: ask
  • milestone-verifierGrant Milestone Verifier with Signed Release Attestation — Decides whether a grantee met a milestone before a DAO releases the next tranche or stream.Can send data outNo findings

    Why it is in this group

    • The input addresses people (input.payout.recipient): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.payout.recipient): what the tool writes goes there.
    • outboundThe input takes a URL (input.evidence.urls): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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
Changes things 11Claude Code: ask
  • arbitrage-lawyerCross-Platform Arbitrage & Resolution Rules Lawyer — Finds fine-print divergences between two prediction markets (e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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
  • clarification-impactPrediction-Market Clarification Impact Pricer — Prices a prediction-market rules clarification as a trade.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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
  • contract-auditorSmart 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 f…No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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
  • cover-claimDeFi Cover Claim Adjudicator — Predicts whether a DeFi cover claim (Nexus Mutual or any provider's wording) will be approved and for how much.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.wording.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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
  • dispute-evUMA 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, expi…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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
  • market-predictorPrediction Market Analyzer — Independent probability that a Polymarket or Kalshi market resolves Yes, checked against the live book.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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
  • screen-tokensBatch 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • token-due-diligenceToken Due Diligence Pack — Honeypot / rug screening from live Base bytecode plus a Solidity audit of the token's verified source.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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
  • token-trap-detectorOn-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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • token-vault-ladderToken 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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
  • vault-exit-lawyerVault 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 convert…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:23 UTC, unchanged since Nov 16, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
12
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 12 tools that change things (1 irreversible, 11 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://agents.writerslogic.com/mcp/crypto: tools/list returned 12 tools to an anonymous client, including milestone-verifier (irreversible), contract-auditor (write), market-predictor (write), arbitrage-lawyer (write), token-trap-detector (write) and 7 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http writerslogic-crypto https://agents.writerslogic.com/mcp/crypto
claude mcp add --transport http writerslogic-crypto https://agents.writerslogic.com/mcp/crypto

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__writerslogic-crypto__contract-auditor",
      "mcp__writerslogic-crypto__market-predictor",
      "mcp__writerslogic-crypto__arbitrage-lawyer",
      "mcp__writerslogic-crypto__token-trap-detector",
      "mcp__writerslogic-crypto__clarification-impact",
      "mcp__writerslogic-crypto__milestone-verifier",
      "mcp__writerslogic-crypto__dispute-ev",
      "mcp__writerslogic-crypto__cover-claim",
      "mcp__writerslogic-crypto__vault-exit-lawyer",
      "mcp__writerslogic-crypto__token-due-diligence",
      "mcp__writerslogic-crypto__screen-tokens",
      "mcp__writerslogic-crypto__token-vault-ladder"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as writerslogic-crypto. Review it before you use it.

Capability tags behind 2 rules
  • mcp__writerslogic-crypto__milestone-verifier outbound
  • mcp__writerslogic-crypto__cover-claim outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.writerslogic.agents/writerslogic-crypto/verify?hash=62f238a20ceb3ab4c41c852f6a80579cef42773e4162077f69536feccb788c3f" | jq -e '.changed == false'

Pinned hash 62f238a20ceb, from Nov 15, 2026, 18:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.writerslogic.agents/writerslogic-crypto/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.writerslogic.agents/writerslogic-crypto
[![Anlyon Radar](https://radar.anlyon.com/badge/com.writerslogic.agents/writerslogic-crypto.svg)](https://radar.anlyon.com/servers/com.writerslogic.agents/writerslogic-crypto)

Source: MCP Registry · repository. Synced Nov 15, 2026, 18:17 UTC.

WritersLogic crypto agents MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the WritersLogic crypto agents MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 12 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the WritersLogic crypto agents MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the WritersLogic crypto agents MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: milestone-verifier.

What tools does the WritersLogic crypto agents MCP server have?

12 tools: 1 irreversible, 11 write. milestone-verifier, contract-auditor, market-predictor, arbitrage-lawyer, token-trap-detector, clarification-impact, dispute-ev, cover-claim and 4 more.

Does the WritersLogic crypto agents MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the WritersLogic crypto agents MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): milestone-verifier and cover-claim.

Has the WritersLogic crypto agents MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.