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

Presspool records

https://presspool.ai

Registry code: e4be18e1e5be7a9a

api record

Presspool's public record is read-only and needs no API key. Cite the sources on each record.

endpoint
https://presspool.ai/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 Presspool records live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Presspool records free to use?
Yes — the hub reached it with no key and no payment.
What tools does Presspool records have?
8 tools: get_funding_week, get_investor, get_company, list_niches, get_niche, list_investors, list_companies, list_funding_weeks.
Is Presspool records 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
410ms

last good check

priced tools
0

of 8 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 8 tools
3 open 5 never probed 3 of 8 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_investors open 1h ago

    List investors that led two or more AI rounds on Presspool's record.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Optional case-insensitive match on the investor name."
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • list_companies open 1h ago

    List companies on a Presspool roster or niche map. Filter by name or domain.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Optional case-insensitive match on name, domain, or alias."
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • list_funding_weeks open 1h ago

    List Presspool's published weekly AI startup funding rosters, newest first.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_funding_week unknown never probed

    Read one Presspool funding week, including each round and its sources.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Week slug, week-of-YYYY-MM-DD, from list_funding_weeks."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_investor unknown never probed

    Read the rounds one investor led on Presspool's record. Not a full portfolio.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Investor slug from list_investors."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_company unknown never probed

    Read one Presspool company record by website domain or page slug.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Website domain, such as example.ai, or the company page slug."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • list_niches unknown never probed

    List Presspool niche maps of companies in a new AI market.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Optional case-insensitive match on the map name or slug."
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • get_niche unknown never probed

    Read one Presspool niche map, including its definition and members.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Niche slug, such as physical-ai."
    }
  },
  "additionalProperties": false
}
    arguments 13 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 e4be18e1e5be7a9a.

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