Remote MCP · Endpoint
agentfeeds.jp MCP server
No. agentfeeds.jp answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.agentfeeds.jp/mcp
The last check completed an MCP handshake.
- Registry name
- jp.agentfeeds.api/agentfeeds
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 604 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Japan regulatory, sanctions & DEX market data for AI agents via x402 (USDC on Base).
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 604 ms |
| 1 day ago | Handshake completed | 554 ms |
| 2 days ago | Handshake completed | 543 ms |
| 3 days ago | Handshake completed | 563 ms |
| 4 days ago | Handshake completed | 581 ms |
| 5 days ago | Handshake completed | 579 ms |
| 6 days ago | Handshake completed | 579 ms |
| 8 days ago | Handshake completed | 595 ms |
| 11 days ago | Handshake completed | 565 ms |
| 13 days ago | Handshake completed | 645 ms |
| 16 days ago | Handshake completed | 539 ms |
| 18 days ago | Handshake completed | 596 ms |
| 20 days ago | Handshake completed | 553 ms |
| 22 days ago | Handshake completed | 567 ms |
| 24 days ago | Handshake completed | 557 ms |
| 26 days ago | Handshake completed | 561 ms |
| 27 days ago | Handshake completed | 669 ms |
| 29 days ago | Handshake completed | 587 ms |
| 30 days ago | Handshake completed | 632 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with agentfeeds.jp and makes no claim about it beyond what these checks measured.