Saber
REMOTE · MCP.SABER.APP · SCANNED SEP 20
Sales intelligence — research companies, qualify prospects, and find contacts.
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 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 Usability76
- 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 2811 tokens (~36/item across 77 items; 76 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability check failed: schema churn in the 30 days we've observed: 47 tool removals, 0 breaking changes, 0 auth/transport breaks, 4 additions. See how to fix → Fail
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 66% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 77 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Saber MCP server?
Saber is a hosted endpoint at https://mcp.saber.app/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.saber.app
claude mcp add --transport http app-saber-mcp-saber 'https://mcp.saber.app/mcp'
{
"mcpServers": {
"app-saber-mcp-saber": {
"url": "https://mcp.saber.app/mcp"
}
}
} {
"servers": {
"app-saber-mcp-saber": {
"type": "http",
"url": "https://mcp.saber.app/mcp"
}
}
} [mcp_servers.app-saber-mcp-saber] url = "https://mcp.saber.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-saber-mcp-saber": {
"type": "remote",
"url": "https://mcp.saber.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-saber-mcp-saber --url 'https://mcp.saber.app/mcp' --transport streamable-http
mcp_servers:
app-saber-mcp-saber:
url: "https://mcp.saber.app/mcp" {
"McpServers": {
"app-saber-mcp-saber": {
"Transport": "http",
"Url": "https://mcp.saber.app/mcp"
}
}
} assistant mcp add app-saber-mcp-saber -t streamable-http -u 'https://mcp.saber.app/mcp'
{
"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.
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.
- 16 Sept 26 0
- Schema quality: fair → good functional
- New tool “companies-resolve-domain” functional
- 13 Sept 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 44 to 61.
- 12 Sept 26 −8
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “company_signals-create” was removed ▼ security
- Tool “company_signals-create_batch” was removed ▼ security
- Tool “company_signals-get” was removed ▼ security
- Tool “company_signals-list” was removed ▼ security
- Tool “company_signals-subscription_logs” was removed ▼ security
- Tool “contacts-create_signal” was removed ▼ security
- Tool “contacts-get_signal” was removed ▼ security
- Tool “contacts-list_signals” was removed ▼ security
- Tool “findEmail” was removed ▼ security
- Tool “findEmailBatchGet” was removed ▼ security
- Tool “findEmailBatchSubmit” was removed ▼ security
- Tool “getContactResearchByExternalID” was removed ▼ security
- Tool “market_signals-create_subscription” was removed ▼ security
- Tool “market_signals-delete_subscription” was removed ▼ security
- Tool “market_signals-get_subscription” was removed ▼ security
- Tool “market_signals-list_signals” was removed ▼ security
- Tool “market_signals-list_subscriptions” was removed ▼ security
- Tool “market_signals-pause_subscription” was removed ▼ security
- Tool “market_signals-resume_subscription” was removed ▼ security
- Tool “market_signals-trigger_subscription” was removed ▼ security
- Tool “market_signals-update_subscription” was removed ▼ security
- Tool “signal_subscriptions-create” was removed ▼ security
- Tool “signal_subscriptions-get” was removed ▼ security
- Tool “signal_subscriptions-list” was removed ▼ security
- Tool “signal_subscriptions-start” was removed ▼ security
- Tool “signal_subscriptions-stop” was removed ▼ security
- Tool “signal_subscriptions-trigger” was removed ▼ security
- Tool “signal_subscriptions-update” was removed ▼ security
- Tool “signal_summaries-generate” was removed ▼ security
- Tool “signal_summaries-list” was removed ▼ security
- Tool “signal_templates-create” was removed ▼ security
- Tool “signal_templates-delete” was removed ▼ security
- Tool “signal_templates-get” was removed ▼ security
- Tool “signal_templates-list” was removed ▼ security
- Tool “signal_templates-update” was removed ▼ security
- Tool “signals-firmographics” was removed ▼ security
- Tool “signals-funding” was removed ▼ security
- Tool “signals-mna” was removed ▼ security
- Tool “signals-open_jobs” was removed ▼ security
- Tool “signals-tech” was removed ▼ security
- Tool “subscription_actions-create” was removed ▼ security
- Tool “subscription_actions-delete” was removed ▼ security
- Tool “subscription_actions-get” was removed ▼ security
- Tool “subscription_actions-list” was removed ▼ security
- Tool “subscription_actions-pause” was removed ▼ security
- Tool “subscription_actions-unpause” was removed ▼ security
- Tool “subscription_actions-update” was removed ▼ security
- Tool “companies-enrich_custom_batch” rewrote its description, which is the text the model reads security
- Tool “company_lists-create” rewrote its description, which is the text the model reads security
- Tool “company_lists-export” rewrote its description, which is the text the model reads security
- Tool coverage: 80% → 65% ▼ functional
- Schema quality: 40 → 36 ▲ functional
- Schema quality: good → fair functional
- New tool “contacts-enrich_work_email_batch” functional
- New tool “contacts-enrich_work_email_batch_get” functional
- New tool “contacts-get_research_by_external_id” functional
- 29 Aug 26 0
- Tool “contacts-search” rewrote its description, which is the text the model reads security
- 26 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
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Aug 26 0
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 0.1.0 → 1.0.0 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 20 Sept 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 | 5 Aug 2026 | 3 Nov 2026 | RSA 2048 | SHA256-RSA | d48ee84f5cd07d7f0a4d4c4d7a89eab6 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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 →
monitors-list ~39
List monitors
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| target | string | – | – |
No output schema declared.
No examples provided.
monitors-list_actions ~21
List monitor actions
| Name | Type | Req | Description |
|---|---|---|---|
| monitorId | string | yes | – |
No output schema declared.
No examples provided.
monitors-list_signals ~38
List a monitor's signals
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| monitorId | string | yes | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
monitors-pause ~21
Pause a monitor
| Name | Type | Req | Description |
|---|---|---|---|
| monitorId | string | yes | – |
No output schema declared.
No examples provided.
monitors-pause_action ~31
Pause a monitor action
| Name | Type | Req | Description |
|---|---|---|---|
| actionId | string | yes | – |
| monitorId | string | yes | – |
No output schema declared.
No examples provided.
monitors-resume ~21
Resume a monitor
| Name | Type | Req | Description |
|---|---|---|---|
| monitorId | string | yes | – |
No output schema declared.
No examples provided.
monitors-resume_action ~31
Resume a monitor action
| Name | Type | Req | Description |
|---|---|---|---|
| actionId | string | yes | – |
| monitorId | string | yes | – |
No output schema declared.
No examples provided.
monitors-trigger ~21
Trigger a monitor run
| Name | Type | Req | Description |
|---|---|---|---|
| monitorId | string | yes | – |
No output schema declared.
No examples provided.
monitors-update ~31
Update a monitor
| Name | Type | Req | Description |
|---|---|---|---|
| __requestBody | object | yes | Request body |
| monitorId | string | yes | – |
No output schema declared.
No examples provided.
monitors-update_action ~41
Update a monitor action
| Name | Type | Req | Description |
|---|---|---|---|
| __requestBody | object | yes | Request body |
| actionId | string | yes | – |
| monitorId | string | yes | – |
No output schema declared.
No examples provided.
organisation-get ~13
Get your organisation profile
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
organisation-update ~24
Update your organisation profile
| Name | Type | Req | Description |
|---|---|---|---|
| __requestBody | object | yes | Request body |
No output schema declared.
No examples provided.
scoring-assignment-bulk-create ~32
Assign a profile to many objects at once
| Name | Type | Req | Description |
|---|---|---|---|
| __requestBody | object | yes | Request body |
No output schema declared.
No examples provided.
scoring-assignment-create ~29
Assign a profile to a single object
| Name | Type | Req | Description |
|---|---|---|---|
| __requestBody | object | yes | Request body |
No output schema declared.
No examples provided.
scoring-assignment-delete ~26
Remove a profile assignment
| Name | Type | Req | Description |
|---|---|---|---|
| assignmentId | string | yes | Profile assignment UUID |
No output schema declared.
No examples provided.
scoring-assignment-list ~68
List profile assignments for an object
| Name | Type | Req | Description |
|---|---|---|---|
| objectId | string | yes | For `company` use the domain (e.g. `acme.com`); for `contact` use the LinkedIn profile URL |
| objectType | string | yes | Object type (`company` or `contact`) |
No output schema declared.
No examples provided.
scoring-compute ~25
Trigger score recomputation
| Name | Type | Req | Description |
|---|---|---|---|
| __requestBody | object | yes | Request body |
No output schema declared.
No examples provided.
scoring-profile-create ~25
Create a scoring profile
| Name | Type | Req | Description |
|---|---|---|---|
| __requestBody | object | yes | Request body |
No output schema declared.
No examples provided.
scoring-profile-delete ~26
Delete a scoring profile
| 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
| 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 schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scoring-profile-update ~37
Update a scoring profile
| 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
| 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
| 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
| 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
| 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.
What is the Saber MCP server?
Saber is an MCP server listed in the public MCP registry as app.saber.mcp/saber. Sales intelligence, research companies, qualify prospects, and find contacts. This page covers its hosted endpoint (https://mcp.saber.app/mcp).
Is the Saber MCP server safe to use?
Saber scores 88 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 Saber MCP server expose?
Saber exposes 76 tools: companies-enrich_custom, companies-enrich_custom_batch, companies-enrich_firmographics, companies-enrich_funding, companies-enrich_mna, and 71 more. Their descriptions and schemas cost roughly 2,783 tokens of context every time the server is loaded.
Does the Saber MCP server require authentication?
Yes. Saber asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Saber MCP server still maintained?
Saber is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.