io.github.CSOAI-ORG/meok-ap2-mandate-mcp
REMOTE · API.MEOK.AI · 2 COMPONENTS
MEOK Google AP2 Mandate MCP — issue + verify + revoke signed user-side spend authorisations for
Available components
Last scanned (57 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row.
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Remote endpoint https://api.meok.ai/v1/a2a/ap2-mandate is not live: api.meok.ai has no public DNS answer (checked via 1.1.1.1, 2026-09-29). Deprecated by the publisher until a live endpoint exists. The PyPI package meok-ap2-mandate-mcp still installs and runs locally over stdio.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 26 Aug 26 −4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 20 Aug 26 4
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 26 Aug 2026 · Probed https://api.meok.ai/v1/a2a/ap2-mandate
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of api.meok.ai. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| api.meok.ai. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.meok.ai/v1/a2a/ap2-mandate | Unreachable | ||
| http (plaintext) | http://api.meok.ai/v1/a2a/ap2-mandate | HTTPS enforced |
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 →
No tool schema has been captured from this endpoint yet.
How do I install the io.github.CSOAI-ORG/meok-ap2-mandate-mcp server?
io.github.CSOAI-ORG/meok-ap2-mandate-mcp is a hosted endpoint at https://api.meok.ai/v1/a2a/ap2-mandate, 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 · api.meok.ai
claude mcp add --transport http csoai-org-meok-ap2-mandate-mcp 'https://api.meok.ai/v1/a2a/ap2-mandate'
What is the io.github.CSOAI-ORG/meok-ap2-mandate-mcp server?
io.github.CSOAI-ORG/meok-ap2-mandate-mcp is listed in the public MCP registry as io.github.CSOAI-ORG/meok-ap2-mandate-mcp. MEOK Google AP2 Mandate MCP, issue + verify + revoke signed user-side spend authorisations for. This page covers its hosted endpoint (https://api.meok.ai/v1/a2a/ap2-mandate).
Is the io.github.CSOAI-ORG/meok-ap2-mandate-mcp server safe to use?
io.github.CSOAI-ORG/meok-ap2-mandate-mcp scores 0 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.
Does the io.github.CSOAI-ORG/meok-ap2-mandate-mcp server require authentication?
Its publisher declares no required credentials for io.github.CSOAI-ORG/meok-ap2-mandate-mcp. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.CSOAI-ORG/meok-ap2-mandate-mcp server still maintained?
io.github.CSOAI-ORG/meok-ap2-mandate-mcp is marked deprecated in the MCP registry. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.