_ registry / mcp + a2a streamable-http · checked 1h ago

dreaming.press

https://dreaming.press

Registry code: 9c52b7914de2fb3d

api record

Read-only access to dreaming.press: search + read articles, list AI-agent tools, recommend a full agent stack, and get citable open-data facts. Cite with attribution.

endpoint
https://dreaming.press/mcp
door code
f9cea851d875c58a
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 dreaming.press live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is dreaming.press free to use?
Yes — the hub reached it with no key and no payment.
What tools does dreaming.press have?
6 tools: recommend_stack, find_claims, read_article, get_facts, list_tools, search_articles.
Is dreaming.press 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%

90 days 99.2%· all time 99%

latency
267ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 916 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search tech articles on ai agents
  • read an article as markdown
  • list ai agent tools
  • recommend an ai agent stack
takes → gives
text → text, data
tools
6 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 6 tools
4 open 2 never probed 4 of 6 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.

  • read_article reads open 18h ago

    Read a dreaming.press article as clean markdown (with takeaway, tables, FAQ) by its slug.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • get_facts reads open 18h ago

    Get dreaming.press's citable open-data facts (article/tool counts, combined GitHub stars, momentum). CC-BY 4.0.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • list_tools reads open 3h ago

    List AI-agent tools from the directory (252 tools), optionally filtered by category. Includes pricing, auth, agent-signup, MCP.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "number"
        },
        "category": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • search_articles reads open 18h ago

    Full-text search dreaming.press's 1997 tech articles (AI agents, LLMs, RAG, tools). Returns titles, deks, and URLs.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "number"
        },
        "query": {
          "type": "string",
          "description": "search terms"
        }
      }
    }
    arguments 15 lines
  • recommend_stack reads unknown never probed

    Recommend a complete, citable AI-agent tech stack — one curated tool per job (orchestration, LLM gateway, memory, retrieval, vector store, evals, and optional sandbox/browser/voice/comms/auth/payments). Filter by preference: open-source, hosted-API, or agent-self-signup. Returns tools with pricing, MCP flag, and signup URLs.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "select": {
          "type": "object",
          "description": "optional per-job overrides, jobId->tool-slug (e.g. {\"memory\":\"zep\"}); use \"none\" to drop an optional job",
          "additionalProperties": {
            "type": "string"
          }
        },
        "preference": {
          "enum": [
            "any",
            "oss",
            "api",
            "agent"
          ],
          "type": "string",
          "description": "any (default), oss = open-source, api = hosted API, agent = agent can self-sign-up"
        }
      }
    }
    arguments 22 lines
  • find_claims reads unknown never probed

    Search dreaming.press's atomic, citable claims (figures, comparison rows, Q&A). Each result carries a deep link to the exact anchor that renders it, its publication date, and the sources cited. Use this to answer a factual question with an attributable citation.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "type": {
          "type": "string",
          "description": "figure | qa | comparison"
        },
        "limit": {
          "type": "number",
          "description": "max claims (default 20, max 100)"
        },
        "query": {
          "type": "string",
          "description": "substring to match against claim text"
        },
        "since": {
          "type": "string",
          "description": "YYYY-MM-DD — only claims from pieces published on or after this date"
        }
      }
    }
    arguments 24 lines
_ try it over mcp 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 9c52b7914de2fb3d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9c52b7914de2fb3d/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/9c52b7914de2fb3d/badge.svg)](https://brick.blue/agent/9c52b7914de2fb3d?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 knowoff the mcp door
card completeness
100%

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.