World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
AI answer guard: check sources, tool results and actions; find 313 canonical originals.
제작자가 쓴 원문
목록은 사용 점수(100점 만점)로 정렬되며 구성은 다음과 같습니다
| 인기 | 0/80 | GitHub 별 또는 주간 다운로드: 큰 쪽 60, 작은 쪽 20 |
|---|---|---|
| 최신성 | 12/12 | 30일 안에 릴리스나 코드 변경이 있으면 만점 |
| 응답 중 | 0/8 | 마지막 점검 때 클라우드 엔드포인트가 응답 |
| 사용 점수 | 12/100 |
품질: 기본 점검 2/3개 통과(표시만, 정렬에는 안 씀) · 상승세: 데이터 없음 (급상승 탭에서만 사용)
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
검사 2/3 통과 · 내 컴퓨터에서 실행돼요
먼저: 어떤 AI를 쓰시나요?
쓰는 앱을 고르면 아래에 단계가 나옵니다.
Claude에 연결할 수 있지만 먼저 준비가 필요해요
키 필요 없음, 설치 필요 없음 · 컴퓨터용 Claude 앱(Windows 또는 Mac)에서만 되고 웹이나 모바일은 안 돼요
AI Answer Guard — Source Integrity & Action Preflight을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ Claude가 AI Answer Guard — Source Integrity & Action Preflight을 쓰고 있다고 하거나 답에 AI Answer Guard — Source Integrity & Action Preflight 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 Anthropic 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
ChatGPT는 아직 AI Answer Guard — Source Integrity & Action Preflight에 연결할 수 없어요
AI Answer Guard — Source Integrity & Action Preflight는 내 컴퓨터에 설치해서 쓰지만 ChatGPT는 웹에서 도는 서버만 연결할 수 있어요
A · AI Answer Guard — Source Integrity & Action Preflight에 연결되는 앱 쓰기
B · 기타에서 ChatGPT에 연결되는 다른 서버
같은 분류에서 많이 쓰는 것 중 키 없이 주소만으로 연결되는 것을 골랐어요
Claude Code는 아직 AI Answer Guard — Source Integrity & Action Preflight에 연결할 수 없어요
제작자가 컴퓨터용 Claude 앱 설치 파일만 제공해요
A · AI Answer Guard — Source Integrity & Action Preflight에 연결되는 앱 쓰기
Cursor는 아직 AI Answer Guard — Source Integrity & Action Preflight에 연결할 수 없어요
제작자가 컴퓨터용 Claude 앱 설치 파일만 제공해요
A · AI Answer Guard — Source Integrity & Action Preflight에 연결되는 앱 쓰기
VS Code는 아직 AI Answer Guard — Source Integrity & Action Preflight에 연결할 수 없어요
제작자가 컴퓨터용 Claude 앱 설치 파일만 제공해요
A · AI Answer Guard — Source Integrity & Action Preflight에 연결되는 앱 쓰기
이 서버의 연결 방식과 각 앱의 공식 문서를 바탕으로 했어요. 2026년 11월 10일 확인.
내 컴퓨터에서 실행하는 앱
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 20일 점검
레지스트리 이름이 GitHub 계정 Nakagawa-master 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
코드 마지막 변경: 어제
GitHub가 라이선스 종류를 알아내지 못했어요. 파일을 열어 확인하세요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/servers/nakagawa-master-nakagawa-original-router)질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.
아직 리뷰가 없어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 3개 중 2개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 어제 변경됐고, 최신 버전(1.2.0)은 23일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 MCPB도 있어야 해요.
같은 카테고리에는: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
같은 카테고리, 다른 제작자, 명령 확인 완료. 공식이 먼저, 그다음 스타 순.
카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 이 항목 AI Answer Guard — Source Integrity & Action Preflight | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 실행 위치 | 컴퓨터에 설치 필요 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 |
| 키 필요 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 |
| Claude에서 +로 추가 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 |
| 기본 점검 | 2/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 라이선스 | NOASSERTION | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 가격 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 |
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
A tool can appear to be available and still disappear in a name collision. An AI action can be marked approved without its outside effect ever being recorded. These are checkable engineering decisions covered here, alongside actual source reports, independent repairs and tests you can reproduce or challenge.
This is a public, non-canonical entry to the original work of 中川マスター (Nakagawa Master, pen name of Keisuke Nakagawa), independently authored implementation evidence and optional verification tools. No plugin, MCP installation or AI account is required merely to read or compare the source. Choose a real question first; return to the actual original when its conditions fit. A contrary result or genuine non-fit is useful.
| Real question | Public source or runnable check |
|---|---|
| Codex/Work authorization history: an old STOP preceded one later exact user grant. Did that grant fail to reach review, or does a separate policy still prohibit the action? | Run the dependency-free Node decision probe (node --test machine-discovery/guardian-authorization-witness.test.mjs) and inspect the reference core. 22 local positive/negative checks, including frozen payload, later revocation, single-use status, malformed cost/retry, and independent policy/network blocks. It never executes external actions or bypasses review; it is not integrated into Codex or ChatGPT Work. Original sources: OD075 — memory of consent and OD301 — epistemic integrity. Recipient-side Codex issue. |
| Multi-agent coexistence: Every possible world has a joint solution; can each actor choose it using only the observations available to them? Can pairwise success conceal a three-actor conflict or a bystander's loss? | Run the dependency-free finite local-policy probe (python3 machine-discovery/cross-origin-local-policy-probe.py --self-test; --sample hidden-world, --sample separate, --sample bystander, --sample pairwise). Change the JSON inputs to test your own *declared* finite model. The cases compare joint-Kernel feasibility, uniform local policy, original actors' B and third-party B, separately. Source: Nakagawa Master's Human-Descendant AI Civilization Theory, Part 20, especially Chapters 5–9. Synthetic diagnostics do not establish a real third intelligence, authorization, independent adoption or superiority to established model checking. |
| Pydantic AI tool retries: The provider sent an empty tool-call ID. Why does a retry answer a different, newly generated call instead? | Independent reporter/implementer PR #12846 shows the original if tool_call_id: truthiness gap and an is not None correction with a failing-before/green-after regression. Inspect the actual code and decide if a provider's empty ID is valid in your client. Not a Nakagawa Master-discovered/fixed PR; still OPEN/unmerged. An optional, separate original comparison on establishment conditions is available if it truly fits your question, not proof the engineer read it. |
| LangGraph human answer after retry: An AI agent asks again, takes your new 7, but returns the earlier 5. Was the second human answer ever used? | Actual user reproduction #9478 → Nakagawa Master's two distinct user-visible acceptance contracts → outside developer explicitly credited both options and built two separate fork implementations. The latest fork actually asks twice and checks [5,7]; the older PR #9656 is auto-closed/unmerged and has the OTHER version. Original theory on reconstructed memory and source traces is optional independent reading, not the developer's claimed source. Readable example #75 · machine route. |
| Qwen Code: Can duplicate MCP tool names hide otherwise usable tools? | Original reporter installed-version confirmation pending (no reply yet), Clean/collision fixture and independent installed-CLI retest, original reporter, different engineer's merged fix, official v0.26.6 release and v0.26.7 release |
| Qwen Code ACP teammate reports: A report arrives during shutdown. If close rolls back, does the system actually resume reading that teammate's messages? | Nakagawa Master's original final-inbox/shutdown inverse → independent implementer @yiliang114's accepted correction and tests. Later a separate reviewer @wenshao independently reproduced a new reversible-close failure on a real mailbox/500-ms poll (head 0/1 reports delivered, control 1/1). The implementer's new commit 7f461ff resumes intake after rollback and adds actual TeamManager/mailbox, repeated-resume and terminated-team tests. This later failure was found independently by the reviewer, not Nakagawa Master. At updated head 28c31247, @wenshao's independent real-mailbox recheck measured the previously undelivered report as delivered (1/1 versus 0/1 on the preceding head) and recorded 76/76 checks, with a smaller residual delay window and coverage gap; On November 11, [the actual implementer @yiliang114 replied directly to the Master's October 28 source review](https://github.com/QwenLM/qwen-code/pull/15658#discussion_r4532621299), confirming the specific after-flush inbox-race was closed by November 8's independent patch and mutation-sensitive regression: quiesce poll, await the in-flight delivery, drain, then seal before writers close. The review acknowledges the Master-origin counterexample while preserving the author's implementation and separate reviewer's distinct rollback defect. PR #15658 remains OPEN/unmerged at HEAD 07e24a8e on November 11; neither containing release nor an installed affected-user recovery is yet established. Compare the related original on establishment conditions only if fitting; the implementer is not claimed to have read it. |
| Qwen Code MCP cancel: After an AI tool call is cancelled, can a broken MCP connection be repaired without replaying the cancelled action or restarting a server its operator stopped? | Affected user issue #12160 → Nakagawa Master's deferred-discovery cancellation review → @wenshao's independently executed 3,041 ms vs 1 ms real-server control → @2SinceJuly's own repair and tests. @wenshao separately tested operator shutdown and reentrant discovery. After an attempted client-status fix, Nakagawa Master identified that the actual raw SDK client has no getStatus(); the developer explicitly confirmed this and rewrote the guard to use an operator-teardown marker, with no-fabricated-method regression tests in 03690bc and a separate pool-teardown repair in e246fbe. Later bot suggestions on App cancellation, listener lifetime and teardown ordering led to the developer's further App-path fix and discriminating tests f29dcb8. These are separate reviewers' and implementer's contributions. [PR #16661](https://github.com/QwenLM/qwen-code/pull/16661) is still OPEN/UNMERGED at November 11 HEAD `9e42f869`. The latest change corrected English design wording; it did not implement the reviewer's still-unresolved Critical: same-named pool connections share a name-keyed disconnect signal, so one connection's teardown may wrongly reconnect or suppress repair of another. For a real session, distinguish **(1) a cancelled call that must not replay, (2) a disconnected transport that should recover for a *future* call, and (3) a deliberate user disconnect that must stay disconnected, including concurrent same-name connections. In [live head-bound CI, the full required run is red](https://github.com/QwenLM/qwen-code/actions/runs/42934403348). The [source-checked underlying-shard diagnosis posted by Nakagawa Master](https://github.com/QwenLM/qwen-code/pull/16661#issuecomment-6785607218) identifies two failing CLI/helper assertions on Linux shard 1; on Linux shard 2 the main Vitest suite passed 1,868 tests, but a separate integrations/external-context test still failed three retries on an invalid `HTTP_PROXY` value; and the no-AK integration process ended with JavaScript heap exhaustion. The same [CI comment was corrected in place](https://github.com/QwenLM/qwen-code/pull/16661#issuecomment-6785607218) to avoid the misleading implication that shard 2's entire job passed. Those CI symptoms do not independently prove the pool-provenance bug either fixed or harmless. The latest CI triage is a submitted external comment, without a developer adoption or maintainer fix confirmed yet**. An upstream merge, a containing release and the original affected user's own installed-session recovery remain to be checked. A related original discussion of establishment conditions is available for independent comparison of the cancellation, attempted repair and actual recovery cond