agentfeeds.jp
REMOTE · API.AGENTFEEDS.JP
Japan regulatory, sanctions & DEX market data for AI agents via x402 (USDC on Base).
Available components
Last scanned (18 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 317 tokens (~52/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://api.agentfeeds.jp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentfeeds.jp | CN=WE1,O=Google Trust Services,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ec2b98ae3221da420e6c430002ba9070 |
| SANs: agentfeeds.jp, *.agentfeeds.jp | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.agentfeeds.jp. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| jp. | present | 33631 | 8 | Verified |
| agentfeeds.jp. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.agentfeeds.jp/mcp | Verified | 200 | |
| http (plaintext) | http://api.agentfeeds.jp/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
catalog ~36
Free: machine-readable product catalog of agentfeeds.jp (Japan regulatory & market data for AI agents). Factual data only; not investment advice.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dex_spread_anomalies ~69
Paid ($0.005/call): DEX spread anomaly events (1-min |spread| above trailing 30-day p99). Descriptive statistics only; not investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| pair | string | – | – |
| since | string | – | – |
No output schema declared.
No examples provided.
dex_spread_summary ~74
Paid ($0.002/call): 1-minute cross-venue DEX spread statistics (WETH/USDC on Base, SOL/USDC via Jupiter). Descriptive statistics only; not investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| pair | string | – | – |
| since | string | – | – |
No output schema declared.
No examples provided.
get_terms ~20
Free: license terms and disclaimer for agentfeeds.jp data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reg_events ~71
Paid ($0.01/call): Japan digital & financial regulatory events (crypto, AML/sanctions, tax, AI) in English, human-reviewed. Factual data; not investment or legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| since | string | – | – |
No output schema declared.
No examples provided.
sanctions_check ~47
Paid ($0.002/call): screen a crypto address against Japan MOF asset-freeze sanctions designations. Factual screening data; not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
How do I install the agentfeeds.jp MCP server?
agentfeeds.jp is a hosted endpoint at https://api.agentfeeds.jp/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.agentfeeds.jp
claude mcp add --transport http jp-agentfeeds-api-agentfeeds 'https://api.agentfeeds.jp/mcp'
What is the agentfeeds.jp MCP server?
agentfeeds.jp is an MCP server listed in the public MCP registry as jp.agentfeeds.api/agentfeeds. Japan regulatory, sanctions & DEX market data for AI agents via x402 (USDC on Base). This page covers its hosted endpoint (https://api.agentfeeds.jp/mcp).
Is the agentfeeds.jp MCP server safe to use?
agentfeeds.jp scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the agentfeeds.jp MCP server expose?
agentfeeds.jp exposes 6 tools: catalog, get_terms, reg_events, dex_spread_summary, dex_spread_anomalies, sanctions_check. Their descriptions and schemas cost roughly 317 tokens of context every time the server is loaded.
Does the agentfeeds.jp MCP server require authentication?
No. We connected to agentfeeds.jp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the agentfeeds.jp MCP server still maintained?
agentfeeds.jp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.