Remote MCP · Endpoint

Builders in Fintech MCP server

No. Builders in Fintech answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://buildersinfintech.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.buildersinfintech/fintech-data
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
735 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Fintech companies, products, investors, funding rounds, news, podcast. Free, keyless, CC BY 4.0.
Listing
From the official MCP registry (active).
Recent checks of Builders in Fintech
CheckedResultHandshake
2 hours agoHandshake completed735 ms
2 days agoHandshake completed631 ms
4 days agoHandshake completed1.29 s
7 days agoHandshake completed1.35 s
9 days agoHandshake completed876 ms
11 days agoHandshake completed1.10 s
13 days agoHandshake completed871 ms
15 days agoHandshake completed183 ms
16 days agoHandshake completed745 ms
18 days agoHandshake completed779 ms
19 days agoHandshake completed615 ms
20 days agoHandshake completed667 ms
23 days agoHandshake completed1.06 s
24 days agoHandshake completed1.04 s

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Builders in Fintech and makes no claim about it beyond what these checks measured.