MCP server for InsForge BaaS — database, storage, edge functions, and deployments
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"insforge-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Every successful check was an authentication response (401/403). The endpoint exists and enforces authentication; nothing behind that boundary — tools, behaviour, service health — has been observed. Latency here is time to authentication response. Tools: not measured — authentication required.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 3 h ago | mcp initialize | ok | 401 | 195 ms | auth required |
| 10 h ago | mcp initialize | ok | 401 | 173 ms | auth required |
| 17 h ago | mcp initialize | ok | 401 | 175 ms | auth required |
| 24 h ago | mcp initialize | ok | 401 | 174 ms | auth required |
| 31 h ago | mcp initialize | ok | 401 | 141 ms | auth required |
| 2 d ago | mcp initialize | ok | 401 | 408 ms | auth required |
| 2 d ago | mcp initialize | ok | 401 | 164 ms | auth required |
| 2 d ago | mcp initialize | ok | 401 | 200 ms | auth required |
| 2 d ago | mcp initialize | ok | 401 | 273 ms | auth required |
| 3 d ago | mcp initialize | ok | 401 | 195 ms | auth required |
Attributed to the source that supplied each field. Treated as claims, not facts.
No long description beyond the summary.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.