amu-pgvector
PYPI · AMU-PGVECTOR · SCANNED OCT 4
Lineage-gated agent memory tools on Postgres + pgvector, enforced by row-level security.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 6 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to sangaraju1988/amu-pgvector). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability56
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 386 tokens (~128/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the amu-pgvector MCP server?
amu-pgvector runs locally as a PyPI package, launched with uvx amu-pgvector. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · amu-pgvector
claude mcp add sangaraju1988-amu-pgvector -- uvx amu-pgvector
{
"mcpServers": {
"sangaraju1988-amu-pgvector": {
"command": "uvx",
"args": [
"amu-pgvector"
]
}
}
} {
"servers": {
"sangaraju1988-amu-pgvector": {
"command": "uvx",
"args": [
"amu-pgvector"
]
}
}
} codex mcp add sangaraju1988-amu-pgvector -- uvx amu-pgvector
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sangaraju1988-amu-pgvector": {
"type": "local",
"command": [
"uvx",
"amu-pgvector"
],
"enabled": true
}
}
} openclaw mcp add sangaraju1988-amu-pgvector --command uvx --arg amu-pgvector
mcp_servers:
sangaraju1988-amu-pgvector:
command: "uvx"
args: ["amu-pgvector"] {
"McpServers": {
"sangaraju1988-amu-pgvector": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"amu-pgvector"
]
}
}
} assistant mcp add sangaraju1988-amu-pgvector -t stdio -c uvx -a amu-pgvector
{
"mcpServers": {
"sangaraju1988-amu-pgvector": {
"command": "uvx",
"args": [
"amu-pgvector"
]
}
}
} 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.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.07 ▲ functional
- Package version: 0.1.2 → 0.1.3 functional
- 28 Sept 26 75
First indexed and scored.
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 4 Oct 2026 · Analysed pypi/amu-pgvector@0.1.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | sangaraju1988/amu-pgvector |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sangaraju1988/amu-pgvector/.github/workflows/publish.yml@refs/tags/v0.1.3 |
| Rekor log index | 2987430995 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:5ee56cb13ee21ef444866ea1eccaeb5ea088ef4f029b54fa12e537f8712f14e0 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 6 packages
| Packages resolved | 6 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
amu_check_conflict ~84
Check whether another department has already recorded a conflicting definition of the same metric_name (same name, different derivation / definition_hash). Returns only department names and hashes -- never values or lineage -- so this cannot become a side channel around the gate.
| Name | Type | Req | Description |
|---|---|---|---|
| definition_hash | string | yes | – |
| metric_name | string | yes | – |
| owner_department | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
amu_record ~100
Record a new Analytical Memory Unit (AMU). Lineage is extracted from the executed `sql` (ground truth), never self-reported. Requires an amu_writer-member Postgres role -- other roles get a Postgres permission error, not a silent no-op.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| metric_name | string | yes | – |
| owner_department | string | yes | – |
| sql | string | yes | – |
| value | object | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
amu_search ~105
Search lineage-gated Analytical Memory Units (AMUs) by semantic similarity to a natural-language query. Results are lineage-gated by Postgres row-level security under this server's own Postgres role: an Analytical Memory Unit (AMU) is only ever returned if every sensitive column touched by its derivation is in this role's permitted set. This tool cannot bypass that gate.
| Name | Type | Req | Description |
|---|---|---|---|
| k | integer | – | – |
| metric_name | – | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
What is the amu-pgvector MCP server?
amu-pgvector is an MCP server listed in the public MCP registry as io.github.sangaraju1988/amu-pgvector. Lineage-gated agent memory tools on Postgres + pgvector, enforced by row-level security. This page covers its PyPI package (amu-pgvector).
Is the amu-pgvector MCP server safe to use?
amu-pgvector scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 2026. Its build provenance is signed and verified. 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 amu-pgvector MCP server expose?
amu-pgvector exposes 3 tools: amu_search, amu_record, amu_check_conflict. Their descriptions and schemas cost roughly 289 tokens of context every time the server is loaded.
Is the amu-pgvector MCP server still maintained?
amu-pgvector is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the amu-pgvector MCP server under?
amu-pgvector declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.