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.

Cryptowisser News

REMOTE · WWW.CRYPTOWISSER.COM

Latest crypto news, stories and articles from Cryptowisser, with news cards linking to full stories.

+3 this week 85 Trust /100

Last scanned (23 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 4 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 Security74
Transport & Reachability100
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1038 tokens (~173/item across 6 items; 5 tools + 1 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 Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
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.

  • 3 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 30 Oct 26 +1

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

  • 28 Oct 26 +1

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

  • 25 Oct 26 +1

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

  • 23 Oct 26 +1

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

  • 21 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 19 Oct 26 +1

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

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 4 Nov 2026 · Probed https://www.cryptowisser.com/mcp/server

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cryptowisser.com CN=WE1,O=Google Trust Services,C=US 18 Oct 2026 16 Jan 2027 ECDSA 256 ECDSA-SHA256 275bb8a6dd9f6c1c13a1f311efe2e7a6
SANs: cryptowisser.com, *.cryptowisser.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 insecure

Validation of www.cryptowisser.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
cryptowisser.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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
x-content-type-options nosniff
x-frame-options SAMEORIGIN

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.cryptowisser.com/mcp/server Verified 200
http (plaintext) http://www.cryptowisser.com/mcp/server HTTPS enforced 301 https://www.cryptowisser.com/mcp/server/
MCP tools · 5 exposed · ~837 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
get-article ~67

Get one Cryptowisser news article in full by its URL or slug: headline, full text, summary, author, date, topics, tags and link. Suited to questions about a specific Cryptowisser article or link.

NameTypeReqDescription
articlestringyesThe article URL or slug.

No output schema declared.

No examples provided.

latest-news ~257

Get the latest crypto news from Cryptowisser. Use this for general questions like "What's the latest crypto news?", "What happened in crypto today?" or "Any crypto news?". By default the stories our editors feature on the front page come first, followed by the newest articles; set by_date to true for strictly newest first. Use from/to for a specific period, e.g. "news from last week". Returns 5 articles by default. Each article has a headline, short summary, date, age and a link to the full story on cryptowisser.com.

NameTypeReqDescription
by_dateboolean–Optional. True to order strictly by publication date, newest first, instead of featured stories first.
categorystring–Optional news category slug to filter by. Leave empty for all news.
fromstring–Optional. Only articles published on or after this date or datetime (ISO 8601, e.g. "2026-09-28"). Leave empty for the newest articles.
limitinteger–Number of articles to return, 1 to 20. Defaults to 5.
tostring–Optional. Only articles published on or before this date or datetime. Defaults to now.

No output schema declared.

No examples provided.

news-about ~181

Get recent Cryptowisser news about a specific coin, token, company, exchange, person, regulator, law, country or story, for example "Bitcoin", "Binance", "CZ", "SEC" or "Bitget hack". Names, tickers and common aliases are recognised. Use from/to for a specific period.

NameTypeReqDescription
entitystringyesThe coin, company, person or story, e.g. "Solana", "Coinbase", "Vitalik Buterin", "Bitget hack".
fromstring–Optional. Only articles published on or after this date or datetime (ISO 8601).
limitinteger–Number of articles to return, 1 to 20. Defaults to 5.
tostring–Optional. Only articles published on or before this date or datetime. Defaults to now.

No output schema declared.

No examples provided.

search-news ~268

Search Cryptowisser news by keywords. How matching works: - If the whole query is a known coin, company, person, regulator or country (names, tickers and aliases like "ETH" or "CZ" work), you get articles tagged with that entity. - Otherwise an article matches only if EVERY keyword appears in its headline or summary. Matching is case-insensitive and on partial words ("ETF" also matches "ETFs"). There are no synonyms and no relevance ranking. - Queries of 1 to 3 distinctive keywords work best: "bitcoin price" matches articles, while a full question like "why is bitcoin down" usually matches nothing. Every extra keyword narrows the results. - Results are newest first, and from/to limit them to a specific period.

NameTypeReqDescription
fromstring–Optional. Only articles published on or after this date or datetime (ISO 8601, e.g. "2026-09-01").
limitinteger–Number of articles to return, 1 to 20. Defaults to 5.
querystringyes1 to 3 distinctive keywords, or a coin, company or person name.
tostring–Optional. Only articles published on or before this date or datetime. Defaults to now.

No output schema declared.

No examples provided.

trending-stories ~64

Get the biggest ongoing crypto stories of the past week, as covered by Cryptowisser, each with its latest articles. Suited to questions about the big or developing stories in crypto.

NameTypeReqDescription
limitinteger–Number of stories to return, 1 to 10.

No output schema declared.

No examples provided.

Install

How do I install the Cryptowisser News MCP server?

Cryptowisser News is a hosted endpoint at https://www.cryptowisser.com/mcp/server, 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 · www.cryptowisser.com

# add to Claude Code
claude mcp add --transport http com-cryptowisser-news 'https://www.cryptowisser.com/mcp/server'
Common questions

What is the Cryptowisser News MCP server?

Cryptowisser News is an MCP server listed in the public MCP registry as com.cryptowisser/news. Latest crypto news, stories and articles from Cryptowisser, with news cards linking to full stories. This page covers its hosted endpoint (https://www.cryptowisser.com/mcp/server).

Is the Cryptowisser News MCP server safe to use?

Cryptowisser News scores 85 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 Cryptowisser News MCP server expose?

Cryptowisser News exposes 5 tools: latest-news, news-about, trending-stories, search-news, get-article. Their descriptions and schemas cost roughly 837 tokens of context every time the server is loaded.

Does the Cryptowisser News MCP server require authentication?

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

Is the Cryptowisser News MCP server still maintained?

Cryptowisser News is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.