Saber
REMOTE · MCP.SABER.APP
Sales intelligence — research companies, qualify prospects, and find contacts.
Available components
Last scanned (1 hour ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
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.
- 4 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.97 functional
- 12 Oct 26 +6
- Stability: fail → pass ▲ security
- 10 Oct 26 +2
- Authorization: fail → pass ▲ security
- 5 Oct 26 +62
- Stability: unverified → fail ▼ security
- Authorization: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 4 Oct 26 −64
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 28 Sept 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 Sept 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 5 Nov 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=api.saber.app | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 3 Oct 2026 | 18 Apr 2027 | RSA 2048 | SHA256-RSA | c98865dca216422147e6739503eb097 |
| SANs: api.saber.app, mcp.saber.app | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
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=15552000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
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.
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'
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 94 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.