_ registry / mcp http-sse · checked 2h ago

newswake

https://newswake-ajq8t.ondigitalocean.app

Registry code: f49cd03c10ac0510

api record

News momentum + what-changed outcome tools for agents. Signals + links, ~296 sources.

from a public catalogue that lists it, not from the operator

endpoint
https://newswake-ajq8t.ondigitalocean.app/mcp
protocol
http-sse ·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 newswake live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is newswake free to use?
Yes — the hub reached it with no key and no payment.
What tools does newswake have?
2 tools: whats_changed, find_trending.
Is newswake 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
99.5%

90 days 99.4%· all time 99.4%

latency
415ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 331 checks · signed record
  • degraded → live
  • live → degraded· HTTP 521
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
search & web news
used for
  • find trending news stories
  • see what changed in coverage of an entity
takes → gives
text → data
tools
2 reads
_ 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 2 tools
1 open 1 never probed 1 of 2 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.

  • find_trending reads open 16h ago

    What news is ACCELERATING right now — a ranked list of story-events climbing in attention, optionally scoped to a beat/topic. Each returns trend, momentum, acceleration, outlet count, a runway hint (act now vs window closing), why-now, and a link. Use to decide what to ride/publish/watch. ~2h behind live, ~296 mainstream sources, signals + links only.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 15,
      "minimum": 1,
      "description": "Max results (default 8)."
    },
    "topic": {
      "type": "string",
      "description": "Beat or keyword to scope to, e.g. \"technology\", \"crypto\", \"nvidia\". Omit for all beats."
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • whats_changed reads unknown never probed

    The DELTA on an entity — what is new or has shifted in news coverage of a company/person/topic since a given time. Returns new vs updated story-events, trend, importance, and links. This is the stateful "what changed since my last check" that stateless search tools cannot answer. ~296 mainstream sources, signals + links only.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "entity"
  ],
  "properties": {
    "since": {
      "type": "string",
      "description": "ISO timestamp of your last check. Default: 7 days ago."
    },
    "entity": {
      "type": "string",
      "description": "Company, person, or topic, e.g. \"Nvidia\", \"OpenAI\", \"Donald Trump\"."
    }
  },
  "additionalProperties": false
}
    arguments 18 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 f49cd03c10ac0510.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f49cd03c10ac0510/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/f49cd03c10ac0510/badge.svg)](https://brick.blue/agent/f49cd03c10ac0510?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
60%

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.