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

upstream

https://upstream.toolweather.workers.dev

Registry code: 3230ffe226ba15b0

api record

Free: 500 calls/day with a free key (POST /v1/keys, send as X-API-Key) or 50/day without one. Over quota, paid tools return an x402 payment requirement; retry with params._meta["x402/payment"] set to the signed payment payload.

endpoint
https://upstream.toolweather.workers.dev/mcp
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 upstream live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is upstream free to use?
Yes — the hub reached it with no key and no payment.
What tools does upstream have?
5 tools: get_status, get_model, get_digest, get_changes, list_providers.
Is upstream 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 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
3 open 2 never probed 3 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.

  • get_digest open 2h ago

    Daily breaking-changes digest (free): AI/dev API incidents, model deprecations/retirements, pricing-page changes, breaking MCP server changes. Optional date YYYY-MM-DD, default latest.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "date": {
      "type": "string",
      "description": "YYYY-MM-DD; omit for the latest issue"
    }
  }
}
    arguments 9 lines
  • get_changes open 2h ago

    What changed: status transitions, deprecation-page edits, model retirements, pricing-page edits. Free within the daily quota, then $0.01 via x402.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "kind": {
      "enum": [
        "status",
        "deprecations",
        "model_retirement",
        "pricing"
      ],
      "type": "string"
    },
    "limit": {
      "type": "number"
    },
    "since": {
      "type": "string",
      "description": "ISO timestamp, default 7 days ago"
    },
    "provider": {
      "type": "string"
    }
  }
}
    arguments 24 lines
  • list_providers open 2h ago

    List the ~40 AI and developer API providers Upstream tracks, with their current state. Free.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_status unknown never probed

    Is this provider's API up right now? Current state, open incidents, affected components. Free within the daily quota, then $0.003 via x402.

    mcp-tool

    {
  "type": "object",
  "required": [
    "provider"
  ],
  "properties": {
    "provider": {
      "type": "string",
      "description": "provider id from list_providers, e.g. openai, anthropic, github, stripe"
    }
  }
}
    arguments 12 lines
  • get_model unknown never probed

    Is this model id active, deprecated or retired? Shutdown date and replacement, from the provider's own deprecation page ("unknown" if not explicitly listed). Free within the daily quota, then $0.003 via x402.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "model id, e.g. gpt-4o, claude-3-opus-20240229, gemini-1.5-pro"
    }
  }
}
    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 3230ffe226ba15b0.

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