OSA Procurement Guard
REMOTE · PKCTQXEYDFUIUPADAOOV.SUPABASE.CO · SCANNED SEP 20
Pre-purchase trust, pricing and budget decisions for AI agents buying APIs and MCP tools.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability51
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 203 tokens (~203/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 38% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the OSA Procurement Guard MCP server?
OSA Procurement Guard is a hosted endpoint at https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · pkctqxeydfuiupadaoov.supabase.co
claude mcp add --transport http omarfff-osa-procurement-guard 'https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp'
{
"mcpServers": {
"omarfff-osa-procurement-guard": {
"url": "https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp"
}
}
} {
"servers": {
"omarfff-osa-procurement-guard": {
"type": "http",
"url": "https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp"
}
}
} [mcp_servers.omarfff-osa-procurement-guard] url = "https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"omarfff-osa-procurement-guard": {
"type": "remote",
"url": "https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp",
"enabled": true
}
}
} openclaw mcp add omarfff-osa-procurement-guard --url 'https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp' --transport streamable-http
mcp_servers:
omarfff-osa-procurement-guard:
url: "https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp" {
"McpServers": {
"omarfff-osa-procurement-guard": {
"Transport": "http",
"Url": "https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp"
}
}
} assistant mcp add omarfff-osa-procurement-guard -t streamable-http -u 'https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp'
{
"mcpServers": {
"omarfff-osa-procurement-guard": {
"type": "http",
"url": "https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 7c35296a896c0a6f13f8495266045d45 |
| SANs: supabase.co, *.supabase.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pkctqxeydfuiupadaoov.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| supabase.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp | Verified | 200 | |
| http (plaintext) | http://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp | HTTPS enforced | 301 | https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp |
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 →
procurement_decision ~158
Use OSA before buying an API or MCP tool. Returns ALLOW, HOLD or DENY using budget policy, endpoint-scoped trust evidence, price history and optional cheaper equivalents. Get an OSA API key at https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-site.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | – |
| capability | string | – | Explicit capability; required to search equivalent alternatives |
| endpoint | string | – | Paid API or tool endpoint URL |
| max_price_usd | number | – | – |
| min_trust | number | – | – |
| name | string | – | Optional OSA registry name |
| network | string | – | – |
| offered_price_usd | number | – | – |
No output schema declared.
No examples provided.
What is the OSA Procurement Guard MCP server?
OSA Procurement Guard is an MCP server listed in the public MCP registry as io.github.omarfff/osa-procurement-guard. Pre-purchase trust, pricing and budget decisions for AI agents buying APIs and MCP tools. This page covers its hosted endpoint (https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp).
Is the OSA Procurement Guard MCP server safe to use?
OSA Procurement Guard scores 72 out of 100 on VerifyMCP. 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 OSA Procurement Guard MCP server expose?
OSA Procurement Guard exposes 1 tool: procurement_decision. Their descriptions and schemas cost roughly 158 tokens of context every time the server is loaded.
Does the OSA Procurement Guard MCP server require authentication?
No. We connected to OSA Procurement Guard without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the OSA Procurement Guard MCP server still maintained?
OSA Procurement Guard is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.