_ registry / mcp streamable-http · checked 19m ago

fundz-agent-api

https://api.fundz.net

Registry code: 0627c2f76dc9d812

api record

Fundz Agent API: dated funding and SEC 8-K event evidence, each item linking to the filing or announcement it came from. Two lanes only — funding (SEC Form D and announcements) and SEC 8-K; there is no contact or people data. Every evidence item carries a `source_kind` (sec_filing or press_or_news) and a `source_url`; cite it. Calls are metered against the caller's key: why_now, events_for_icp and predicted_next cost 1 unit each, and watchlist_diff costs 0.1 per company CHECKED — so poll a book with watchlist_diff and a cursor rather than calling why_now across it. predicted_next is…

endpoint
https://api.fundz.net/v1/agent/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 fundz-agent-api live?
Yes — it answered the hub's last check (checked 19m ago). It answered 98% of checks over the last 30 days.
Is fundz-agent-api free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does fundz-agent-api have?
4 tools: watchlist_diff, events_for_icp, why_now, predicted_next.
Is fundz-agent-api 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
97.6%

90 days 98.4%· all time 98.4%

latency
817ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 386 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • find companies with recent funding
  • get sec 8-k events for a company
  • watch a company list for new events
  • forecast a company's next move
takes → gives
text, data → data
tools
4 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 4 tools
4 auth-required 4 of 4 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.

  • watchlist_diff reads auth-required 14h ago

    Given a book of up to 400 company domains and a cursor, return ONLY those with new evidence since that cursor. This is the tool to poll daily or weekly rather than re-fetching every company. Costs 0.1 units per company CHECKED — not per company returned — so a quiet week still reflects the work done. Split a larger book across several calls: the request body is capped at 8 KB at the edge, and because pricing is per company checked, two calls of 200 cost exactly what one call of 400 would.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domains"
      ],
      "properties": {
        "since": {
          "type": "string",
          "format": "date",
          "description": "The `next_cursor` from your previous call."
        },
        "domains": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 400
        }
      }
    }
    arguments 20 lines
  • events_for_icp reads auth-required 6h ago

    Find companies matching an ideal-customer profile that have had recent funding or SEC 8-K events, ranked, each with its evidence. Use this to build a list from scratch. `min_signals` filters for companies with several signals at once. Costs 1 unit.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 25,
          "maximum": 100,
          "description": "Rows per call. Hard-capped at 100 server-side; values above are clamped, not refused. Page with `cursor` for more."
        },
        "cursor": {
          "type": "string"
        },
        "states": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Full state names as stored, e.g. 'California'."
        },
        "industries": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "min_signals": {
          "type": "integer",
          "default": 1
        },
        "lookback_days": {
          "type": "integer",
          "default": 90
        },
        "max_employees": {
          "type": "integer"
        },
        "min_employees": {
          "type": "integer"
        }
      }
    }
    arguments 41 lines
  • why_now reads auth-required 6h ago

    Why to contact ONE company right now: dated funding and SEC 8-K evidence, each item linking to its source filing or announcement. Use this when you have a company and need the reason and the proof. Costs 1 unit. `evidence` covers the last `lookback_days` days (default 365, max 1825); `last_event` is ALWAYS the most recent event on record whatever its age, with `within_lookback` saying whether it also appears in `evidence`. So an empty `evidence` with a populated `last_event` means the company is known and simply quiet — widen `lookback_days` to bring it in. `resolved:false` means we hold no such company at all, which is a different answer again. `resolution_confidence` (0-1) says how strongly the resolved name agrees with the domain asked about; treat anything below 0.67 as unconfirmed attribution.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "domain": {
          "type": "string",
          "description": "Any spelling: bare, www., scheme, path."
        },
        "org_id": {
          "type": "integer"
        },
        "lookback_days": {
          "type": "integer",
          "default": 365,
          "maximum": 1825,
          "minimum": 1,
          "description": "Window for `evidence[]`, in days. Clamped to 1825. Does not affect `last_event`, which is never age-limited."
        }
      }
    }
    arguments 19 lines
  • predicted_next reads auth-required 6h ago

    EXPERIMENTAL forecast of what a company may do next (raise, be acquired, acquire), from FundzScore v3. Treat `lift` as a ranking aid only: `base_rate` is a population mean rather than a validated historical rate, and the forward cohorts do not resolve until 2026-10-22 and 2027-02-19. Do not present these as predictions to an end user. Costs 1 unit.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "domain": {
          "type": "string"
        },
        "org_id": {
          "type": "integer"
        }
      }
    }
    arguments 11 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 0627c2f76dc9d812.

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

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.

_ also on fundz.net 2 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.