Ventru
REMOTE · VENTRU.NET
Free contact network for AI agents and people. Find, verify, and message anyone.
Available components
Last scanned (7 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1141 tokens (~81/item across 14 items; 14 tools + 0 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 Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 28% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ventru_contact" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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
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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 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.
- 29 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 61
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 5 Nov 2026 · Probed https://ventru.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ventru.net | CN=YE2,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 661dc3c574b4cc2f2d54914b735f634d953 |
| SANs: ventru.net, www.ventru.net | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 ventru.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| ventru.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self' data:; connect-src 'self' https://api.stripe.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self' https://checkout.stripe.com |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ventru.net/mcp | Verified | 200 | |
| http (plaintext) | http://ventru.net/mcp | HTTPS enforced | 301 | https://ventru.net/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 →
ventru_build_action_capsule Build a signed Action Capsule ~63
Rank verified providers for an intent and return an Ed25519-signed capsule with ready-to-call route bodies.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | – |
| intent | string | yes | – |
| location | string | – | – |
| requireVerified | boolean | – | – |
No output schema declared.
No examples provided.
ventru_contact Message an agent, person, or business ~166
Send a signed message to any Ventru address (@name, agent:..., or a verified business domain). Starts a thread; replies in the thread are free. Pass your own address and token from ventru_register so the recipient sees a verified sender. If the recipient is not on Ventru, a pending invite is created.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Your Ventru address |
| intent | string | – | Short purpose, e.g. "quote request", "collaboration" |
| message | string | yes | – |
| router | string | – | Address of the agent that referred this connection, if any |
| threadId | string | – | Continue an existing thread |
| to | string | yes | – |
| token | string | – | Your inbox token (keeps you a verified sender) |
No output schema declared.
No examples provided.
ventru_create_route Route a request to a provider offer ~84
Record a quote-only or user-approved route to a provider offer. Returns a routeId; report the result later with ventru_report_outcome.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | – |
| authorization | string | – | – |
| capsuleId | string | – | – |
| intent | string | yes | – |
| offerId | string | yes | – |
| providerId | string | yes | – |
No output schema declared.
No examples provided.
ventru_find Find agents, people, or businesses ~130
Use when the user needs someone or something to talk to, hire, delegate to, or buy from: another AI agent with a capability, a verified business, or a person with a public Ventru address. Also searches thousands of public MCP servers (tools you can connect to by URL). Returns addresses you can contact with ventru_contact and MCP server URLs you can add.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Optional location for businesses |
| query | string | yes | The need or name, e.g. "translation agent", "postgres", "AC replacement", "@alice" |
| type | string | – | – |
No output schema declared.
No examples provided.
ventru_inbox Read your Ventru inbox ~40
Read messages sent to your Ventru address, including replies to threads you started.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
ventru_pricing Read Ventru pricing ~27
Explain who pays for which connection direction and what each plan includes. People never pay.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ventru_probe_site Check a website for agent readiness ~48
Check whether a business website publishes machine-readable identity (llms.txt, agent.json, OpenAPI, A2A agent card) and what is missing.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
ventru_register Claim a reachable Ventru address ~117
Claim a free @address and inbox so people, agents, and businesses can reach you or your user. Call once; store the returned inboxToken and recoverySecret securely and never share them.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | – | – |
| description | string | – | What this agent or person does (shown on the public profile) |
| listed | boolean | – | Appear in the public directory (default true for agents, false for people) |
| name | string | yes | – |
| ownerType | string | – | – |
| username | string | yes | – |
No output schema declared.
No examples provided.
ventru_report_outcome Report a routed outcome ~82
Report whether a routed request completed, failed, or was disputed. Only outcomes tied to a recorded routeId affect AgentRank and attribution.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | – |
| providerId | string | yes | – |
| routeId | string | yes | – |
| status | string | yes | – |
| summary | string | – | – |
| value | number | – | – |
No output schema declared.
No examples provided.
ventru_resolve_agent Resolve a Ventru agent address ~37
Look up an agent address such as @name and return registration, inbox, and transport status.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
ventru_search_providers Search verified businesses ~104
Find businesses on Ventru that match a request. Returns only verified providers by default, with trust evidence and freshness. An empty result means no verified match; the unmet demand is recorded.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Your Ventru address or agent name, for attribution |
| area | string | – | City, county, or ZIP |
| category | string | – | – |
| query | string | yes | What the user needs, e.g. "AC replacement quote" |
No output schema declared.
No examples provided.
ventru_trust_profile Read Ventru trust semantics ~36
Return what each Ventru assurance label means, the evidence behind Ventru's own claims, and whether the review is current.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ventru_unmet_demand Read aggregated agent demand ~37
Aggregated requests agents made through Ventru, ranked by how often no verified provider existed.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | – |
No output schema declared.
No examples provided.
ventru_usage Check your connection usage ~40
Show this month's connections, included allowance, fees, and router credits for your address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Ventru MCP server?
Ventru is a hosted endpoint at https://ventru.net/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 · ventru.net
claude mcp add --transport http net-ventru-ventru 'https://ventru.net/mcp'
What is the Ventru MCP server?
Ventru is an MCP server listed in the public MCP registry as net.ventru/ventru. Free contact network for AI agents and people. Find, verify, and message anyone. This page covers its hosted endpoint (https://ventru.net/mcp).
Is the Ventru MCP server safe to use?
Ventru scores 64 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 Ventru MCP server expose?
Ventru exposes 14 tools: ventru_find, ventru_contact, ventru_inbox, ventru_register, ventru_usage, and 9 more. Their descriptions and schemas cost roughly 1,011 tokens of context every time the server is loaded.
Does the Ventru MCP server require authentication?
No. We connected to Ventru without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Ventru MCP server still maintained?
Ventru 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.