Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "evidence-ledger": {
      "type": "http",
      "url": "https://saasdossier.com/mcp"
    }
  }
}

claude mcp add --transport http evidence-ledger https://saasdossier.com/mcp

[mcp_servers.evidence-ledger]
url = "https://saasdossier.com/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "evidence-ledger": {
      "type": "remote",
      "url": "https://saasdossier.com/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "evidence-ledger": {
      "type": "http",
      "url": "https://saasdossier.com/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=evidence-ledger&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vc2Fhc2Rvc3NpZXIuY29tL21jcCJ9"
}

{
  "servers": {
    "evidence-ledger": {
      "type": "http",
      "url": "https://saasdossier.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "evidence-ledger": {
      "httpUrl": "https://saasdossier.com/mcp"
    }
  }
}

extensions:
  "evidence-ledger":
    enabled: true
    name: "evidence-ledger"
    type: streamable_http
    uri: "https://saasdossier.com/mcp"
    timeout: 300

Quality 76 / 100good

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene64 · weight 30

pass
tools.descriptionsevery tool has a description
warn
tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
pass
tools.schemasevery tool has an object input schema
fail
tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_methodology (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_free_dossier (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_register (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
pass
tools.token_costabout 978 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

4 tools, about 978 tokens to load them all · tool set 5498f3fafcf0 · checked 2026-10-19 16:20 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 75 / 100

no-repository

provenance55

liveness98

freshness65

hygiene80

+dns-namespace +website +reachable +uptime-95% ~updated-95d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://saasdossier.com/mcp` streamable-http	none	yes	95%	203 ms	2025-06-18	2026-10-19

Tools (4)

`get_free_dossier`	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.
`get_methodology`	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.
`get_openai_ledger`	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.
`get_register`	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.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "com.saasdossier/evidence-ledger",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-09-29/server.schema.json",
  "remotes": [
    {
      "url": "https://saasdossier.com/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.1.0",
  "websiteUrl": "https://saasdossier.com",
  "description": "Read-only MCP: free OpenAI security evidence ledger (55 fields) + SaaSDossier release register."
}