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

techeu-funding-explorer

https://funding.tech.eu

Registry code: 7e71868485ddd82d

api record

Tech.eu Funding Explorer — European tech funding rounds, investors and exits. Read-only, source-linked, EUR-normalized at the ECB reference rate on each round date. Full dataset (the same tables the site renders), not a sample; no key or account. Typical flow: find_companies → get_company; or search_rounds with filters. Keeping a local copy in sync? Use list_changes, not repeated search_rounds paging. Free within per-IP fair-use limits; methodology at https://funding.tech.eu/methodology. Licence CC BY 4.0: when you show figures, cite "Tech.eu Funding Explorer" and link the page each came from…

endpoint
https://funding.tech.eu/api/mcp
protocol
http-sse ·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 techeu-funding-explorer live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is techeu-funding-explorer free to use?
Yes — the hub reached it with no key and no payment.
What tools does techeu-funding-explorer have?
8 tools: get_investor, list_changes, find_companies, get_company, market_map, search_exits, search_rounds, search_investors.
Is techeu-funding-explorer 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
98.6%

90 days 98.8%· all time 98.8%

latency
306ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 433 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
  • search european tech funding rounds
  • get a startup's funding history
  • look up an investor portfolio
  • search tech exits and acquisitions
takes → gives
text, data → data
tools
8 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 8 tools
4 open 4 never probed 4 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.

  • market_map reads open 15h ago

    Aggregate the European funding picture for a period in ONE call: totals (disclosed €, split into equity / debt / grant €, rounds, companies, investors, exits), concentration, and breakdowns by country, sector and stage — with provenance (disclosed %, high-confidence %, ECB reconciliation Δ). Beats paging every round to sum client-side. Defaults to the current year.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "period": {
          "type": "string",
          "description": "A year (\"2026\"), half-year (\"2026-h1\"), quarter (\"2026-q1\") or month (\"2026-01\"); defaults to the current year"
        }
      }
    }
    arguments 10 lines
  • search_exits reads open 15h ago

    European tech exits and M&A (acquisitions, IPOs), newest first with a nextCursor. Filter by date window and by the exited company's country (use it for "European exits"). Most deal values are undisclosed — valueEur is null in ~65% of exits.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "to": {
          "type": "string",
          "description": "Latest exit date, YYYY-MM-DD"
        },
        "from": {
          "type": "string",
          "description": "Earliest exit date, YYYY-MM-DD"
        },
        "after": {
          "type": "string",
          "description": "Opaque nextCursor from a previous call"
        },
        "limit": {
          "type": "number",
          "maximum": 100,
          "minimum": 1
        },
        "country": {
          "type": "string",
          "description": "Exited company country, e.g. \"UK\", \"Germany\", \"France\""
        }
      }
    }
    arguments 27 lines
  • search_rounds reads open 15h ago

    Search European tech funding rounds (cited, EUR-normalized at the ECB rate on the round date). Returns newest first with a `nextCursor` for pagination.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "to": {
          "type": "string",
          "description": "Latest round date, YYYY-MM-DD"
        },
        "from": {
          "type": "string",
          "description": "Earliest round date, YYYY-MM-DD"
        },
        "after": {
          "type": "string",
          "description": "Opaque nextCursor from a previous call"
        },
        "limit": {
          "type": "number",
          "maximum": 100,
          "minimum": 1,
          "description": "Max results (default 25, cap 100)"
        },
        "stage": {
          "type": "string",
          "description": "Stage filter, e.g. \"Seed\", \"Series A\", \"Debt\", \"Grant\""
        },
        "sector": {
          "type": "string",
          "description": "Sector filter (canonical), e.g. \"AI\", \"Fintech\", \"Healthtech\", \"Software\", \"Cleantech\", \"Energy\""
        },
        "country": {
          "type": "string",
          "description": "Country filter, e.g. \"UK\", \"Germany\", \"France\", \"Türkiye\""
        },
        "minAmountEur": {
          "type": "number",
          "description": "Only rounds of at least this many EUR"
        }
      }
    }
    arguments 40 lines
  • search_investors reads open 8h ago

    Search investors (entity-resolved: name variants are merged). Sortable by deal count or company count.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "page": {
          "type": "number",
          "minimum": 1
        },
        "sort": {
          "enum": [
            "deals_desc",
            "companies_desc",
            "name_asc"
          ],
          "type": "string"
        },
        "type": {
          "type": "string",
          "description": "Investor type filter, e.g. \"Venture Capital\""
        },
        "query": {
          "type": "string",
          "description": "Investor name or fragment, e.g. \"accel\""
        }
      }
    }
    arguments 26 lines
  • get_investor reads unknown 11h ago

    Investor profile: deal count, companies backed, stage mix, portfolio and recent deals.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Investor display name, e.g. \"Accel\" or \"High-Tech Gründerfonds (HTGF)\""
        },
        "compact": {
          "type": "boolean",
          "description": "Lean profile to save context: top 15 portfolio companies by €, top co-investors, no year-by-year breakdown"
        }
      }
    }
    arguments 17 lines
  • list_changes reads unknown 11h ago

    Incremental sync: what was ADDED or REMOVED since a timestamp. Use this — not repeated search_rounds calls — when you keep a local copy in step with the dataset. Sorted oldest-first by ingestion time, so `nextCursor` is resumable: store the last one and start there next run. Reports additions and removals only; the source tables have no modification timestamp, so a silent edit to an existing row is not reported (re-read that record by id when you need its current state). Exits are not available here — that table has no ingestion timestamp.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "since"
      ],
      "properties": {
        "type": {
          "enum": [
            "rounds",
            "companies"
          ],
          "type": "string",
          "description": "What to sync — \"rounds\" (default) or \"companies\""
        },
        "after": {
          "type": "string",
          "description": "Opaque nextCursor from a previous call"
        },
        "limit": {
          "type": "number",
          "maximum": 100,
          "minimum": 1,
          "description": "Max results (default 25, cap 100)"
        },
        "since": {
          "type": "string",
          "description": "Start of the window: a date (YYYY-MM-DD) or the ISO timestamp your last sync ended at"
        }
      }
    }
    arguments 31 lines
  • find_companies reads unknown 8h ago

    Find companies by name (case-insensitive substring). Returns id, location and verified funding totals; pass the id to get_company for the full profile.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "minLength": 2,
          "description": "Company name or fragment, e.g. \"Theker\", \"mistral\""
        }
      }
    }
    arguments 14 lines
  • get_company reads unknown 8h ago

    Full company profile: description, location, sectors, every funding round with stage/amount/investors, named backers, exit if any. Figures are source-linked on the company page URL.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Company id from find_companies or search_rounds"
        }
      }
    }
    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 7e71868485ddd82d.

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