Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Palimpsest — censorship, China economy and model-eval observatory

REMOTE · API.SEICHE.INFO · SCANNED SEP 20

Rights-aware censorship, China-economic status, and tamper-evident AI evaluation tools.

Available components

0 this week 80 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability76
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2206 tokens (~275/item across 8 items; 7 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 77% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Palimpsest — censorship, China economy and model-eval… MCP server?

Palimpsest — censorship, China economy and model-eval… is a hosted endpoint at https://api.seiche.info/palimpsest/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.seiche.info

# add to Claude Code
claude mcp add --transport http beepboop2025-palimpsest 'https://api.seiche.info/palimpsest/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "beepboop2025-palimpsest": {
      "url": "https://api.seiche.info/palimpsest/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "beepboop2025-palimpsest": {
      "type": "http",
      "url": "https://api.seiche.info/palimpsest/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.beepboop2025-palimpsest]
url = "https://api.seiche.info/palimpsest/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "beepboop2025-palimpsest": {
      "type": "remote",
      "url": "https://api.seiche.info/palimpsest/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add beepboop2025-palimpsest --url 'https://api.seiche.info/palimpsest/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  beepboop2025-palimpsest:
    url: "https://api.seiche.info/palimpsest/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "beepboop2025-palimpsest": {
      "Transport": "http",
      "Url": "https://api.seiche.info/palimpsest/mcp"
    }
  }
}
# add to Vellum
assistant mcp add beepboop2025-palimpsest -t streamable-http -u 'https://api.seiche.info/palimpsest/mcp'
// mcp.json
{
  "mcpServers": {
    "beepboop2025-palimpsest": {
      "type": "http",
      "url": "https://api.seiche.info/palimpsest/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 9 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool coverage: 85% → 77% functional
    • New tool “research_catalog” functional
  • 29 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_newsroom” rewrote its description, which is the text the model reads security
    • Tool “get_signal” rewrote its description, which is the text the model reads security
    • Tool “list_signals” rewrote its description, which is the text the model reads security
    • Tool “query_economic_observations” rewrote its description, which is the text the model reads security
    • Schema quality: 355 → 296 functional
    • The server now declares the “resources” capability functional
    • New resource “china-economic-publication-rights” functional
    • Server version: 1.9.1 → 1.9.3 functional
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
    • Server version: 1.9.0 → 1.9.1 functional
  • 24 Aug 26 0
    • Tool “get_newsroom” rewrote its description, which is the text the model reads security
    • Server version: 1.8.1 → 1.9.0 functional
  • 23 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_signal” rewrote its description, which is the text the model reads security
    • Tool “list_signals” rewrote its description, which is the text the model reads security
    • Tool “whats_happening” rewrote its description, which is the text the model reads security
    • Schema quality: 272 → 350 functional
    • Tool coverage: 67% → 85% functional
    • Server version: 1.5.0 → 1.8.1 functional
    • New tool “query_economic_observations” functional
    • “get_signal” reworded the description of “name” cosmetic
  • 12 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool coverage: 100% → 67% functional
    • Schema quality: 1137 → 1360 functional
    • MCP protocol: pass → fail functional
    • New prompt “evidence_desk_briefing” functional
    • MCP protocol version: 2025-11-25 → 2025-06-18 functional
    • Server version: 1.3.1 → 1.5.0 functional
    • New tool “get_newsroom” functional
Diagnostics

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 20 Sept 2026 · Probed https://api.seiche.info/palimpsest/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.seiche.info CN=YE1,O=Let's Encrypt,C=US 7 Sept 2026 6 Dec 2026 ECDSA 256 ECDSA-SHA384 51c1896503dd693d96ce81ef09be5a03892
SANs: api.seiche.info
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of api.seiche.info. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
info. present 5104 8 Verified
seiche.info. present 2371 13 Verified
api.seiche.info. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'none'; frame-ancestors 'none'; base-uri 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.seiche.info/palimpsest/mcp Verified 200
http (plaintext) http://api.seiche.info/palimpsest/mcp HTTPS enforced 308 https://api.seiche.info/palimpsest/mcp
MCP tools · 7 exposed · ~1,299 tokens

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 →

Tool Tokens
get_newsroom ~209

Read one evidence-first reporting surface without scraping a page or guessing a filename. Views: 'newsroom' for prioritized deterministic stories, 'wire' for normalized source dossiers, 'economy' for the currently restricted China economic pulse, 'machine-analysis' for the currently restricted AnalysisReports and AbstentionReports, 'investigations' for review-gated research leads, 'editorial-readiness' for publication gates, and 'interconnection' for named-key fat-object joins on China situation events (topic-surface-only, never wire corroboration). The economy, machine-analysis and interconnection views are metadata-only until a lineage-filtered rebuild removes denied derivatives. Availability never implies publication readiness: statuses, gates, counterevidence, limitations and right-to-reply state stay attached.

NameTypeReqDescription
limitinteger
prioritystringoptional exact priority filter for the newsroom view
statusstringoptional exact status filter for story/case views
viewstring

No output schema declared.

No examples provided.

get_signal ~307

Read one named signal. Permitted signals return their bounded latest payload; China-economic signals in the denied lineage closure return explicit restricted/unavailable rights metadata and no values. Call list_signals first to discover valid names. Use this for the AI-model-evaluation side too: 'eval-registry' returns the pre-registered, hash-chained eval ledger with its verified flag and Merkle root, 'gfi-transcripts' returns a bounded view of the complete GFI v2 response matrix, and 'refusal-drift' returns the current frontier-model refusal reading on the frozen benign probe set; read 'eval-assurance' before turning either into a validity claim, and 'eval-journal' for the evidence-bound explanation and source receipts, or 'eval-findings' for the current deterministic article edition. Distinct from gfw_reading, which merges the two Great Firewall layers into one combined view.

NameTypeReqDescription
max_rowsintegercap on long row arrays (dataset, ranked, samples). Default 25 keeps a call small enough not to stall a tool loop; the generative-firewall-index dataset is 132 rows. Any cap applied is reported in the…
namestringyessignal name from list_signals, e.g. 'ooni-gfw', 'eval-registry', 'eval-assurance', 'eval-journal', 'eval-findings', 'gfi-transcripts' or 'refusal-drift'

No output schema declared.

No examples provided.

gfw_reading ~96

Read the Great Firewall's current state at both layers in one call: live network blocking measured inside China via OONI (website, messenger and circumvention-tool reachability) joined with model-layer censorship from the Generative Firewall Index over Chinese LLMs. Takes no arguments. A combined convenience view — for one layer's full raw payload use get_signal with 'ooni-gfw' or 'generative-firewall-index'.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_signals ~182

List every published signal Palimpsest exposes across its three applications: name, one-line description and source URL for each. Censorship and information control — OONI Great Firewall probes, Censored Planet, IODA outages, circumvention demand, takedown and redaction pressure, and the board's own verdict. China economics — explicit metadata-only rights status for affected observations, pulse, forecast and derivative surfaces; no denied values are returned. AI model evaluation — the tamper-evident, pre-registered eval registry (hash-chained and Merkle-rooted), its claim-by-claim assurance ceiling, evidence-bound Eval Journal, deterministic live findings, and frontier-model refusal drift, alongside the Generative Firewall Index over a named China-focused panel. Takes no arguments. Call this first to discover signal names, then get_signal for one full reading.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

query_economic_observations ~295

Inspect the native publication-rights status for the China-economic observation surface. The reviewed default-deny policy does not authorize redistribution of current CFETS/ChinaMoney values, so this tool returns policy digest, UTC clocks, per-source decisions and zero published-record status only. It never reads or returns observation rows, empty row arrays, derived signals, or neutral replacements. Filters are validated for contract compatibility but cannot override source rights.

NameTypeReqDescription
as_ofstringpoint-in-time cutoff applied to BOTH released_at and collected_at; omitted means the full published ledger
cursorstringopaque next_cursor from the preceding page
firm_sizestringexact firm_size filter
geographystringexact geography filter
limitinteger
ownershipstringexact ownership filter
period_endstringinclusive upper bound on observation period_end
period_startstringinclusive lower bound on observation period_start
released_fromstringinclusive lower bound on released_at
released_tostringinclusive upper bound on released_at
revision_viewstringall visible vintages, or the newest knowable revision per source/series/slice/period
sectorstringexact sector filter
series_idstringexact series_id filter
source_idstringexact source_id filter

No output schema declared.

No examples provided.

research_catalog ~85

Discover every Palimpsest dataset, including the latest China economic histories, external trade, regional research, information controls and model evaluations. Paginated metadata retains source clocks, rights and access states. Includes the Seiche research_network handoff for funding, institution and market-liquidity context; values are not copied.

NameTypeReqDescription
limitinteger
offsetinteger

No output schema declared.

No examples provided.

whats_happening ~125

Judge whether anything is happening in Chinese censorship right now, across every signal at once: the board's own cross-signal verdict with the multiplicity paid for (false-discovery control) and coverage confounds flagged as measurement artifacts, never findings. Takes no arguments. Use this instead of fetching signals individually and reconciling them yourself; then use get_signal to drill into whichever signal moved. Scope note: this is the censorship board. For the AI-model-evaluation side use get_signal with 'eval-registry', 'eval-assurance' or 'refusal-drift'.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the Palimpsest — censorship, China economy and model-eval… MCP server?

Palimpsest — censorship, China economy and model-eval… is an MCP server listed in the public MCP registry as io.github.beepboop2025/palimpsest. Rights-aware censorship, China-economic status, and tamper-evident AI evaluation tools. This page covers its hosted endpoint (https://api.seiche.info/palimpsest/mcp).

Is the Palimpsest — censorship, China economy and model-eval… MCP server safe to use?

Palimpsest — censorship, China economy and model-eval… scores 80 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 Palimpsest — censorship, China economy and model-eval… MCP server expose?

Palimpsest — censorship, China economy and model-eval… exposes 7 tools: research_catalog, list_signals, get_signal, get_newsroom, query_economic_observations, and 2 more. Their descriptions and schemas cost roughly 1,299 tokens of context every time the server is loaded.

Does the Palimpsest — censorship, China economy and model-eval… MCP server require authentication?

No. We connected to Palimpsest — censorship, China economy and model-eval… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Palimpsest — censorship, China economy and model-eval… MCP server still maintained?

Palimpsest — censorship, China economy and model-eval… is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.