CodeNate-こうでねーと-
https://mcp.yomitasu.jp/s/codenate-jp/mcp
● healthy
CodeNate(こうでねーと)は、プロのコーディネーターがデザイン料0円でお部屋のインテリアを提案するサービスです。（codenate.jp の内容を検索して答える。ヨミタス経由）
Transport
streamable-http
Auth
—
Cost
—
Protocol revision
2025-11-25
negotiated, not declared
MCP readiness
B · 86/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 B, 83.6/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 | 25/25 | Endpoint answers the MCP initialize handshake (854 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 | 21/21 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 6 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 | 2/5 | seen within 30 days. |
| Auth declaration | 0/5 | How to authenticate is not stated. |
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive
(854 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 80% of peers
- This listing 86 · peer median 81
- Latency
- Faster than 26% of peers
- This listing 542 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Auth declaration −5
— State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.
- Verified identity −3
— Claim the listing and prove control of its domain.
Now: Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
- Freshness + modern flags −3
— Keep the listing current in the registry or source it comes from.
Now: seen within 30 days.
Listed in
Directories this entry was found in.
mcp-registry since 2026-10-23
capkey since 2026-10-26
↗
How to connect
MCP endpoint (streamable-http)
https://mcp.yomitasu.jp/s/codenate-jp/mcpJSON-RPC initialize probe
curl -X POST https://mcp.yomitasu.jp/s/codenate-jp/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'