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
553 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Japan regulatory, sanctions & DEX market data for AI agents via x402 (USDC on Base).
Website
https://api.agentfeeds.jp/v1/catalog
Listing
From the official MCP registry (active).
Recent checks of agentfeeds.jp
CheckedResultHandshake
1 hour agoHandshake completed553 ms
2 days agoHandshake completed567 ms
4 days agoHandshake completed557 ms
5 days agoHandshake completed561 ms
7 days agoHandshake completed669 ms
8 days agoHandshake completed587 ms
9 days agoHandshake completed632 ms
12 days agoHandshake completed574 ms
13 days agoHandshake completed579 ms
15 days agoHandshake completed600 ms
17 days agoHandshake completed552 ms
18 days agoHandshake completed518 ms
19 days agoHandshake completed541 ms
20 days agoHandshake completed581 ms
21 days agoHandshake completed562 ms
21 days agoHandshake completed587 ms
23 days agoHandshake completed532 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.