Signetex
REMOTE · MCP.SIGNETEX.CH
Public AI claim register: E0-E4 evidence grades, forecast tracking, no verdicts.
Available components
Last scanned (15 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Education and Research
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 Security46
- 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 9 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1451 tokens (~161/item across 9 items; 9 tools + 0 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “register_stats” rewrote its description, which is the text the model reads security
- Tool “track_record” rewrote its description, which is the text the model reads security
- Server version: 1.7.24 → 1.7.33 functional
- 20 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.7.5 → 1.7.24 functional
- 19 Nov 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 116 → 145 ▼ functional
- Server version: 1.5.0 → 1.7.5 functional
- “compare_forecasts” reworded the description of “topic” cosmetic
- “search_claims” reworded the description of “query” cosmetic
- “track_record” reworded the description of “institution” cosmetic
- “track_record” reworded the description of “speaker” cosmetic
- 18 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_claims” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.2.0 → 1.5.0 functional
- New tool “compare_forecasts” functional
- New tool “list_due” functional
- New tool “track_record” functional
- “search_claims” reworded the description of “area” cosmetic
- 17 Nov 26 57
First indexed and scored.
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 21 Nov 2026 · Probed https://mcp.signetex.ch/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=signetex.ch | CN=WE1,O=Google Trust Services,C=US | 13 Nov 2026 | 11 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 47ba4505a9ca8f6b13d76a027c1f0fa3 |
| SANs: signetex.ch, mcp.signetex.ch, *.mcp.signetex.ch | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.signetex.ch. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ch. | DS published | 58745 | 13 | Verified |
| signetex.ch. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.signetex.ch/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.signetex.ch/mcp | Inconclusive | 405 |
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 →
compare_forecasts ~113
Show forecasts by different sources on one topic, drawn from public and MCP-only entries. Signetex grades evidence and issues no true/false verdicts.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Optional register area filter. |
| limit | integer | – | Maximum number of forecasts to return (default 20, max 50). |
| topic | string | yes | Topic or free-text query, for example inflation, GDP, AGI, deliveries, or several words such as "SNB inflation" (matched word by word, ranked). |
No output schema declared.
No examples provided.
due_forecasts ~87
List register forecasts whose due date falls within the given number of days (including those already due and still open). Futures essays are not included. Signetex grades evidence and issues no true/false verdicts.
| Name | Type | Req | Description |
|---|---|---|---|
| within_days | integer | – | Include forecasts due on or before today plus this many days (default 365, max 3650). Already-due open forecasts are included. |
No output schema declared.
No examples provided.
evidence_grades ~35
Return the published E0–E4 evidence-grade definitions from the Signetex method page, not a true/false scale.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_entry ~90
Get one register entry by its stable ID (for example SGX-AI-000031 or SGX-HU-000016), including sources, counter-evidence, grade rationale and history, with the canonical page URL. Signetex grades evidence and issues no true/false verdicts.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Stable Signetex entry ID, for example SGX-AI-000031. |
No output schema declared.
No examples provided.
latest_proof ~30
Return the latest published OpenTimestamps proof snapshot of the register (root hash, status, manifest URLs).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_due ~93
List forecasts whose due date falls in the inclusive window from…to (YYYY-MM-DD). Returns public and MCP-only entries, including already closed ones in that window. Signetex grades evidence and issues no true/false verdicts.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Start of the due-date window, inclusive, YYYY-MM-DD. |
| to | string | yes | End of the due-date window, inclusive, YYYY-MM-DD. |
No output schema declared.
No examples provided.
register_stats ~93
Headline counts for the published register: totals, areas, grades, forecast outcomes. A hit rate is only included once at least 30 forecasts have closed, as on the public site. Only forecasts whose criterion was fixed before the outcome count; back-captured entries with criterion_timing retrospective are reported separately as retrospective_accuracy, never as a hit rate. Signetex grades evidence and issues no true/false verdicts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_claims ~332
Search the Signetex register of verified claims (public pages and MCP-only entries) across machine-intelligence, human-impact, politics-economy and corporate-promises. Internal or paywalled corporate entries are not included, nor are the speculative Futures essays. Returns matching entries with canonical URLs. Signetex grades evidence and issues no true/false verdicts.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Register area: machine-intelligence (the AI itself), human-impact (AI and humans) politics-economy (forecasts by governments, central banks, politicians and economists) or corporate-promises (company… |
| grade | string | – | Evidence grade: E0, E1, E2, E3 or E4. |
| kind | string | – | Entry kind: finding, forecast or possibility (also accepts the stored values befund, prognose, moeglichkeit). |
| limit | integer | – | Maximum number of results to return (default 10, max 50). |
| outcome | string | – | Forecast outcome: open, met, partial, not_met, unclear (German stored values also accepted). |
| query | string | – | Free-text search over English and German claim text, verbatim quote, speaker, organisation, company, ticker, topic and ID. Several words are matched individually (case and accents ignored) and result… |
No output schema declared.
No examples provided.
track_record ~187
Return the closed-forecast record of a speaker or institution: counts of met, partial and not met, and a hit rate per register area. Hit rates count only forecasts whose criterion was fixed before the outcome; retrospective (back-captured) entries are counted separately under retrospective. Uses public and MCP-only entries, never internal ones. Signetex grades evidence and issues no true/false verdicts.
| Name | Type | Req | Description |
|---|---|---|---|
| institution | string | – | Name of the institution or organisation to match (case- and accent-insensitive, partial match allowed; common abbreviations understood, for example SNB, Fed/FOMC, ECB/EZB, IMF, TTWO, NVDA). Alias: or… |
| speaker | string | – | Name of the person or official speaker to match (case- and accent-insensitive; partial names, surnames and common short forms allowed, for example Altman or Powell). |
No output schema declared.
No examples provided.
How do I install the Signetex MCP server?
Signetex is a hosted endpoint at https://mcp.signetex.ch/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 · mcp.signetex.ch
claude mcp add --transport http ch-signetex-register 'https://mcp.signetex.ch/mcp'
What is the Signetex MCP server?
Signetex is an MCP server listed in the public MCP registry as ch.signetex/register. Public AI claim register: E0-E4 evidence grades, forecast tracking, no verdicts. This page covers its hosted endpoint (https://mcp.signetex.ch/mcp).
Is the Signetex MCP server safe to use?
Signetex scores 58 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 Signetex MCP server expose?
Signetex exposes 9 tools: search_claims, get_entry, due_forecasts, register_stats, evidence_grades, and 4 more. Their descriptions and schemas cost roughly 1,060 tokens of context every time the server is loaded.
Does the Signetex MCP server require authentication?
No. We connected to Signetex without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Signetex MCP server still maintained?
Signetex is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Signetex MCP server?
VerifyMCP ran 11 checks on Signetex, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Signetex: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.