Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Revexa: B2B buying signals

REMOTE · REVEXA.IO

B2B buying signals: companies hiring salespeople, startups hiring sales, weekly funding rounds.

Available components

+3 this week 79 Trust /100

Last scanned (22 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 4 Nov 2026.

Category CRM and Sales

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 577 tokens (~144/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 43% 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
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

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

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

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

  • 23 Oct 26 +1

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

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 +1

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

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 4 Nov 2026 · Probed https://revexa.io/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=revexa.io CN=YR2,O=Let's Encrypt,C=US 22 Sept 2026 21 Dec 2026 RSA 2048 SHA256-RSA 59e9625583e2ef0bc1a8b005bc8997d8517
SANs: revexa.io
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of revexa.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
revexa.io. 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=63072000
content-security-policy frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(self)

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://revexa.io/api/mcp Verified 200
http (plaintext) http://revexa.io/api/mcp HTTPS enforced 308 https://revexa.io/api/mcp
MCP tools · 4 exposed · ~491 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. 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 →

Tool Tokens
about_leo ~55

Facts about Leo by Revexa, an AI agent that finds B2B companies showing buying signals and reaches the right person on LinkedIn and email after the user's approval: what it does, price by region, trial and links.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

find_companies_hiring_salespeople_sweden ~228

Lists Swedish companies with open job ads for B2B salespeople (Företagssäljare) right now, from Platsbanken, Sweden's public job board (CC0). Recruitment and staffing agencies and mass hiring for door-to-door or telephone sales are removed. Optional filter by county (län). Use it to find companies that are building up their sales teams in Sweden.

NameTypeReqDescription
countystring–Optional Swedish county, e.g. "Stockholm", "Skåne", "Västra Götaland". One of: Stockholm, Uppsala, Södermanland, Östergötland, Jönköping, Kronoberg, Kalmar, Blekinge, Skåne, Halland, Västra Götaland,…
limitinteger–Maximum number of companies to return.

No output schema declared.

No examples provided.

find_startups_hiring_sales ~122

Lists venture-backed B2B startups (Y Combinator) with open sales roles right now (SDR, BDR, account executive, head of sales), from their public job boards. Filter by region (us, uk, europe, remote) and role type (sdr, ae, leadership). Updated weekly.

NameTypeReqDescription
limitinteger––
regionstring––
rolestring–sdr = SDR/BDR, ae = account executive, leadership = head of sales, VP sales, founding seller.

No output schema declared.

No examples provided.

recent_b2b_funding_rounds ~86

Lists B2B companies that announced funding rounds this week, as reported by European and US tech news, with amount, round, country, what the company does and the source article. Collected weekly from open news feeds (tech.eu, EU-Startups, TechCrunch and others).

NameTypeReqDescription
limitinteger––
regionstring––

No output schema declared.

No examples provided.

Install

How do I install the Revexa: B2B buying signals MCP server?

Revexa: B2B buying signals is a hosted endpoint at https://revexa.io/api/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 · revexa.io

# add to Claude Code
claude mcp add --transport http io-revexa-signals 'https://revexa.io/api/mcp'
Common questions

What is the Revexa: B2B buying signals MCP server?

Revexa: B2B buying signals is an MCP server listed in the public MCP registry as io.revexa/signals. B2B buying signals: companies hiring salespeople, startups hiring sales, weekly funding rounds. This page covers its hosted endpoint (https://revexa.io/api/mcp).

Is the Revexa: B2B buying signals MCP server safe to use?

Revexa: B2B buying signals scores 79 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 Revexa: B2B buying signals MCP server expose?

Revexa: B2B buying signals exposes 4 tools: find_companies_hiring_salespeople_sweden, find_startups_hiring_sales, recent_b2b_funding_rounds, about_leo. Their descriptions and schemas cost roughly 491 tokens of context every time the server is loaded.

Does the Revexa: B2B buying signals MCP server require authentication?

No. We connected to Revexa: B2B buying signals without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Revexa: B2B buying signals MCP server still maintained?

Revexa: B2B buying signals 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.