_ registry / mcp streamable-http · checked 59m ago

Cryptowisser News

https://www.cryptowisser.com

Registry code: 75c75aadc2e378a6

api record

Cryptowisser is an independent crypto news publication. This server gives access to its published news: the latest articles, news about specific coins, companies and people, the biggest ongoing stories, and keyword search.

Article lists contain a headline, a short summary, the publication date, how long ago it was published and a link. Use get-article to read one article in full. When you use an article, attribute it to Cryptowisser and include its link.

endpoint
https://www.cryptowisser.com/mcp/server
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Cryptowisser News live?
Yes — it answered the hub's last check (checked 59m ago). It answered 100% of checks over the last 30 days.
Is Cryptowisser News free to use?
Yes — the hub reached it with no key and no payment.
What tools does Cryptowisser News have?
5 tools: news-about, search-news, get-article, latest-news, trending-stories.
Is Cryptowisser News safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
239ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
2 open 3 never probed 2 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • latest-news open 59m ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "to": {
      "type": "string",
      "description": "Optional. Only articles published on or before this date or datetime. Defaults to now."
    },
    "from": {
      "type": "string",
      "description": "Optional. Only articles published on or after this date or datetime (ISO 8601, e.g. \"2026-09-28\"). Leave empty for the newest articles."
    },
    "limit": {
      "type": "integer",
      "default": 5,
      "description": "Number of articles to return, 1 to 20. Defaults to 5."
    },
    "by_date": {
      "type": "boolean",
      "default": false,
      "description": "Optional. True to order strictly by publication date, newest first, instead of featured stories first."
    },
    "category": {
      "type": "string",
      "description": "Optional news category slug to filter by. Leave empty for all news."
    }
  }
}
    arguments 27 lines
  • trending-stories open 59m ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 5,
      "description": "Number of stories to return, 1 to 10."
    }
  }
}
    arguments 10 lines
  • news-about unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "entity"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "Optional. Only articles published on or before this date or datetime. Defaults to now."
    },
    "from": {
      "type": "string",
      "description": "Optional. Only articles published on or after this date or datetime (ISO 8601)."
    },
    "limit": {
      "type": "integer",
      "default": 5,
      "description": "Number of articles to return, 1 to 20. Defaults to 5."
    },
    "entity": {
      "type": "string",
      "description": "The coin, company, person or story, e.g. \"Solana\", \"Coinbase\", \"Vitalik Buterin\", \"Bitget hack\"."
    }
  }
}
    arguments 25 lines
  • search-news unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "Optional. Only articles published on or before this date or datetime. Defaults to now."
    },
    "from": {
      "type": "string",
      "description": "Optional. Only articles published on or after this date or datetime (ISO 8601, e.g. \"2026-09-01\")."
    },
    "limit": {
      "type": "integer",
      "default": 5,
      "description": "Number of articles to return, 1 to 20. Defaults to 5."
    },
    "query": {
      "type": "string",
      "description": "1 to 3 distinctive keywords, or a coin, company or person name."
    }
  }
}
    arguments 25 lines
  • get-article unknown 59m ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "article"
  ],
  "properties": {
    "article": {
      "type": "string",
      "description": "The article URL or slug."
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 75c75aadc2e378a6.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/75c75aadc2e378a6/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/75c75aadc2e378a6/badge.svg)](https://brick.blue/agent/75c75aadc2e378a6?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.