korean-patent-mcp

Name: korean-patent-mcp
Author: io.github.didrod205

MCPattested

v1.3.6io.github.didrod205UnknownUpdated 18d agonpm GitHub

특허 검색이 아니라 존속 판정: 특허·실용신안 번호가 지금도 유효한지 등록원부 연차료까지 대조해 소멸 사유와 함께 알려줍니다

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build

A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.

1GitHub stars

18d agoLast update

Needs 1 credential before it runs

KIPRIS_SERVICE_KEYAPI keyrequired
KIPRIS Plus 서비스 키. plus.kipris.or.kr에서 무료로 발급합니다(공공데이터포털 키가 아닙니다).
DATA_GO_KR_SERVICE_KEYAPI keyoptional
선택. 공공데이터포털 등록원부 API 키(일반 인증키 Decoding). 넣으면 만료일·권리자·연차료를 등록원부 확정값으로 판정합니다.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package

Authorio.github.didrod205

LicenseUnknown

Version1.3.6

Sourcenpm+mcp-registry

npmkorean-patent-mcp

GitHubdidrod205/korean-patent-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

85/100Trusted

✓Listed in Forge index+10/10

✓Identity verified · attested build+20/20

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓npm Trusted Publishing (Sigstore)+5/5

—npm maintainer match+0/5

→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusIdentity verified

PublisherUnverified

SignatureUnsigned

Domain—

Provenance✓ Sigstore-verified · 456ca57

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface3 tools · none privileged

Security scan✓ Cleanv1.3.6 · 18d agoHow well does this scan work?

EvalsNone

IndexedSep 17, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

3 tools · none privileged

Statically extracted from the published packagev1.3.6 · 18d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

rights_alive특허·실용신안 번호 하나를 받아 그 권리가 지금 살아있는지 판정합니다.

특허·실용신안 번호 하나를 받아 그 권리가 지금 살아있는지 판정합니다.

No input schema was published for this tool.

verify_citations텍스트에 인용된 특허번호가 진짜인지 통째로 검증합니다.

텍스트에 인용된 특허번호가 진짜인지 통째로 검증합니다.

No input schema was published for this tool.

search_ip특허·실용신안을 키워드로 검색합니다. 모든 결과에 생사(alive) 판정이 붙어서 나오며,

특허·실용신안을 키워드로 검색합니다. 모든 결과에 생사(alive) 판정이 붙어서 나오며,

No input schema was published for this tool.

3 of 3 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

특허 검색이 아니라 존속 판정: 특허·실용신안 번호가 지금도 유효한지 등록원부 연차료까지 대조해 소멸 사유와 함께 알려줍니다

Keywords

mcp

Alternatives

Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-17 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod3.25.76
@modelcontextprotocol/sdk1.30.017 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.8
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.6.5
- cors2.8.6+1 not drawn1 dependency
  - object-assign4.1.1
- hono4.13.8
- jose6.2.12
- express5.2.1+27 not drawn1 dependency
  - content-type1.0.5
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.1
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.0+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 49
below the depth cap: 5

wrappy 1 — required by once@1.4.0package cap reached
http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached
parseurl ^1.3.3 — required by router@2.2.0package cap reached

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

korean-patent-mcp

Tools

Tools exposed

Dependency tree

Declared but not resolved