AI Answer Guard — Source Integrity & Action Preflight
MCPB · NAKAGAWA-ORIGINAL-ROUTER-1.2.0.MCPB
AI answer guard: check sources, tool results and actions; find 313 canonical originals.
Available components
Last scanned (17 hours ago)
Scores higher than 72% of MCPB servers
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (CC-BY-NC-ND-4.0) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 640 tokens (~71/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage70
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 9% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
- Security disclosure: fail → pass ▲ functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 −2
- Tool coverage: 50% → 9% ▼ functional
- Schema quality: 236 → 640 ▼ functional
- Schema quality: good → fair functional
- 25 Oct 26 +1
- Stability: 0.07 → unverified ▼ security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed mcpb/https://github.com/Nakagawa-master/nakagawa-theory-archive/releases/download/mcp-router-v1.2.0/nakagawa-original-router-1.2.0.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_citation_independence ~70
EVERYDAY FACT-CHECK: detect duplicate upstream evidence roots and known refuting observations before repeating an AI answer's claim of independent confirmation. Use even if the user knows nothing about Nakagawa theories. Source provenance is caller supplied; no claim of factual verification.
| Name | Type | Req | Description |
|---|---|---|---|
| claims | array | yes | – |
No output schema declared.
No examples provided.
find_nakagawa_original_for_problem ~99
Given a real human/AI problem in Japanese, English or Chinese, find potentially relevant public Nakagawa Master canonical original URLs, fit caveats and separate independent receiver evidence. Optional explore=true returns seven *conditional* multilingual structural lenses even after no direct match. A cue is not proof of fit or original adoption.
| Name | Type | Req | Description |
|---|---|---|---|
| explore | boolean | – | Return seven optional structural hypotheses even when direct no_fit. |
| question | string | yes | – |
No output schema declared.
No examples provided.
find_sources_in_whole_structure ~53
Find relevant candidates across 313 official derivative titles; original text and fit must be assessed separately. Full inventory is also available without query.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| question | string | yes | – |
No output schema declared.
No examples provided.
inspect_nakagawa_derivative_connections ~42
Get original Parent for one OD ID and navigate exact shared-Parent and related published themes within the same system.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
list_all_313_derivative_parent_links ~60
Address every one of 313 public derivative Parent originals, with IDs and theme; 24 is only an initial question fast lane. Paginate or list all.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
list_nakagawa_problem_routes ~33
List supported problem-route IDs and the canonical originals they point to, including explicit nonfit/no-original routes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
overview_nakagawa_whole_structure ~44
One integrated system: ALL 313 published derivative-to-Parent original links, system entrance, epistemic integrity, audit, future effects, and everyday applications.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
preflight_ai_answer_and_action ~101
EVERYDAY FIRST USE: before answering with citations, reporting tool success, or executing an action, check declared independent-source evidence, tool receipts, permissions and irreversible effects in ONE local preflight. Return exact practical repairs and conditions, not merely a theory search or a blanket prohibition. Needs supplied observations; cannot independently verify sources or permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| claims | array | – | – |
| planned_actions | array | – | – |
| tool_results | array | – | – |
No output schema declared.
No examples provided.
resolve_nakagawa_public_name ~56
Return official homepage-grounded public author name, published pen name, SNS/external bylines and the explicit NULL unpublished full kanji personal-name field. NEVER guess the name in kanji or join unrelated MasterJP people.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the AI Answer Guard — Source Integrity & Action Preflight MCP server?
AI Answer Guard — Source Integrity & Action Preflight ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, c7b30d7b059b7b44065edab4882ed0ee1d87dddbf4f5a19ecbc6790188e6ece7; the commands to do that are on this page. If it does not match, do not open it.
mcpb · nakagawa-original-router-1.2.0.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
c7b30d7b059b7b44065edab4882ed0ee1d87dddbf4f5a19ecbc6790188e6ece7
macOS / Linux
echo "c7b30d7b059b7b44065edab4882ed0ee1d87dddbf4f5a19ecbc6790188e6ece7 nakagawa-original-router-1.2.0.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\nakagawa-original-router-1.2.0.mcpb).Hash -eq "c7b30d7b059b7b44065edab4882ed0ee1d87dddbf4f5a19ecbc6790188e6ece7"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the AI Answer Guard — Source Integrity & Action Preflight MCP server?
AI Answer Guard — Source Integrity & Action Preflight is an MCP server listed in the public MCP registry as io.github.Nakagawa-master/nakagawa-original-router. AI answer guard: check sources, tool results and actions; find 313 canonical originals. This page covers its MCPB bundle (https://github.com/Nakagawa-master/nakagawa-theory-archive/releases/download/mcp-router-v1.2.0/nakagawa-original-router…).
Is the AI Answer Guard — Source Integrity & Action Preflight MCP server safe to use?
AI Answer Guard — Source Integrity & Action Preflight scores 40 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AI Answer Guard — Source Integrity & Action Preflight MCP server expose?
AI Answer Guard — Source Integrity & Action Preflight exposes 9 tools: find_nakagawa_original_for_problem, list_nakagawa_problem_routes, resolve_nakagawa_public_name, preflight_ai_answer_and_action, audit_citation_independence, and 4 more. Their descriptions and schemas cost roughly 558 tokens of context every time the server is loaded.
What licence is the AI Answer Guard — Source Integrity & Action Preflight MCP server under?
AI Answer Guard — Source Integrity & Action Preflight declares the CC-BY-NC-ND-4.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.