OutSend
REMOTE · OUTSEND.XYZ
Find local businesses, enrich them with emails and socials, and run lead pipelines from your AI.
Available components
Last scanned (18 hours ago)
Scores higher than 35% of remote servers
Reachable. Last reached 4 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
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 29 Sept 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Authorization: fail → pass ▲ security
- First check of Authorization: pass security
- Capabilities: fail → 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
- 24 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 23 Sept 26 0
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 28 functional
- 11 Sept 26 0
First indexed and scored.
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 4 Nov 2026 · Probed https://outsend.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=outsend.xyz | CN=YE1,O=Let's Encrypt,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5982fd1e59fafe8097475b62f0c8305443d |
| SANs: outsend.xyz | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of outsend.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| outsend.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://outsend.xyz/.well-known/oauth-protected-resource/mcp", scope="mcp"
Bearer resource_metadata="https://outsend.xyz/.well-known/oauth-protected-resource/mcp", scope="mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.hcaptcha.com https://*.hcaptcha.com; style-src 'self' 'unsafe-inline' https://*.hcaptcha.com; img-src 'self' data: https://server.arcgisonline.com https://*.basemaps.cartocdn.com https://fazier.com https://findly.tools https://saasdb.net https://tinylaunch.com https://www.tinylaunch.com https://www.toolpilot.ai https://launchbuff.com https://francesaas.fr https://saasfame.com https://dofollow.tools https://img.turbo0.com https://firsto.co https://productwatch.io https://statics.startupbase.io https://listmysaas.xyz https://cdn.openhunts.com https://smollaunch.com https://www.scrolllaunch.com; font-src 'self'; connect-src 'self' https://*.hcaptcha.com; frame-src https://*.hcaptcha.com https://newassets.hcaptcha.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'; report-uri /api/csp-report |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=(), usb=(), magnetometer=(), gyroscope=() |
| www-authenticate | Bearer resource_metadata="https://outsend.xyz/.well-known/oauth-protected-resource/mcp", scope="mcp" |
Protected resource metadata
| Document | https://outsend.xyz/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://outsend.xyz/mcp |
| Authorisation server | https://outsend.xyz |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://outsend.xyz/mcp | Auth required | 401 | |
| http (plaintext) | http://outsend.xyz/mcp | HTTPS enforced | 308 | https://outsend.xyz/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 →
create_enrichment_job ~83
Enrich the results of a finished job (async): find emails, scrape reviews, detect social networks, verify emails, tech stack, etc. Returns the new job id.
| Name | Type | Req | Description |
|---|---|---|---|
| email_mode | string | – | Only for enrichment=emails. Default normal. |
| enrichment | string | yes | – |
| source_job_id | string | yes | A job with status=done |
No output schema declared.
No examples provided.
create_pipeline ~216
Create AND start a multi-step pipeline (e.g. scrap → emails → verify_emails). Keep chains LINEAR (each block feeds the next). Edges use the keys "from" and "to" — NOT source/target. Call get_pipeline_schema first for the valid block types and their config fields. Returns pipeline id + initial job ids. Example definition: {"nodes": [{"id": "n1", "type": "scrap", "config": {"queries": ["plombier"], "zones": ["Lyon"], "stop_at": 500}}, {"id": "n2", "type": "emails", "config": {}}], "edges": [{"id": "e1", "from": "n1", "to": "n2"}]}
| Name | Type | Req | Description |
|---|---|---|---|
| definition | object | yes | {nodes: [{id, type, config}], edges: [{id, from, to}]} — edge keys are "from"/"to", not source/target |
| name | string | – | – |
No output schema declared.
No examples provided.
create_scrap_job ~109
Launch a Google Maps extraction (async). Returns the job id immediately; poll get_job until status=done, then use get_job_results. When the user wants ~N results, set stop_at.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO3, default FRA |
| extra_columns | array | – | – |
| max_per_phone | integer | – | – |
| queries | array | yes | – |
| scrap_mode | string | – | – |
| stop_at | integer | – | – |
| zones | array | yes | – |
No output schema declared.
No examples provided.
create_veille ~73
Turn a finished job or pipeline into recurring monitoring: outsend re-runs it every N days and computes the diff (new / removed / modified places).
| Name | Type | Req | Description |
|---|---|---|---|
| frequency_days | integer | yes | – |
| name | string | yes | – |
| source_job_id | string | – | – |
| source_pipeline_id | string | – | – |
No output schema declared.
No examples provided.
estimate_scrap ~126
Estimate the cost (EF) and volume of a Google Maps extraction WITHOUT launching it. Always estimate before creating a large job. 1 EF = a full-France scrape for one query type.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO3 country code, default FRA |
| queries | array | yes | Business types, e.g. ['plombier', 'electricien'] |
| scrap_mode | string | – | – |
| stop_at | integer | – | Stop after N unique places (recommended when the user gives a number) |
| zones | array | yes | Cities, departments, regions or 'France' |
No output schema declared.
No examples provided.
get_events ~55
Account event feed (job.completed, pipeline.completed, veille.run_completed…). Cursor-based: pass back last_id as since_id.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| since_id | integer | – | – |
| types | array | – | – |
No output schema declared.
No examples provided.
get_job ~26
Status, counters and download URL of a job.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
get_job_results ~74
Preview of a finished job's rows (max 50 per call, paginate with offset) + total count + CSV download URL. Never dump thousands of rows into the conversation: show a sample, give the link.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
get_pipeline_schema ~33
Machine contract for building pipelines: valid block types, per-block config schema, and chaining rules. Use before create_pipeline.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_jobs ~24
The account's recent jobs, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_modules ~41
Catalog of outsend data modules: what each one needs and produces. Call this first to know what is possible. Modules listed as coming_soon cannot be launched.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_pipelines ~16
The account's pipelines with status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_veilles ~16
The account's recurring monitors.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the OutSend MCP server?
OutSend is a hosted endpoint at https://outsend.xyz/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 · outsend.xyz
claude mcp add --transport http xyz-outsend-outsend 'https://outsend.xyz/mcp'
What is the OutSend MCP server?
OutSend is an MCP server listed in the public MCP registry as xyz.outsend/outsend. Find local businesses, enrich them with emails and socials, and run lead pipelines from your AI. This page covers its hosted endpoint (https://outsend.xyz/mcp).
Is the OutSend MCP server safe to use?
OutSend scores 39 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 OutSend MCP server expose?
OutSend exposes 13 tools: list_modules, get_pipeline_schema, estimate_scrap, create_scrap_job, create_enrichment_job, and 8 more. Their descriptions and schemas cost roughly 892 tokens of context every time the server is loaded.
Does the OutSend MCP server require authentication?
Yes. OutSend 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 OutSend MCP server still maintained?
OutSend is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.