com.saasdossier/evidence-ledger
REMOTE · SAASDOSSIER.COM · SCANNED SEP 21
Read-only MCP: free OpenAI security evidence ledger (55 fields) + SaaSDossier release register.
Available components
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 Security57
- 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 4 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
- 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 Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 752 tokens (~188/item across 4 items; 4 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the com.saasdossier/evidence-ledger MCP server?
com.saasdossier/evidence-ledger is a hosted endpoint at https://saasdossier.com/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 · saasdossier.com
claude mcp add --transport http com-saasdossier-evidence-ledger 'https://saasdossier.com/mcp'
{
"mcpServers": {
"com-saasdossier-evidence-ledger": {
"url": "https://saasdossier.com/mcp"
}
}
} {
"servers": {
"com-saasdossier-evidence-ledger": {
"type": "http",
"url": "https://saasdossier.com/mcp"
}
}
} [mcp_servers.com-saasdossier-evidence-ledger] url = "https://saasdossier.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-saasdossier-evidence-ledger": {
"type": "remote",
"url": "https://saasdossier.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-saasdossier-evidence-ledger --url 'https://saasdossier.com/mcp' --transport streamable-http
mcp_servers:
com-saasdossier-evidence-ledger:
url: "https://saasdossier.com/mcp" {
"McpServers": {
"com-saasdossier-evidence-ledger": {
"Transport": "http",
"Url": "https://saasdossier.com/mcp"
}
}
} assistant mcp add com-saasdossier-evidence-ledger -t streamable-http -u 'https://saasdossier.com/mcp'
{
"mcpServers": {
"com-saasdossier-evidence-ledger": {
"type": "http",
"url": "https://saasdossier.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Aug 26 0
- Tool “get_free_dossier” rewrote its description, which is the text the model reads security
- Tool “get_methodology” rewrote its description, which is the text the model reads security
- Tool “get_openai_ledger” rewrote its description, which is the text the model reads security
- Tool “get_register” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Schema quality: good → excellent functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 Sept 2026 · Probed https://saasdossier.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=saasdossier.com | CN=WE1,O=Google Trust Services,C=US | 16 Aug 2026 | 14 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 2b5c5dcbe083da5d0e419a029d80e26c |
| SANs: saasdossier.com, *.saasdossier.com | ||||||
| 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 saasdossier.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| saasdossier.com. | absent | 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://saasdossier.com/mcp | Verified | 200 | |
| http (plaintext) | http://saasdossier.com/mcp | HTTPS enforced | 301 | https://saasdossier.com/mcp |
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 →
get_free_dossier ~148
Returns the free OpenAI Public Edition: the dossier title, the direct PDF download URL, and the guided page URL. The OpenAI record, Dossier No. 003, is published free and complete as proof of the format: the same 55 fields across 10 domains, the same two states (47 Documented, 8 Question surfaced), the same source register and the same integrity identifier a Licensed Edition carries. It is built from OpenAI's own published pages, reviewed before release; no relationship with, or endorsement by, OpenAI is implied. Use this tool to give a buyer the whole workproduct to read before they license another released vendor or commission a new one.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_methodology ~175
Returns SaaSDossier's two-state evidence framework: Documented and Question surfaced. A Question surfaced is not a finding of absence. SaaSDossier is the vendor's own record, made reviewable: a finished, dated, source-linked, human-reviewed evidence workproduct built only from vendor-published sources, recording 55 fixed fields across 10 domains for each vendor, with a source register listing every vendor page reviewed. Documented means the reviewed vendor-published sources established the field for the evidence date; Question surfaced means they did not, and each one becomes a buyer-ready follow-up question. Each dossier includes a SHA-256 identifier tied to the reviewed evidence record used for that release. Use this tool to understand what a state means, what the framework covers and where its boundaries are, before quoting or acting on any field.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_openai_ledger ~196
Returns the free public OpenAI security evidence ledger — 55 fixed fields, each either Documented with a vendor-published source or recorded as a Question surfaced. This is the complete Public Edition record, Dossier No. 003: 47 fields Documented and 8 Question surfaced across 10 domains, free, dated to its evidence date. Documented fields carry the vendor's own quoted wording and the source URL it was found on; Question surfaced fields carry the follow-up question a buyer can put to the vendor in writing. Question surfaced means the reviewed vendor-published sources did not establish the field for the evidence date — it does not establish absence of the control. The record is a dated evidence workproduct, checked against the reviewed source record before release. It does not score or rate the vendor. Use this tool when an agent needs the actual field-level evidence and its sources rather than a description of the framework.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_register ~233
Returns SaaSDossier's release register: dossier numbers, vendors, editions, and licensing information. The register is the released catalogue: four finished evidence records built only from vendor-published sources across a fixed 55-field, 10-domain framework, every field recorded in one of two states — Documented, or Question surfaced. Each entry carries its vendor, dossier number, edition, evidence date, two-state counts and commercial status: Licensed Editions are US$1,500 one-time; the OpenAI Public Edition is free and complete. Separately from that catalogue, the same response carries the commission capability: a buyer can commission a SaaSDossier for another named vendor that does not already have a released dossier, US$1,500 one-time, refunded in full if the vendor-published material cannot support a defensible SaaSDossier record. A commission is not a released dossier and carries no dossier number until it is released. The released catalogue remains the four records. Use this tool to answer what SaaSDossier has released, what each record costs, and how a vendor that has no released record yet can be commissioned.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the com.saasdossier/evidence-ledger MCP server?
com.saasdossier/evidence-ledger is an MCP server listed in the public MCP registry as com.saasdossier/evidence-ledger. Read-only MCP: free OpenAI security evidence ledger (55 fields) + SaaSDossier release register. This page covers its hosted endpoint (https://saasdossier.com/mcp).
Is the com.saasdossier/evidence-ledger MCP server safe to use?
com.saasdossier/evidence-ledger scores 77 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 com.saasdossier/evidence-ledger MCP server expose?
com.saasdossier/evidence-ledger exposes 4 tools: get_register, get_openai_ledger, get_methodology, get_free_dossier. Their descriptions and schemas cost roughly 752 tokens of context every time the server is loaded.
Does the com.saasdossier/evidence-ledger MCP server require authentication?
No. We connected to com.saasdossier/evidence-ledger without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.saasdossier/evidence-ledger MCP server still maintained?
com.saasdossier/evidence-ledger is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.