Ipable MCP Server

@ipable/mcp npm v0.6.0

Published by @ipable — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 100 − adoption risk = 98/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 2 = 98. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 38

Each tool and what it can reach — statically extracted from the published source.

  • descriptionno sensitive capability
  • discover-technologyno sensitive capability
  • explore-technologyno sensitive capability
  • ipable_assess_patent_directionno sensitive capability
  • ipable_assignee_landscapeno sensitive capability
  • ipable_chatno sensitive capability
  • ipable_check_alertsno sensitive capability
  • ipable_claim_elementsno sensitive capability
  • ipable_claim_overlapno sensitive capability
  • ipable_classify_patentno sensitive capability
Show 28 more tools ↓
  • ipable_classify_patent_from_featuresno sensitive capability
  • ipable_cluster_patentsno sensitive capability
  • ipable_cluster_prior_artno sensitive capability
  • ipable_company_overviewno sensitive capability
  • ipable_company_tech_portfoliono sensitive capability
  • ipable_cross_domainno sensitive capability
  • ipable_element_landscapeno sensitive capability
  • ipable_find_similar_patentsno sensitive capability
  • ipable_find_technologyno sensitive capability
  • ipable_fto_riskno sensitive capability
  • ipable_graph_statsno sensitive capability
  • ipable_ipc_distributionno sensitive capability
  • ipable_ipc_vs_clusterno sensitive capability
  • ipable_list_technologiesno sensitive capability
  • ipable_market_concentrationno sensitive capability
  • ipable_my_subscriptionsno sensitive capability
  • ipable_novel_elementsno sensitive capability
  • ipable_obviousness_checkno sensitive capability
  • ipable_problem_mapno sensitive capability
  • ipable_research_intensityno sensitive capability
  • ipable_search_claimno sensitive capability
  • ipable_similar_limitationsno sensitive capability
  • ipable_subscribeno sensitive capability
  • ipable_technology_flowno sensitive capability
  • ipable_technology_timelineno sensitive capability
  • ipable_unsubscribeno sensitive capability
  • Motor Control Technology Taxonomyno sensitive capability
  • technologyno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.6.0 latest A 98/100 0 1.9.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/ipable-mcp/badge.svg)](https://mcptrustchecker.com/registry/ipable-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/ipable-mcp"><img src="https://mcptrustchecker.com/registry/ipable-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/ipable-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @ipable/mcp --online

Use the free API → How scoring works

More in Developer Tools