Skip to main content
Glama
aygp-dr

liquidus-005

by aygp-dr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local
README.md
# liquidus-005 — MCP server

[![spec](https://img.shields.io/badge/spec-v1.15-blue)](https://github.com/aygp-dr/liquidus)
[![python](https://img.shields.io/badge/python-%E2%89%A5%203.11-3776AB?logo=python)](https://www.python.org/)
[![mcp](https://img.shields.io/badge/protocol-MCP%202024--11--05-6E4C9F)](https://modelcontextprotocol.io/)
[![f5](https://img.shields.io/badge/F5%20provenance-wrapped-brightgreen)](https://github.com/aygp-dr/liquidus)
[![role](https://img.shields.io/badge/role-reference%20implementation-purple)](https://github.com/aygp-dr/liquidus)

Consumes: [aygp-dr/liquidus](https://github.com/aygp-dr/liquidus) tag `v1.3`.

Language: Python (mcp SDK).

## What lives here

- `src/liquidus_mcp/provenance.py` — F5 governance-tuple wrapping.
- `src/liquidus_mcp/sdk.py` — httpx client (v1.2 bearer-tri-state, v1.3 hand-authored-SDK).
- `src/liquidus_mcp/server.py` — MCP stdio server, 4 tools + wrapping.
- `tests/test_provenance.py` — F5 shape assertions (unit level).
- `FEEDBACK.md` — clarity report against v1.3.

## Quick start

```
gmake install
gmake test           # F5 shape unit tests
gmake run            # server on stdio — use from an MCP client
```

## Load-bearing finding

Wrap is NOT idempotent — nested wrapping is intentional (composable provenance). Spec v1.4 should say so explicitly. See `FEEDBACK.md` §1.1.
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct resource (order, product, products, taxonomies) with no overlap. The operations are clearly differentiated: single retrieval vs. listing.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern: get_ for single entities and list_ for collections. The naming is predictable and uniform.

Tool Count3/5

With 4 tools, the server is minimally scoped. While it could be sufficient for a read-only browsing service, it feels thin for a typical e-commerce server and may leave agents wanting more functionality.

Completeness2/5

The server covers only retrieval operations for products, orders, and taxonomies. Missing common actions like listing orders, creating or updating products, or managing carts, which are significant gaps for a storefront API.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources