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.

CompanyProof

REMOTE · COMPANYPROOF.AI

Find legal companies, retrieve registry profiles and verify company facts with source evidence.

Available components

+4 this week 86 Trust /100

Last scanned (7 hours ago)

Scores higher than 93% of remote servers

Reachable. Last reached 5 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 Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 185 tokens (~61/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
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.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 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 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.

  • 24 Oct 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.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 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 5 Nov 2026 · Probed https://companyproof.ai/v2/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=companyproof.ai CN=WE1,O=Google Trust Services,C=US 21 Oct 2026 19 Jan 2027 ECDSA 256 ECDSA-SHA256 4e56b32c6d08b07e0eca68c0cac3a601
SANs: companyproof.ai
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 companyproof.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
companyproof.ai. 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
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(self), geolocation=(), browsing-topics=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://companyproof.ai/v2/mcp Verified 200
http (plaintext) http://companyproof.ai/v2/mcp HTTPS enforced 302 https://companyproof.ai/v2/mcp
MCP tools · 3 exposed · ~185 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
get_company_profile ~73

Retrieve a CompanyProof company profile and enrichment payload by the opaque company ID returned from search_companies. This read-only operation requires an active CompanyProof evaluation or paid plan and live account access, and consumes one shared claim credit.

NameTypeReqDescription
company_idstringyesOpaque CompanyProof company ID returned by search_companies.
NameTypeReqDescription
company_idstringyes–
enrichment–yes–
profileobjectyes–
section_statusobjectyes–

No examples provided.

search_companies ~61

Find ranked CompanyProof company matches by name, registration number, VAT/tax identifier or ticker, optionally narrowed by subdivision and city/state. This read-only operation requires an active CompanyProof evaluation or paid plan and live account access, and consumes one shared claim credit.

Input schema present but exposes no named parameters.

NameTypeReqDescription
companiesarrayyes–

No examples provided.

verify_company_claims ~51

Resolve a company, compare supported claims with current company evidence, preserve a proof record, and optionally monitor verified claims for change. This call consumes normal CompanyProof claim credits and writes to the account evidence ledger.

Input schema present but exposes no named parameters.

NameTypeReqDescription
claimsarrayyes–
companyobjectyes–
latency_msnumberyes–
monitoringstringyes–
proof_idstringyes–
summaryobjectyes–

No examples provided.

Install

How do I install the CompanyProof MCP server?

CompanyProof is a hosted endpoint at https://companyproof.ai/v2/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 · companyproof.ai

# add to Claude Code
claude mcp add --transport http ai-companyproof-companyproof 'https://companyproof.ai/v2/mcp'
Common questions

What is the CompanyProof MCP server?

CompanyProof is an MCP server listed in the public MCP registry as ai.companyproof/companyproof. Find legal companies, retrieve registry profiles and verify company facts with source evidence. This page covers its hosted endpoint (https://companyproof.ai/v2/mcp).

Is the CompanyProof MCP server safe to use?

CompanyProof scores 86 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 CompanyProof MCP server expose?

CompanyProof exposes 3 tools: verify_company_claims, search_companies, get_company_profile. Their descriptions and schemas cost roughly 185 tokens of context every time the server is loaded.

Does the CompanyProof MCP server require authentication?

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

Is the CompanyProof MCP server still maintained?

CompanyProof 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.