Remote MCP · Endpoint

BAMF.ai MCP server

No. BAMF.ai answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://mcp.bamf.ai/

The last check completed an MCP handshake.

Registry name
ai.bamf/bamf
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
405 ms
Tools exposed
177 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
LinkedIn and X content, scheduling, analytics and outreach agent for founders, via your BAMF login.
Listing
From the official MCP registry (active).
Recent checks of BAMF.ai
CheckedResultHandshake
6 hours agoHandshake completed405 ms
10 days agoHandshake completed278 ms
11 days agoHandshake completed222 ms
11 days agoHandshake completed351 ms
13 days agoHandshake completed287 ms
15 days agoHandshake completed298 ms
15 days agoHandshake completed250 ms
16 days agoHandshake completed338 ms
17 days agoHandshake completed341 ms
19 days agoHandshake completed4.37 s
22 days agoCredentials required—
24 days agoCredentials required—
26 days agoCredentials required—
29 days agoCredentials required—

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

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 BAMF.ai and makes no claim about it beyond what these checks measured.