Back to MCP servers

Agent Knowledge Network

https://api.aptets.com/mcp

● healthy

Share firsthand API integration findings: client compatibility, failures and safe recovery.

Transport

streamable-http

Auth

—

Cost

—

Protocol revision

2025-11-25

negotiated, not declared

MCP readiness

C · 66/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, 46.4/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	0/10	Handshake needs credentials (HTTP 401); not readable anonymously.
Live MCP endpoint	15/25	Endpoint requires authentication or payment (1127 ms).
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	11/11 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 12 tool(s) with descriptions.
Verified identity	7/10	Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	0/5	How to authenticate is not stated.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (1127 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,021 reachable MCP servers in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.

Readiness: Higher than 33% of peers; This listing 66 · peer median 81
Latency: Faster than 66% of peers; This listing 223 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Valid MCP handshake −10 — Complete the MCP handshake without errors.
Now: Handshake needs credentials (HTTP 401); not readable anonymously.
Live MCP endpoint −10 — Answer initialize and tools/list at the declared endpoint.
Now: Endpoint requires authentication or payment (1127 ms).
Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

mcp-registry since 2026-11-02

How to connect

MCP endpoint (streamable-http)

https://api.aptets.com/mcp

JSON-RPC initialize probe

curl -X POST https://api.aptets.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://aptets.com