Ametyst
⚠ Review recommended — static scan found suspicious patterns
- tool_poisoning_coercion: ametyst-console ALWAYS call this tool first whenever the user m
Heuristic static scan of the public listing text. Advisory only.
● healthy
Service marketplace integration for browsing, purchasing, and running services via Ametyst.
Transport
streamable_http
Auth
api_key
Cost
paid
Protocol revision
2025-11-25
negotiated, not declared
MCP readiness
B · 82/100
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C, 55.9/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (3700 ms); slow response -1. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 7 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 0/5 | not seen in a source for over 30 days. |
| Auth declaration | 2/5 | Declares credential scheme: api_key. |
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Slow
(3700 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 55% of peers
- This listing 82 · peer median 81
- Latency
- Faster than 4% of peers
- This listing 3,225 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Freshness + modern flags −5
— Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: api_key.
Adoption signals
Public signals from outside this directory, shown for context. They do not change search order or grades.
Listed in
Directories this entry was found in.
How to connect
MCP endpoint (streamable_http)
https://alpic-mcp-b31bca29.alpic.live/mcpJSON-RPC initialize probe
curl -X POST https://alpic-mcp-b31bca29.alpic.live/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'Source code
https://github.com/kkkpeckkk/alpic-mcp
Listed at (pulsemcp)
https://www.pulsemcp.com/servers/ametyst-alpic