api.seiche.info
https://api.seiche.info/palimpsest/mcp
active Production-safe Score 96/100 http no auth
At a glance
| Endpoint | https://api.seiche.info/palimpsest/mcp |
|---|---|
| Source | https://github.com/beepboop2025/palimpsest/blob/main/.github/workflows/registry-publish.yml |
| Transport | http |
| Tools | 7 |
| Auth | none |
| First seen | 2026-08-24 12:50:24 |
| Last checked | 2026-11-17 21:58:23 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 276 / 433 ms |
| Last successful check | 2026-11-17 21:58:23 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (7)
research_catalog— Discover every Palimpsest dataset, including the latest China economic histories, external trade, regional research, information controls anlist_signals— List every published signal Palimpsest exposes across its three applications: name, one-line description and source URL for each. Censorshipget_signal— Read one named signal. Permitted signals return their bounded latest payload; China-economic signals in the denied lineage closure return exget_newsroom— Read one evidence-first reporting surface without scraping a page or guessing a filename. Views: 'newsroom' for prioritized deterministic stinspect_economic_publication_rights— Inspect publication-rights metadata for China economic evidence. Returns the policy digest, UTC evaluation clocks, per-source decisions andwhats_happening— Judge whether anything is happening in Chinese censorship right now, across every signal at once: the board's own cross-signal verdict withgfw_reading— Read the Great Firewall's current state at both layers in one call: live network blocking measured inside China via OONI (website, messenger
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:58:23 | ✓ | ✓ | 153 ms | 95 | active |
| 2026-11-17 21:43:21 | ✓ | ✓ | 297 ms | 95 | active |
| 2026-11-17 21:28:20 | ✓ | ✓ | 161 ms | 95 | active |
| 2026-11-17 21:13:13 | ✓ | ✓ | 145 ms | 95 | active |
| 2026-11-17 20:57:41 | ✓ | ✓ | 303 ms | 91 | active |
| 2026-11-17 20:42:39 | ✓ | ✓ | 126 ms | 95 | active |
| 2026-11-17 20:27:38 | ✓ | ✓ | 143 ms | 95 | active |
| 2026-11-17 20:12:36 | ✓ | ✓ | 126 ms | 95 | active |
| 2026-11-17 19:55:17 | ✓ | ✓ | 146 ms | 95 | active |
| 2026-11-17 19:40:11 | ✓ | ✓ | 128 ms | 95 | active |
| 2026-11-17 19:24:51 | ✓ | ✓ | 129 ms | 95 | active |
| 2026-11-17 19:09:45 | ✓ | ✓ | 280 ms | 95 | active |
| 2026-11-17 18:54:37 | ✓ | ✓ | 270 ms | 95 | active |
| 2026-11-17 18:39:30 | ✓ | ✓ | 295 ms | 95 | active |
| 2026-11-17 18:24:23 | ✓ | ✓ | 479 ms | 91 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://api.seiche.info/palimpsest/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/api-seiche-info-palimpsest-mcp # JSON