**Know what's protectable before competitors copy it.** FITTIN runs an instant IP-strategy check on your startup idea, repo, or pitch — right inside your AI assistant. Right in your chat — no signup — you get: - 🛡️ **Clone risk** — how fast big-tech could copy you - 🏰 **Your one defensible moat** — what actually protects you - ⚖️ **What's patentable** — which features pass, which fail the §101 abstract-idea test - 🔒 **Patent vs. trade secret** — so you don't publish away what you should protect **Tools** - `fittin_patentability` — instant inline protection check - `fittin_invention` — capture an invention disclosure - `fittin_protect` — moat & clone-risk read - `fittin_report` — order the full IP package **Free** to try. The **$99 IP Portfolio Package** delivers six attorney-ready documents: patentability analysis, market & prior-art landscape, patent strategy for counsel, technical assignment & next steps, a preliminary patent application draft, and an IP risk & opportunity repo
fittin-ip is a remote MCP server published at fittin.dev. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 583 ms, a delay an agent will notice. It offers a narrow, focused set of 4 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
fittin_patentability — No explicit guidance on when to use for different invention typesfittin_invention — Lacks clarity on input requirements for technical contributionsfittin_protect — Ambiguous prioritization criteria for IP opportunitiesfittin_report — No mention of input validation for professional document generationRisk: medium
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/revkov-fittin-ip)<a href="https://mcpmetrics.io/servers/revkov-fittin-ip"><img src="https://mcpmetrics.io/badge/revkov/fittin-ip/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-11 15:07:20 | Legacy | 200 | 682 | 200 | 588 | 2024-11-05 |
| 2026-09-11 13:13:33 | Legacy | 200 | 614 | 200 | 583 | 2024-11-05 |
| 2026-09-11 11:20:19 | Legacy | 200 | 641 | 200 | 650 | 2024-11-05 |
| 2026-09-11 09:28:19 | Legacy | 200 | 580 | 200 | 550 | 2024-11-05 |
| 2026-09-11 07:35:54 | Legacy | 200 | 561 | 200 | 553 | 2024-11-05 |
| 2026-09-10 21:16:35 | Unknown | 404 | 332 | 404 | 332 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.