Saber

REMOTE · MCP.SABER.APP · SCANNED AUG 3

Sales intelligence — research companies, qualify prospects, and find contacts.

Available components

+8 this week 83 83 Trust /100

Trust breakdown (6 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 →

Endpoint Security97

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
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
The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability78

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 3813 tokens (~44/item across 85 items; 84 tools + 1 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 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
99% of tool parameters carry a description.Partial

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.saber.app

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http app-saber-mcp-saber https://mcp.saber.app/mcp

# ~/.codex/config.toml

[mcp_servers.app-saber-mcp-saber]
url = "https://mcp.saber.app/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-saber-mcp-saber": {
      "type": "remote",
      "url": "https://mcp.saber.app/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add app-saber-mcp-saber --url https://mcp.saber.app/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  app-saber-mcp-saber:
    url: "https://mcp.saber.app/mcp"

// mcp.json

{
  "mcpServers": {
    "app-saber-mcp-saber": {
      "type": "http",
      "url": "https://mcp.saber.app/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.

2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1

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

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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
26 Jul 26 75

First indexed and scored.

Show 5 earlier entries Hide earlier entries

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 3 Aug 2026 · Probed https://mcp.saber.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=mcp.saber.app	CN=WR3,O=Google Trust Services,C=US	10 Jun 2026	8 Sept 2026	RSA 2048	SHA256-RSA	c2f24e6c45d550411219b67bf1b39312
SANs: mcp.saber.app
CN=WR3,O=Google Trust Services,C=US (CA)	CN=GTS Root R1,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	RSA 2048	SHA256-RSA	7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	19 Jun 2020	28 Jan 2028	RSA 4096	SHA256-RSA	77bd0d6cdb36f91aea210fc4f058d30d

DNSSEC secure

Validation of mcp.saber.app. — Secure

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
app.	present	23684	8	Verified
saber.app.	present	39806	13	Verified
mcp.saber.app.				Verified address RRset verified with the apex keys

Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result	Enforced and verified
Enforced	On tool calls
HTTP status	200

WWW-Authenticate challenge Bearer realm="Saber MCP", resource_metadata="https://mcp.saber.app/.well-known/oauth-protected-resource"

Bearer realm="Saber MCP", resource_metadata="https://mcp.saber.app/.well-known/oauth-protected-resource"

Header	Value
strict-transport-security	max-age=31536000; includeSubDomains
x-content-type-options	nosniff
x-frame-options	DENY
referrer-policy	strict-origin-when-cross-origin
permissions-policy	geolocation=(), microphone=()

Protected resource metadata

Document	https://mcp.saber.app/.well-known/oauth-protected-resource
Retrieved	Yes
Resource	https://mcp.saber.app
Authorisation server	https://mcp.saber.app

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://mcp.saber.app/mcp	Verified	200
http (plaintext)	http://mcp.saber.app/mcp	HTTPS enforced

MCP tools — 84 exposed · ~3,785 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.

Tool Tokens

scoring-profile-delete ~26

Delete a scoring profile

Input Output Examples

Name	Type	Req	Description
profileId	string	yes	Scoring profile UUID

No output schema declared.

No examples provided.

scoring-profile-get ~26

Get a scoring profile

Input Output Examples

Name	Type	Req	Description
profileId	string	yes	Scoring profile UUID

No output schema declared.

No examples provided.

scoring-profile-list ~13

List scoring profiles

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scoring-profile-update ~37

Update a scoring profile

Input Output Examples

Name	Type	Req	Description
__requestBody	object	yes	Request body
profileId	string	yes	Scoring profile UUID

No output schema declared.

No examples provided.

scoring-rule-delete ~38

Delete a scoring rule

Input Output Examples

Name	Type	Req	Description
profileId	string	yes	Scoring profile UUID
ruleId	string	yes	Scoring rule UUID

No output schema declared.

No examples provided.

scoring-rule-list ~28

List scoring rules for a profile

Input Output Examples

Name	Type	Req	Description
profileId	string	yes	Scoring profile UUID

No output schema declared.

No examples provided.

scoring-rule-upsert ~39

Upsert a scoring rule

Input Output Examples

Name	Type	Req	Description
__requestBody	object	yes	Request body
profileId	string	yes	Scoring profile UUID

No output schema declared.

No examples provided.

scoring-scores-get ~55

Read scores for one or more objects

Input Output Examples

Name	Type	Req	Description
objectId	array	yes	Repeatable. For `company` use the domain; for `contact` use the LinkedIn profile URL.
objectType	string	yes	—

No output schema declared.

No examples provided.

signal_subscriptions-create ~35

Schedule recurring signal execution for a template, domain, or list target.

Input Output Examples

Name	Type	Req	Description
__requestBody	object	yes	Request body

No output schema declared.

No examples provided.

signal_subscriptions-get ~31

Get a signal subscription by ID

Input Output Examples

Name	Type	Req	Description
subscriptionId	string	yes	The unique identifier of the subscription

No output schema declared.

No examples provided.

signal_subscriptions-list ~45

List all signal subscriptions for your organization

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Maximum number of subscriptions to return
offset	integer	—	Number of subscriptions to skip for pagination

No output schema declared.

No examples provided.

signal_subscriptions-start ~31

Start a signal subscription

Input Output Examples

Name	Type	Req	Description
subscriptionId	string	yes	The unique identifier of the subscription to start

No output schema declared.

No examples provided.

signal_subscriptions-stop ~31

Stop a signal subscription

Input Output Examples

Name	Type	Req	Description
subscriptionId	string	yes	The unique identifier of the subscription to stop

No output schema declared.

No examples provided.

signal_subscriptions-trigger ~35

Trigger an immediate run of a signal subscription

Input Output Examples

Name	Type	Req	Description
subscriptionId	string	yes	The unique identifier of the subscription to trigger

No output schema declared.

No examples provided.

signal_subscriptions-update ~42

Update a signal subscription

Input Output Examples

Name	Type	Req	Description
__requestBody	object	yes	Request body
subscriptionId	string	yes	The unique identifier of the subscription to update

No output schema declared.

No examples provided.

signal_summaries-generate ~39

Generate an AI summary consolidating insights from all completed company signals for a domain

Input Output Examples

Name	Type	Req	Description
__requestBody	object	yes	Request body

No output schema declared.

No examples provided.

signal_summaries-list ~76

List all AI-generated signal summaries for a domain, ordered by creation date (latest first)

Input Output Examples

Name	Type	Req	Description
domain	string	yes	Filter summaries by company domain (e.g., "acme.com")
limit	integer	—	Maximum number of results per page
offset	integer	—	Number of results to skip for pagination

No output schema declared.

No examples provided.

signal_templates-create ~36

Create a reusable research question template that can be applied to many companies in batch.

Input Output Examples

Name	Type	Req	Description
__requestBody	object	yes	Request body

No output schema declared.

No examples provided.

signal_templates-delete ~43

Soft-delete a signal template so it is no longer active while preserving it for historical tracking.

Input Output Examples

Name	Type	Req	Description
templateId	string	yes	The unique identifier of the template to delete

No output schema declared.

No examples provided.

signal_templates-get ~30

Get a signal template by ID

Input Output Examples

Name	Type	Req	Description
templateId	string	yes	The unique identifier of the template

No output schema declared.

No examples provided.

signal_templates-list ~58

List all signal templates for your organization

Input Output Examples

Name	Type	Req	Description
includeDeleted	boolean	—	Include deleted templates in the response
limit	integer	—	Maximum number of templates to return
offset	integer	—	Number of templates to skip for pagination

No output schema declared.

No examples provided.

signal_templates-update ~59

Update a signal template by creating a new version while preserving the template ID. Omitted fields keep their previous values.

Input Output Examples

Name	Type	Req	Description
__requestBody	object	yes	Request body
templateId	string	yes	The unique identifier of the template to update

No output schema declared.

No examples provided.

signals-firmographics ~54

Return a company's firmographic profile (headcount, size, type, founded, HQ) plus a Saber-derived refined category and sell-to segments, with cited evidence.

Input Output Examples

Name	Type	Req	Description
__requestBody	object	yes	Request body

No output schema declared.

No examples provided.

signals-funding ~46

Research a company's most recent funding round and public/IPO status by domain. Returns a structured funding summary with investors and source URLs.

Input Output Examples

Name	Type	Req	Description
__requestBody	object	yes	Request body

No output schema declared.

No examples provided.

signals-mna ~48

Research a company's recent M&A activity by domain — whether it was acquired or made acquisitions, with counterparty, deal status, and value.

Input Output Examples

Name	Type	Req	Description
__requestBody	object	yes	Request body

No output schema declared.

No examples provided.

signals-open_jobs ~48

Summarise a company's current hiring from public job postings by domain — total openings, example titles, function areas, technologies, and locations.

Input Output Examples

Name	Type	Req	Description
__requestBody	object	yes	Request body

No output schema declared.

No examples provided.

signals-tech ~51

Detect the ERP or CRM system(s) a company uses, or verify a specific technology, by domain — verified with public web evidence, not vendor data alone.

Input Output Examples

Name	Type	Req	Description
__requestBody	object	yes	Request body

No output schema declared.

No examples provided.

subscription_actions-create ~40

Create a subscription action

Input Output Examples

Name	Type	Req	Description
__requestBody	object	yes	Request body
subscriptionId	string	yes	The subscription to add the action to

No output schema declared.

No examples provided.

subscription_actions-delete ~41

Delete a subscription action

Input Output Examples

Name	Type	Req	Description
actionId	string	yes	The action ID to delete
subscriptionId	string	yes	The subscription that owns the action

No output schema declared.

No examples provided.

subscription_actions-get ~41

Get a subscription action by ID

Input Output Examples

Name	Type	Req	Description
actionId	string	yes	The action ID
subscriptionId	string	yes	The subscription that owns the action

No output schema declared.

No examples provided.

subscription_actions-list ~57

List all actions for a subscription

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Maximum number of actions to return
offset	integer	—	Number of actions to skip for pagination
subscriptionId	string	yes	The subscription whose actions to list

No output schema declared.

No examples provided.

subscription_actions-pause ~42

Pause a subscription action

Input Output Examples

Name	Type	Req	Description
actionId	string	yes	The action ID to pause
subscriptionId	string	yes	The subscription that owns the action

No output schema declared.

No examples provided.

subscription_actions-unpause ~44

Unpause a subscription action

Input Output Examples

Name	Type	Req	Description
actionId	string	yes	The action ID to unpause
subscriptionId	string	yes	The subscription that owns the action

No output schema declared.

No examples provided.

subscription_actions-update ~52

Update a subscription action

Input Output Examples

Name	Type	Req	Description
__requestBody	object	yes	Request body
actionId	string	yes	The action ID to update
subscriptionId	string	yes	The subscription that owns the action

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	75
27 Jul	75
28 Jul	76
29 Jul	77
30 Jul	77
31 Jul	82
1 Aug	82
2 Aug	83
3 Aug	83