ToolsMCP
Devart MCP Server for PostgreSQL (ADO.NET)
Listed in the official MCP Registry with an installable nuget package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- devart.com
- Prerequisites
- Install Devart.Mcp.PostgreSql from nuget (stdio transport). Declares 3 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 1.1.0 · updated
- Official links
Publisher’s description
Schema-aware read/write access to PostgreSQL through Devart dotConnect ADO.NET data provider.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.1.0, registry status active. 1 package (nuget)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- devart.com
- Version observed
- 1.1.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/com.devart%2Fmcp-postgresql/versions/1.1.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Query a database in plain language | Publisher description mentions “postgresql”, “schema”. | No connection check or task run. Capability is as described by the publisher. | Rule database-query matched: “postgresql”, “schema”. Rule database-query. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
Devart.Mcp.PostgreSql(nuget, stdio, 3 secret inputs)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
com.devart/mcp-postgresql
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.