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.

ERP Partner Finder

REMOTE · ERPPARTNERFINDER.COM

Search, compare and shortlist Odoo partners in Germany, Austria and Switzerland.

+2 this week 78 Trust /100

Last scanned (14 hours ago)

Scores higher than 73% of remote servers

Reachable. Last reached 6 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 Security63
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 585 tokens (~117/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage78
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 33% 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 5 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 current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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.

  • 6 Nov 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
  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

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

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

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

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

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 6 Nov 2026 · Probed https://erppartnerfinder.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.erppartnerfinder.com CN=YR1,O=Let's Encrypt,C=US 4 Oct 2026 2 Jan 2027 RSA 2048 SHA256-RSA 6a1b32fd0a7bb2ee36b0e042df7ac6e5d57
SANs: *.erppartnerfinder.com, erppartnerfinder.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
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 erppartnerfinder.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
erppartnerfinder.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=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://erppartnerfinder.com/api/mcp Verified 200
http (plaintext) http://erppartnerfinder.com/api/mcp HTTPS enforced 308 https://erppartnerfinder.com/api/mcp
MCP tools · 5 exposed · ~585 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
directory_stats ~39

Aggregate figures: partners per country and tier, medians per tier, pricing transparency, AI-assisted delivery, cities and app specialisms with the most partners.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_partner ~70

Full profile of one partner: odoo.com figures (tier, references by industry, certified experts, project sizes, retention) and facts from the partner's own website (services, specialisms, prices, AI-assisted delivery, hosting, languages).

NameTypeReqDescription
slugstringyesPartner slug from search_partners

No output schema declared.

No examples provided.

match_partners ~130

Rule-based shortlist (up to 5) for a buyer's project, with the reasons for each match — the same published matching rules as the questionnaire on erppartnerfinder.com. Read-only: nothing is sent to any partner. To let the buyer contact partners, call prepare_request.

NameTypeReqDescription
ai_assisted_deliverystring––
appsarray––
countrystringyes–
employeesstringyes–
industrystringyes–
languagesarray––
situationstringyes–
usersstringyesPlanned Odoo users

No output schema declared.

No examples provided.

prepare_request ~208

Saves the buyer's project answers (no personal data) and returns a link to erppartnerfinder.com where the buyer reviews the answers, adds their own contact details, confirms their email and chooses which partners receive the request. Nothing is sent to partners and no email is sent by this tool. Give the link to the buyer; it is valid for 30 days. Optionally name one partner the buyer asked about (it is then always shown and preselected).

NameTypeReqDescription
ai_assisted_deliverystring––
appsarray––
countrystringyes–
employeesstringyes–
industrystringyes–
languagestring–Language of the page the buyer will see
languagesarray––
partner_slugstring–A partner the buyer specifically wants to contact (slug from search_partners)
situationstringyes–
timelinestring––
usersstringyesPlanned Odoo users

No output schema declared.

No examples provided.

search_partners ~138

Search the Odoo implementation partners in Germany, Austria and Switzerland, ranked by a published formula (tier, references, certified experts, retention). Filter by country, city, tier, app specialism or industry focus.

NameTypeReqDescription
appstring–Odoo app the partner highlights as a specialism
citystring–City name, e.g. München, Munich, Wien, Zürich
countrystring––
industrystring–Industry the partner states as a focus
limitinteger––
querystring–Text in the partner name or summary
tierstring––

No output schema declared.

No examples provided.

Install

How do I install the ERP Partner Finder MCP server?

ERP Partner Finder is a hosted endpoint at https://erppartnerfinder.com/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 · erppartnerfinder.com

# add to Claude Code
claude mcp add --transport http com-erppartnerfinder-partner-finder 'https://erppartnerfinder.com/api/mcp'
Common questions

What is the ERP Partner Finder MCP server?

ERP Partner Finder is an MCP server listed in the public MCP registry as com.erppartnerfinder/partner-finder. Search, compare and shortlist Odoo partners in Germany, Austria and Switzerland. This page covers its hosted endpoint (https://erppartnerfinder.com/api/mcp).

Is the ERP Partner Finder MCP server safe to use?

ERP Partner Finder 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 ERP Partner Finder MCP server expose?

ERP Partner Finder exposes 5 tools: search_partners, get_partner, match_partners, prepare_request, directory_stats. Their descriptions and schemas cost roughly 585 tokens of context every time the server is loaded.

Does the ERP Partner Finder MCP server require authentication?

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

Is the ERP Partner Finder MCP server still maintained?

ERP Partner Finder is still listed as active in the MCP registry. We last reached this channel on 6 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 ERP Partner Finder MCP server?

VerifyMCP ran 12 checks on ERP Partner Finder, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about ERP Partner Finder: Authorization. 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.