Skip to content

Fundz Agent API MCP server

net.fundz/agent-apifundz.netstreamable-httpv1.0.0Scanned

Dated funding and SEC 8-K events, each linked to the filing it came from.

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Fundz Agent API MCP server can do

The Fundz Agent API MCP server is published by fundz.net, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: predicted_next and why_now), but cannot delete data. 2 tools only read.

4 tools bring in text other people can write (events_for_icp, predicted_next, watchlist_diff and 1 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 2Claude Code: ask
  • predicted_nextEXPERIMENTAL forecast of what a company may do next (raise, be acquired, acquire), from FundzScore v3.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: FundzScore v3 forecasts (experimental)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • why_nowWhy to contact ONE company right now: dated funding and SEC 8-K evidence, each item linking to its source filing or announcement.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Dated evidence for one company
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • events_for_icpFind companies matching an ideal-customer profile that have had recent funding or SEC 8-K events, ranked, each with its evidence.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Ranked companies matching an ICP, each with evidence
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • watchlist_diffGiven a book of up to 400 company domains and a cursor, return ONLY those with new evidence since that cursor.Reads text others writeNo findings

    Why it is in this group

    • The name "watchlist_diff" says "diff": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Only the companies in your book with new events since a cursor
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:16 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.fundz.net/v1/agent/mcp: tools/list returned 4 tools to an anonymous client, including predicted_next (write), why_now (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http agent-api https://api.fundz.net/v1/agent/mcp --header 'X-Fundz-Key: <your-x-fundz-key>'
claude mcp add --transport http agent-api https://api.fundz.net/v1/agent/mcp --header 'X-Fundz-Key: <your-x-fundz-key>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__agent-api__events_for_icp",
      "mcp__agent-api__watchlist_diff"
    ],
    "ask": [
      "mcp__agent-api__predicted_next",
      "mcp__agent-api__why_now"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agent-api. Review it before you use it.

Capability tags behind 4 rules
  • mcp__agent-api__events_for_icp untrusted-input
  • mcp__agent-api__predicted_next untrusted-input
  • mcp__agent-api__watchlist_diff untrusted-input
  • mcp__agent-api__why_now untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/net.fundz/agent-api/verify?hash=86b6a5000d7fe8d9e59a581b147d3ba99a519594b403fbc621b7bbbb15d73468" | jq -e '.changed == false'

Pinned hash 86b6a5000d7f, from Nov 18, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/net.fundz/agent-api/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for net.fundz/agent-api
[![Anlyon Radar](https://radar.anlyon.com/badge/net.fundz/agent-api.svg)](https://radar.anlyon.com/servers/net.fundz/agent-api)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:53 UTC.

Fundz Agent API MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Fundz Agent API MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Fundz Agent API MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Fundz Agent API MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Fundz Agent API MCP server have?

4 tools: 2 write, 2 read. predicted_next, why_now, events_for_icp and watchlist_diff.

Does the Fundz Agent API MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Fundz Agent API MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Fundz Agent API MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.