mcpbeat Sign in

nwsppr MCP Server

answering

nwsppr is answering right now. Last checked 13 min ago.

Your company's own morning paper: the industry news that matters to you, ranked, with sources.

Uptime history 36 hours of history
36 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
186 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check nwsppr every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add paper --transport http https://mcp.nwsppr.ai/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.nwsppr.ai/mcp
~/.codex/config.toml
[mcp_servers.paper]
url = "https://mcp.nwsppr.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "paper": {
      "url": "https://mcp.nwsppr.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "paper": {
      "type": "http",
      "url": "https://mcp.nwsppr.ai/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.nwsppr.ai/mcp streamable-http sign-in 218 ms 13 min ago

Alternatives to nwsppr

same job, measured the same way
nwsppr: today's top stories
by nwsppr

Free, no sign-in: today's most important industry news, ranked, with sources and why each matters.

3 tools answering
In Parallel
by in-parallel

The context layer for your company's AI: your team's decisions, meetings and plans, with sources.

answering
MemoryBrain
by memorybrain

Your own memory inside ChatGPT and Claude, with the source of every note.

answering
Syracuse Company News
by 1145-am

Structured company & industry news for AI agents: typed, dated, source-linked events.

4 tools answering
Briefings
by jshelley

Hourly ranked news (AI, markets, sports, world): JSON, e-ink pages, Morning Paper PDF; 25 free/day

3 tools answering
Testfinder
by cloudcorprecords

Find the tests relevant to a source file from an import map, ranked, with the run command.

289 installs/wk local only
UGT: Use the GitHub Thing
by usegithubthing

Get open-source GitHub projects running on your computer, with your AI app

5 tools answering
CNC Compass
by cnccompass

Search reviewed Chinese CNC machining suppliers, with each fact linked to its source page.

3 tools answering

nwsppr — questions

Answers built from our own checks of this server.

Why is there no tool list for nwsppr?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is nwsppr working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 186 ms. The bar chart above shows every period we have measured.
How do I connect nwsppr?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to nwsppr?
No API key is involved. nwsppr answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is nwsppr?
It answers our handshake in 186 ms on average, which is faster than 73% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.