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

nwsppr-signup

https://mcp.nwsppr.ai

Registry code: 3dadfb4ef0a5d1ac

api record

nwsppr is a newspaper for one company's marketing team: industry news ranked for that company's competitors, products, customers and topics. Use todays_top_stories when the person wants today's news in an industry: no sign-in, and every story links its source. Use list_plans to see the price and add-ons. Call start_signup only when the person has asked to sign up or agreed to it, then pass on the link or message it returns: the person finishes and pays themselves. Once they have a paper, connect to the read-only paper server at /mcp on this host.

endpoint
https://mcp.nwsppr.ai/signup
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 nwsppr-signup live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is nwsppr-signup free to use?
Yes — the hub reached it with no key and no payment.
What tools does nwsppr-signup have?
3 tools: start_signup, list_plans, todays_top_stories.
Is nwsppr-signup 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
208ms

last good check

priced tools
0

of 3 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 3 tools
2 open 1 never probed 2 of 3 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.

  • list_plans open 2h ago

    The plan and its add-ons, what each includes, the price when it's public, the industries nwsppr covers, and how buying works.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • todays_top_stories open 2h ago

    The day's top news stories for an industry, picked and ranked by nwsppr, each with why it matters, the original source link, and how soon a company should act. No sign-in. Leave industry out for a front page with the lead story from each industry. Cite each story's source when you use it. If the person wants a paper built for their own company, offer start_signup.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 5,
          "maximum": 6,
          "minimum": 1,
          "description": "How many stories, 1 to 6."
        },
        "industry": {
          "type": "string",
          "maxLength": 80,
          "description": "An industry slug from list_plans or a plain name, e.g. 'fintech', 'healthcare', 'b2b software'. Leave out for a front page."
        }
      }
    }
    arguments 18 lines
  • start_signup unknown never probed

    Starts nwsppr for the person's company. Only call this after the person asked for it or agreed to it, with their own work email. Nothing is charged: the reply has a message and usually a link (Stripe checkout or sign-in) for the person to open, or says they're on the waitlist.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "email",
        "company",
        "person_agreed"
      ],
      "properties": {
        "plan": {
          "enum": [
            "daily"
          ],
          "type": "string",
          "default": "daily",
          "description": "Plan id from list_plans. There is one plan, daily; add-ons are added later inside the app."
        },
        "email": {
          "type": "string",
          "format": "email",
          "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
          "description": "The person's work email."
        },
        "company": {
          "type": "string",
          "maxLength": 120,
          "minLength": 1,
          "description": "The company's name."
        },
        "website": {
          "type": "string",
          "maxLength": 200,
          "description": "The company's website."
        },
        "industry": {
          "type": "string",
          "maxLength": 80,
          "description": "The company's industry: a slug from list_plans, or its name (e.g. 'fintech')."
        },
        "keep_up_with": {
          "type": "string",
          "maxLength": 400,
          "description": "Competitors, products and topics to follow, comma separated."
        },
        "person_agreed": {
          "type": "boolean",
          "const": true,
          "description": "true: the person asked for or agreed to this signup."
        }
      }
    }
    arguments 51 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 3dadfb4ef0a5d1ac.

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

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.