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.

Trusted Vendors

REMOTE · INDEX.GETPROVEN.COM

Startup software vendors ranked by Proven Score, with public deals. Read-only, no sign-in.

+3 this week 78 Trust /100

Last scanned (17 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 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
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1223 tokens (~152/item across 8 items; 8 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 Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 0
    • Tool “compare_vendors” rewrote its description, which is the text the model reads security
    • Tool “what_startups_use” rewrote its description, which is the text the model reads security
  • 20 Nov 26 +1
    • Tool “get_vendor” rewrote its description, which is the text the model reads security
  • 18 Nov 26 +1
    • Server version: 1.1.0 → 1.1.1 functional
  • 16 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.

  • 14 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.

  • 12 Nov 26 +1

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

  • 10 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 1027 → 1205 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.0.1 → 1.1.0 functional
    • New tool “what_startups_use” functional
  • 9 Nov 26 72

    First indexed and scored.

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 21 Nov 2026 · Probed https://index.getproven.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=getproven.com CN=WE1,O=Google Trust Services,C=US 29 Oct 2026 27 Jan 2027 ECDSA 256 ECDSA-SHA256 d568560bcbf829a50e517a8df6033dcb
SANs: getproven.com, index.getproven.com, *.index.getproven.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of index.getproven.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
getproven.com. No DS 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=2592000; includeSubDomains; preload
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://index.getproven.com/mcp Verified 200
http (plaintext) http://index.getproven.com/mcp HTTPS enforced 301 https://index.getproven.com/mcp
MCP tools · 8 exposed · ~1,087 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
compare_vendors ~70

Side-by-side for two vendors: Proven Scores and score inputs, how many portfolio companies use each (portfolio_usage), founder searches for each (search_demand) and their startup offers.

NameTypeReqDescription
astringyesFirst vendor name or domain.
bstringyesSecond vendor name or domain.

No output schema declared.

No examples provided.

find_vendors ~201

Ranked vendors for a buying need (e.g. "payroll for a 10-person startup in Ireland"): name, profile URL, Proven Score, band, one-line description, and whether a public or network offer exists.

NameTypeReqDescription
categorystring–Optional group name, e.g. "Payroll & HR". Restricts results to that group.
countrystring–Optional: where the buyer company is registered, as a country name or ISO code (e.g. Ireland, US, GB). Leaves out vendors whose own website says they are not available there; vendors with no availabi…
limitinteger–Results to return (default 10).
needstringyesWhat the buyer needs, in plain words.
stagestring–Optional buyer stage, e.g. seed, series a, growth, enterprise. Boosts, does not filter.

No output schema declared.

No examples provided.

get_credits_page ~162

A startup deals page in full: AI credits, cloud credits or developer tool credits for startups (each vendor's offer with its value, who qualifies, access: public deal, VC-backed only via the work-email check or through investor networks, claimed count, claim or check URL, how to claim and FAQs), or startup-deals (every public deal grouped by category, sorted by value). Values, counts and conditions come only from the deals data, claim counts and eligibility; nothing is estimated. Call with no slug to list the pages.

NameTypeReqDescription
slugstring–ai-credits-for-startups, cloud-credits-for-startups, developer-tool-credits-for-startups or startup-deals (or the page URL). Leave empty to list the pages.

No output schema declared.

No examples provided.

get_offers ~142

A vendor's offers: public offers in full; network-tier offers only as "Offer available" with a banded amount; redemption URLs for VC-backed companies (redemption.vc_backed) and any other startup (redemption.public). For vendors whose startup offers only go through investor networks (flow network_only): the statement, the work-email check URL and public deals in the same category. Each public offer has about: who_qualifies, customers (new / existing), limits and stacking quoted verbatim from the terms, and the full terms, only where the data says.

NameTypeReqDescription
name_or_domainstringyesVendor name, domain or profile URL.

No output schema declared.

No examples provided.

get_pack ~148

One startup pack in full: each pick with category, Proven Score, band, portfolio usage, its deal (claim_url for public deals), where it is available and the reason it was picked, plus claim_all_url to claim every public deal with one sign-in. With country, a pick not available there is replaced by the next vendor in its category that is (or left out if none is).

NameTypeReqDescription
countrystring–Optional: where the company is registered, as a country name or ISO code. Swaps out picks not available there.
slugstringyesPack slug (e.g. early-stage-startup-pack), title, or pack URL. get_packs lists them.

No output schema declared.

No examples provided.

get_packs ~70

Startup packs: the tools a startup needs at a stage (early-stage, AI, fundraising, first hires, compliance, go-to-market, seed to Series A ops), each with its vendors, audience, number of public deals and total deal value. Picks are chosen by data from the Proven Trust Index.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_vendor ~137

A vendor's full public record: Proven Score with every input, best-for facts, offers, alternatives, FAQs and, where known, portfolio_usage (how many portfolio companies in investor networks on Proven use it, with as_of; anonymised counts) search_demand (founder searches for it on Proven and the number of investor networks they came from, with the period) and eligibility (where a company must be registered to use it, company requirements, who it is not available for, with source_url on the vendor's own website).

NameTypeReqDescription
name_or_domainstringyesVendor name, domain (ramp.com) or profile URL.

No output schema declared.

No examples provided.

what_startups_use ~157

Which vendors startups actually use for a job, counted from software stacks shared on Proven by portfolio companies in investor networks (the result gives how many companies shared one). Use it when someone building a product asks which provider to pick (auth, database, email API, payments, error monitoring, CRM...). Returns vendors ranked by companies_using, with Proven Score and deal. Only vendors listed on Proven; companies are never named.

NameTypeReqDescription
categorystring–Optional group name, e.g. "Databases", "CRM".
limitinteger–Default 8.
needstring–The job in plain words, e.g. "transactional email API", "auth for a Next.js app", "Postgres hosting".

No output schema declared.

No examples provided.

Install

How do I install the Trusted Vendors MCP server?

Trusted Vendors is a hosted endpoint at https://index.getproven.com/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 · index.getproven.com

# add to Claude Code
claude mcp add --transport http com-getproven-trust-index 'https://index.getproven.com/mcp'
Common questions

What is the Trusted Vendors MCP server?

Trusted Vendors is an MCP server listed in the public MCP registry as com.getproven/trust-index. Startup software vendors ranked by Proven Score, with public deals. Read-only, no sign-in. This page covers its hosted endpoint (https://index.getproven.com/mcp).

Is the Trusted Vendors MCP server safe to use?

Trusted Vendors scores 78 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 Trusted Vendors MCP server expose?

Trusted Vendors exposes 8 tools: find_vendors, what_startups_use, get_vendor, compare_vendors, get_offers, and 3 more. Their descriptions and schemas cost roughly 1,087 tokens of context every time the server is loaded.

Does the Trusted Vendors MCP server require authentication?

No. We connected to Trusted Vendors without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Trusted Vendors MCP server still maintained?

Trusted Vendors is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Trusted Vendors MCP server?

VerifyMCP ran 13 checks on Trusted Vendors, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.