io.github.lizhuojunx86/chinese-history-mcp

The evidence

Every deduction below names the artefact that produced it. Nothing on this page was executed: the source was read, never run, and no running server was contacted.

Code Safety

• src/storyextractor/db.py:639mcp-python-sql-string-built (medium/medium)

  A SQL statement is assembled by string building rather than passed as a parameterised query. Every driver here accepts parameters as a second argument; building the string is never necessary.

  def _add_column(conn: sqlite3.Connection, table: str, col: str, decl: str) -> None:
      """Idempotent ALTER ADD COLUMN (SQLite errors if a column is added twice)."""
      existing = {r[1] for r in conn.execute(f"PRAGMA table_info({table})")}
      if col not in existing:
          conn.execute(f"ALTER TABLE {table} ADD COLUMN {col} {decl}")

• src/storyextractor/db.py:641mcp-python-sql-string-built (medium/medium)

  A SQL statement is assembled by string building rather than passed as a parameterised query. Every driver here accepts parameters as a second argument; building the string is never necessary.

      existing = {r[1] for r in conn.execute(f"PRAGMA table_info({table})")}
      if col not in existing:
          conn.execute(f"ALTER TABLE {table} ADD COLUMN {col} {decl}")
  
  

• src/storyextractor/db.py:847mcp-python-sql-string-built (medium/medium)

  A SQL statement is assembled by string building rather than passed as a parameterised query. Every driver here accepts parameters as a second argument; building the string is never necessary.

          if version < ver:
              fn(conn)
              conn.execute(f"PRAGMA user_version = {ver}")   # ver 为内部 int 常量, 无注入风险
      conn.commit()
  

• src/storyextractor/mcp/queries.py:110mcp-python-sql-string-built (medium/medium)

  A SQL statement is assembled by string building rather than passed as a parameterised query. Every driver here accepts parameters as a second argument; building the string is never necessary.

                       "WHERE es.event_id=e.id AND b.slug=?)")
          params.append(book)
      total = conn.execute(
          f"SELECT COUNT(*) FROM events e WHERE {' AND '.join(where)}", params).fetchone()[0]
      rows = conn.execute(

• src/storyextractor/mcp/queries.py:157mcp-python-sql-string-built (medium/medium)

  A SQL statement is assembled by string building rather than passed as a parameterised query. Every driver here accepts parameters as a second argument; building the string is never necessary.

      返回 (row, candidates)。candidates 非空 = 需消歧 (同名异指 / 多人共用一别名)。
      整词匹配杜绝 '霸'→西楚霸王 一类子串误配; 命中>1 时不静默 LIMIT 1 任意取。"""
      exact = conn.execute(
          f"SELECT {_ENTITY_COLS} FROM entities WHERE name=? OR slug=?", (name, name)).fetchall()
      if len(exact) == 1:

Auth Posture

• authentication_model

  stdio transport: the client launches the server as a subprocess, so the OS process boundary is the auth boundary — `03` §4 does not penalise absent auth here

• transport_security

  declared transport: stdio — launched as a subprocess by the client, so the security boundary is the client process, not a network port (`03` §4)

• secret_handling

  no committed credential found, and no environment variable with a credential-shaped name is read anywhere in the source

• authorization_granularity

  no tool registration was recognised anywhere in the source. An MCP server registers tools by definition, so this is a gap in our detection rather than a server with none, and `03` §4's threshold cannot be applied to it.

Maintenance

• recency

  last commit 74 day(s) before 2026-10-16

• issue_responsiveness

  this repository has no issues `03` §5's window covers. An unanswered issue scores 0 under §5, but a repository with no issues filed has not failed to answer one.

• release_cadence

  released 2 day(s) ago (by releases), inside `03` §5's 30-day window

• bus_factor

  sole maintainer

• repository_signals

  `03` §5 scores this by quartile WITHIN the server's category, which needs a distribution across every scanned server and so cannot be computed while scanning one. It is a post-pass over the crawl and that pass does not exist yet.

Transparency

• license

  LICENSE present with no SPDX-License-Identifier tag; identified as 'MIT' from its text

• readme_quality

  README.md: installation instructions (+25), configuration documented (+25), exposed tools or resources enumerated (+30), states what the server does in the first 200 words (+20)

• declared_scopes

  specific scope or access documentation is present, but `03` §7's 100 and 60 bands both compare it against scopes INFERRED from static analysis, which is not built yet. Scoring 100 on an empty inference would be a vacuous truth — 'all ∅ inferred scopes are documented'.

• changelog

  no CHANGELOG in the fetched source. `03` §7's partial credit for tagged releases carrying release notes is not applied here — that needs the forge API, which this check does not call

• security_contact

  no SECURITY.md and no disclosure contact in the README, so a finder has no route to report a vulnerability privately