Remote MCP · Endpoint

API Plan Finder MCP server

No. API Plan Finder answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://plans.intoperson.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.scraping-api-plans/web-data-plan-finder
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
717 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Best API plans + report on 46 conditions for scraping, SERP, search, browser, email, TTS, STT, docs
Listing
From the official MCP registry (active).
Recent checks of API Plan Finder
CheckedResultHandshake
1 hour agoHandshake completed717 ms
3 days agoHandshake completed696 ms
12 days agoHandshake completed670 ms
13 days agoHandshake completed691 ms
15 days agoHandshake completed656 ms
15 days agoHandshake completed681 ms
17 days agoHandshake completed652 ms
18 days agoHandshake completed721 ms
18 days agoHandshake completed333 ms
20 days agoHandshake completed804 ms
22 days agoHandshake completed653 ms
25 days agoHandshake completed277 ms
27 days agoHandshake completed726 ms
29 days agoHandshake completed769 ms

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