agentfeeds.jp MCP server
jp.agentfeeds.api/agentfeedsapi.agentfeeds.jpstreamable-httpv1.0.0Scanned
Japan regulatory, sanctions & DEX market data for AI agents via x402 (USDC on Base).
6 tools: 5 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the agentfeeds.jp MCP server can do
The agentfeeds.jp MCP server is published by api.agentfeeds.jp, a domain the MCP Registry verified. It has 6 tools. It can create or change data (5 tools: catalog, reg_events, dex_spread_summary, dex_spread_anomalies and 1 more), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 5Claude Code: ask
catalogFree: machine-readable product catalog of agentfeeds.jp (Japan regulatory & market data for AI agents).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Free: machine-readable product catalog of agentfeeds.jp (Japan regulatory & market data for AI agents). Factual data only; not investment advice.
dex_spread_anomaliesPaid ($0.005/call): DEX spread anomaly events (1-min |spread| above trailing 30-day p99).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Paid ($0.005/call): DEX spread anomaly events (1-min |spread| above trailing 30-day p99). Descriptive statistics only; not investment advice.
dex_spread_summaryPaid ($0.002/call): 1-minute cross-venue DEX spread statistics (WETH/USDC on Base, SOL/USDC via Jupiter).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
reg_eventsPaid ($0.01/call): Japan digital & financial regulatory events (crypto, AML/sanctions, tax, AI) in English, human-reviewed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
sanctions_checkPaid ($0.002/call): screen a crypto address against Japan MOF asset-freeze sanctions designations.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Paid ($0.002/call): screen a crypto address against Japan MOF asset-freeze sanctions designations. Factual screening data; not legal advice.
Only reads 1Show 1 read-only tool
get_termsFree: license terms and disclaimer for agentfeeds.jp data.No findings
Why it is in this group
- The name "get_terms" says "get": a word for reading.
Description, as the server wrote it Free: license terms and disclaimer for agentfeeds.jp data.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:15 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.agentfeeds.jp/mcp: tools/list returned 6 tools to an anonymous client, including catalog (write), reg_events (write), dex_spread_summary (write), dex_spread_anomalies (write), sanctions_check (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http agentfeeds https://api.agentfeeds.jp/mcpclaude mcp add --transport http agentfeeds https://api.agentfeeds.jp/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__agentfeeds__get_terms"
],
"ask": [
"mcp__agentfeeds__catalog",
"mcp__agentfeeds__reg_events",
"mcp__agentfeeds__dex_spread_summary",
"mcp__agentfeeds__dex_spread_anomalies",
"mcp__agentfeeds__sanctions_check"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agentfeeds. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/jp.agentfeeds.api/agentfeeds/verify?hash=dab5c9cdacf0dbd917151d1e19a1dda8bb50039b3390eb7845d2e09c7d5d21e9" | jq -e '.changed == false'Pinned hash dab5c9cdacf0, from Nov 18, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/jp.agentfeeds.api/agentfeeds/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/jp.agentfeeds.api/agentfeeds)Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.
agentfeeds.jp MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the agentfeeds.jp MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the agentfeeds.jp MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the agentfeeds.jp MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the agentfeeds.jp MCP server have?
- 6 tools: 5 write, 1 read. catalog, reg_events, dex_spread_summary, dex_spread_anomalies, sanctions_check and get_terms.
Does the agentfeeds.jp MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the agentfeeds.jp MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the agentfeeds.jp MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.