Customs Declaration Consistency

io.github.PerryLinkPublished by GitHub account PerryLinkv0.1.0Updated Oct 26, 2026

Read-only MCP server that checks a Chinese customs declaration ledger for internal inconsistency.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Read-only MCP server that checks a Chinese customs declaration ledger for internal inconsistencies, for use in a local desktop assistant.

What you can do
  • Inspect a Chinese customs declaration ledger and flag internal inconsistencies.
  • Operates read-only, so it reports findings rather than editing the ledger.
  • Runs as a local stdio process started by the assistant on the user's machine.
  • No tool list, instructions or README is published, so the exact checks and inputs are not documented.
When to use it
Worth adding when you work with Chinese customs declaration ledgers and want an assistant to spot internal inconsistencies in them before submission or review. It is a narrow, single-purpose checker, so it is not useful for other kinds of data.
Requirements
A local desktop environment that can run a stdio MCP server, plus the npm package dsh-customs-mcp installed and launched by the assistant. No authentication, environment variables or headers are declared. The ledger to check must be accessible locally.
Before you install
The server is read-only, so it should not alter your ledger, but confirm that before pointing it at production data. No tool list or documentation is published, so what it reads and whether anything leaves the machine cannot be verified from the listing. Customs declaration data is sensitive commercial information; keep it local.

Installation

In SourceWeft

  1. Open Customs Declaration Consistency in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 20, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.