Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.engrossa/ipnex

REMOTE · API.IPNEX.AI · SCANNED AUG 3

Cited, confidence-stamped patent intelligence over US university tech-transfer out-licensing.

Available components

+4 this week 59 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1002 tokens (~501/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · api.ipnex.ai

# add to Claude Code
claude mcp add --transport http engrossa-ipnex https://api.ipnex.ai/mcp
# ~/.codex/config.toml
[mcp_servers.engrossa-ipnex]
url = "https://api.ipnex.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "engrossa-ipnex": {
      "type": "remote",
      "url": "https://api.ipnex.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add engrossa-ipnex --url https://api.ipnex.ai/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  engrossa-ipnex:
    url: "https://api.ipnex.ai/mcp"
// mcp.json
{
  "mcpServers": {
    "engrossa-ipnex": {
      "type": "http",
      "url": "https://api.ipnex.ai/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 55

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://api.ipnex.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.ipnex.ai CN=WE1,O=Google Trust Services,C=US 2 Aug 2026 31 Oct 2026 ECDSA 256 ECDSA-SHA256 c19d066301da4cb10edb7bb0f4f73efb
SANs: api.ipnex.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of api.ipnex.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
ipnex.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.ipnex.ai/mcp Verified 200
http (plaintext) http://api.ipnex.ai/mcp HTTPS enforced 301 https://api.ipnex.ai/mcp
MCP tools — 2 exposed · ~473 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
get_technology ~125

Fetch the published view of one technology by its TTO docket. Cited + confidence-stamped; point-in-time via 'as_of'. Patent data: Google Patents (CC BY 4.0) + USPTO (public domain). Summaries are IPNEX-authored. TTO listing content is linked, not reproduced.

NameTypeReqDescription
as_ofstringISO-8601 timestamp for the point-in-time published view.
docketstringyesThe TTO docket id, e.g. 'P160232US05', 'S17-467'.

No output schema declared.

No examples provided.

search_licensable_ip ~348

Search published, licensable US university patent technologies. Answers 'what currently-Active US university IP is licensable from X?'. Every result is cited (Google Patents / USPTO), confidence-stamped, and carries an 'ownership' signal flagging whether the patent's current assignee of record is the marketing institution or a third party, a 'status' interpretation flagging public-domain (term-expired) vs revivable fee-lapsed vs in-force patents, and an 'expiry' reading of how many years of exclusive term remain (expired / expiring_soon / active_term). The response also carries 'facets' -- corpus-level breakdowns over all matches by ownership, institution, status, status_detail, and expiry (the whole-query split, without paging). Patent data: Google Patents (CC BY 4.0) + USPTO (public domain). Summaries are IPNEX-authored. TTO listing content is linked, not reproduced.

NameTypeReqDescription
institutionstringMarketing institution substring, e.g. 'Wisconsin', 'Stanford'.
keywordstringSubstring matched against the title and our summary.
licensable_from_institutionbooleanWhen true, exclude hits whose patent's current assignee of record is positively not the marketing institution (assigned-away or third-party owned); honest-unknowns are kept. Default false.
limitintegerMax results to return (confidence-sorted).
min_confidencenumberDrop results below this join confidence (0-1).
statusstringLegal-status substring, e.g. 'Active', 'Expired'.

No output schema declared.

No examples provided.