About this category
MCP Servers & Connectors on Attesar
New listings are reviewed and published daily. Model Context Protocol servers that connect an assistant to a tool, a database or an internal API. Every seller here is identity-verified, every listing is reviewed before publication, and your payment is protected until you confirm delivery.
Read the scopes before you connect it
An MCP server decides what an assistant can see and do. Listings state the permissions requested and whether the server performs writes. A reporting connector that asks for write access to your database is asking for more than it needs, and that is worth a question before purchase.
Source, manifest and transport
You should receive the server source, its manifest and a clear statement of the transport it uses — stdio for a local process, HTTP or SSE for a hosted one. A hosted endpoint on its own is not delivery, because you cannot audit what you cannot read.
Test it against a copy, not production
Point the server at a staging database or a scratch account first and watch what it actually calls. Confirm delivery once you have seen the tool list and the traffic match the description.