Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AgentFeed

REMOTE · X402.OCHINIMUS.APP

Crypto briefs and data, Solana pre-trade checks, sanctions, papers, NLP. 102 tools, USDC, 20 chains.

0 this week 85 Trust /100

Last scanned (7 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 14797 tokens (~145/item across 102 items; 102 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management88
  • Stability check failed: schema churn in the 30 days we've observed: 7 tool removals, 0 breaking changes, 0 auth/transport breaks, 50 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 102 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 103 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 85 to 88.

  • 4 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 88 to 85.

  • 1 Nov 26 0
    • Schema quality: 13171 → 14797 ▼ functional
    • New tool “get_company_check” functional
    • New tool “get_pkg_check” functional
    • New tool “get_rwa_yields” functional
    • New tool “get_tx_precheck” functional
    • New tool “get_cascade_backtest” functional
    • New tool “get_claim_check” functional
    • New tool “get_site_signals” functional
    • New tool “get_x402_lint” functional
    • New tool “get_x402_test” functional
  • 30 Oct 26 0
    • “get_hl_whales” changed the type of “top”: number → integer ▼ functional
    • “get_insider_trades” changed the type of “days”: number → integer ▼ functional
    • “get_papers” changed the type of “limit”: number → integer ▼ functional
    • “get_papers” changed the type of “year_from”: number → integer ▼ functional
    • “get_sec_8k” changed the type of “hours”: number → integer ▼ functional
    • “get_sec_filings” changed the type of “limit”: number → integer ▼ functional
    • “get_signal_board” changed the type of “n”: number → integer ▼ functional
    • “get_sol_token_flow” changed the type of “swaps”: number → integer ▼ functional
    • Server version: 2.9.0 → 2.10.0 functional
    • New tool “get_anomaly_flag” functional
    • New tool “get_morning_brief” functional
    • New tool “get_move_alert” functional
  • 25 Oct 26 0
    • Tool “get_jito_tips” rewrote its description, which is the text the model reads security
  • 22 Oct 26 0
    • Tool “get_cascade_forecast” rewrote its description, which is the text the model reads security
    • Tool “get_cascade_scan” rewrote its description, which is the text the model reads security
  • 19 Oct 26 0
    • Tool “get_cascade_forecast” rewrote its description, which is the text the model reads security
    • Tool “get_injection_check” rewrote its description, which is the text the model reads security
    • Tool “get_liq_feed” rewrote its description, which is the text the model reads security
    • Tool “get_liq_heatmap” rewrote its description, which is the text the model reads security
    • Tool “get_paper” rewrote its description, which is the text the model reads security
    • “get_paper” reworded the description of “doi” cosmetic
  • 16 Oct 26 0
    • Server version: 2.8.0 → 2.9.0 functional
Diagnostics

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 5 Nov 2026 · Probed https://x402.ochinimus.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ochinimus.app CN=WE1,O=Google Trust Services,C=US 11 Oct 2026 9 Jan 2027 ECDSA 256 ECDSA-SHA256 26d56231f28590b90ec422b2eebc8792
SANs: ochinimus.app, *.ochinimus.app
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 x402.ochinimus.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
ochinimus.app. No DS 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
Header Value
strict-transport-security max-age=15552000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://x402.ochinimus.app/mcp Verified 200
http (plaintext) http://x402.ochinimus.app/mcp HTTPS enforced 308 https://x402.ochinimus.app/mcp
MCP tools · 102 exposed · ~14,524 tokens

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 →

Tool Tokens
get_x402_test ~160

Use when an agent needs proof that an x402 endpoint takes a real payment. Returns PASS, FAIL or INCONCLUSIVE with the receipt after paying it once from our own wallet, up to $0.05, in Base or Solana USDC. A 503 or 404 is not charged. Costs 1 USDC per call (x402, USDC on Solana, Base, Polygon, Arbitrum or Arc).

NameTypeReqDescription
methodstring–HTTP method to pay with, default GET (a POST is sent with an empty body)
urlstringyesthe x402 endpoint to pay once, URL-encoded: https only, a public host, port 443; the paid request goes to exactly this URL
NameTypeReqDescription
dataobjectyesthe get_x402_test payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_x402_test
toolstringyesthe tool that produced this payload

No examples provided.

pricing ~34

Use when an agent needs the price list before calling anything. Returns every agentfeed tool with its USDC price and description. Free.

Input schema present but exposes no named parameters.

NameTypeReqDescription
dataobjectyestools: the full price list
toolstringyesthe tool that produced this payload

No examples provided.

Install

How do I install the AgentFeed MCP server?

AgentFeed is a hosted endpoint at https://x402.ochinimus.app/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 · x402.ochinimus.app

# add to Claude Code
claude mcp add --transport http seekdaseek-agentfeed 'https://x402.ochinimus.app/mcp'
Common questions

What is the AgentFeed MCP server?

AgentFeed is an MCP server listed in the public MCP registry as io.github.seekdaseek/agentfeed. Crypto briefs and data, Solana pre-trade checks, sanctions, papers, NLP. 102 tools, USDC, 20 chains. This page covers its hosted endpoint (https://x402.ochinimus.app/mcp).

Is the AgentFeed MCP server safe to use?

AgentFeed scores 85 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 AgentFeed MCP server expose?

AgentFeed exposes 102 tools: get_liq_pulse, get_perp, get_funding_pulse, get_liquidation_leaders, get_cascade_scan, and 97 more. Their descriptions and schemas cost roughly 14,524 tokens of context every time the server is loaded.

Does the AgentFeed MCP server require authentication?

No. We connected to AgentFeed without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AgentFeed MCP server still maintained?

AgentFeed is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the AgentFeed MCP server?

VerifyMCP ran 13 checks on AgentFeed, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.