Remote MCP · Endpoint

Builders in Fintech MCP server

No. Builders in Fintech answered an MCP handshake 27 minutes ago.

UpLast checked 27 minutes 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
1.08 s
Tools exposed
32 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Fintech companies, products, rounds, investors, news, Agent-Ready scores. Free, keyless, CC BY 4.0.
Listing
From the official MCP registry (active).
Recent checks of Builders in Fintech
CheckedResultHandshake
27 minutes agoHandshake completed1.08 s
10 days agoHandshake completed1.19 s
11 days agoHandshake completed245 ms
12 days agoHandshake completed1.30 s
13 days agoHandshake completed947 ms
14 days agoHandshake completed177 ms
15 days agoHandshake completed1.10 s
16 days agoHandshake completed940 ms
17 days agoHandshake completed1.31 s
19 days agoHandshake completed1.02 s
22 days agoHandshake completed735 ms
24 days agoHandshake completed631 ms
26 days agoHandshake completed1.29 s
29 days agoHandshake completed1.35 s

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

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.