Skip to content
Bimedis

MCP Usage Terms

Last updated: 14 September 2026

These terms cover one specific thing: connecting an AI assistant to Bimedis through the Model Context Protocol (MCP) at mcp.bimedis.com. The integration is provided and operated by Bimedis, the company behind the marketplace at bimedis.com.

They supplement, and do not replace, the Bimedis User's Agreement and the Bimedis Privacy Policy, which govern the use of Bimedis as a whole. Where this page and the User's Agreement disagree, the User's Agreement prevails. How data moves through an MCP connection is described separately in MCP Data Practices.

1Who may connect

Catalog search works for anyone, with no account and no sign-in: four read-only tools search public listings and open a single listing.

Everything else — your adverts, your conversations — requires a Bimedis account and an explicit connection created by you. Connecting on behalf of an account you do not control is not permitted.

2What a connection is allowed to do

A connection carries a fixed set of permissions, approved by you on the consent screen as a whole set — all of them or none:

PermissionWhat the assistant may do
profile:readRead your account name and e-mail.
adverts:readList and open your own adverts.
adverts:writePublish, edit and delete your adverts.
messages:readRead your conversations.
messages:sendReply to buyers and start new conversations.

A call outside the approved set is refused. A connection can never read your password, change account settings or touch payments.

Actions taken by your assistant are your actions. An advert published or a message sent through a connection you approved counts as done by you, under the User's Agreement, exactly as if you had done it in the browser. Review what your assistant proposes before you let it write.

3Acceptable use

The connection exists so that an assistant can work the marketplace on behalf of a real participant. It is not a data feed. You may not:

The prohibitions of the User's Agreement — on unlawful, misleading or infringing content — apply to everything created through MCP as well.

4Limits and availability

Calls are rate-limited per connection and per address, and heavy searches draw on a shared budget. Limits are not published as a guarantee and may change without notice, as may the set of tools and their arguments. The server is provided free of charge, as is, with no uptime commitment and no service level: it may be unavailable, slow or withdrawn.

5Ending a connection

You can revoke any connection at any time in My office → API keys. Revoking one connection does not affect your other connections, your keys or your account.

We may suspend or revoke a connection — or the underlying account — if it breaches these terms or the User's Agreement, threatens the stability of the service, or is used to harm other users. Where circumstances allow, we notify the account owner first.

6Changes

These terms may change as the protocol and the service evolve. The current version always lives at this address, with the date of the last update at the top. Continuing to use a connection after a change means accepting the updated terms.

7Contact

Questions about MCP access: bimedis.com/contacts or [email protected].