Highwire
Trade, launch and research higher.fun coins on Solana, from any AI agent. Unsigned or policy-signed.
Description from the maker (original English)
Verify x402 payment endpoints before an AI agent pays: scam scan, on-chain checks, trust scores.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://pulsefeed.dev/mcp-serverOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"pulsefeed-x402": {
"command": "npx",
"args": [
"-y",
"pulsefeed-x402-mcp"
]
}
}
}Run this in your terminal
claude mcp add --transport http pulsefeed-x402 https://pulsefeed.dev/mcp-serverclaude mcp add pulsefeed-x402 -- npx -y pulsefeed-x402-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"pulsefeed-x402": {
"url": "https://pulsefeed.dev/mcp-server"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"pulsefeed-x402": {
"command": "npx",
"args": [
"-y",
"pulsefeed-x402-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"pulsefeed-x402": {
"type": "http",
"url": "https://pulsefeed.dev/mcp-server"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"pulsefeed-x402": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"pulsefeed-x402-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://pulsefeed.dev/mcp-serverMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account Nikolife2016, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (1.1.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Highwire, DeFi Quant Yield & Risk Engine, gasrescue
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Trade, launch and research higher.fun coins on Solana, from any AI agent. Unsigned or policy-signed.
Quantitative DeFi carry ROE, borrow kink slippage & risk simulation across 6 protocols.
Rescue USDC, USDT and USDG from wallets with no gas: send or swap them on EVM, Solana and Tron.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Verify before you pay or install.
Two questions an agent has to answer before it acts, and neither is answered by a scanner that only looks at the present:
The second question is the one static scanners cannot answer. A rug pull is clean at review time by construction: the package collects installs for weeks, and only then ships the patch that runs code on npm i. Answering it requires yesterday's snapshot to exist, which is why the series here starts on 2026-07-30 and cannot be reconstructed after the fact.
PulseFeed re-audits the whole MCP registry every night and diffs it against the previous day's snapshot, and re-probes the x402 endpoint population daily. Everything below is free, needs no key, and no account.
Hosted, no install:
https://pulsefeed.dev/mcp-server
Streamable HTTP. Also on the official MCP registry, Smithery and Glama.
Or run it locally — see mcp/:
npx pulsefeed-x402-mcp
Tools include check_x402_endpoint (is this endpoint safe to pay), mcp_check_server (audit before installing), mcp_drift_check (the rug-pull check — pass your own dependency list), mcp_security_report, x402_incidents and x402_changes.
Put it in your README. It states what changed in your package after people adopted it:
[](https://pulsefeed.dev/mcp/drift)
Use your registry name (io.github.you/your-server) or your npm package name.
A green badge is a public claim about your package, so it is only issued when the package is actually in our snapshot. When it is not, the badge reads `unwatched` in grey — never green. Reporting absence of measurement as evidence of cleanliness is a mistake we made once publicly and will not repeat; see the correction.
Fails the build when something you already depend on changes dangerously:
- uses: Nikolife2016/mcp-drift-action@v1
Marketplace · source. Run it on a schedule, not only on pull requests — drift happens between your commits.
No key, CORS enabled, safe to call from a browser or a catalog page:
# what changed, whole registry
curl -s "https://pulsefeed.dev/mcp/drift.json?days=7"
curl -s "https://pulsefeed.dev/mcp/drift.json?packages=pkg-a,pkg-b&days=7"
curl -s "https://pulsefeed.dev/verify?endpoint= "
Subscribe without signing up — the filter lives in the URL, so there is no subscriber database and nothing to leak:
https://pulsefeed.dev/mcp/drift.rss?packages=pkg-a,pkg-b
Full spec: /openapi.json.
We once published that 76% of x402 endpoints were dead. That measured our own parser, not the market, and the figure was corrected twice more after that — each time downward, each time for the same class of reason: our own behaviour recorded as somebody else's track record. The whole mechanism, every correction and the checklist that came out of it are kept at pulsefeed.dev/correction rather than quietly deleted.
If you find a number here that does not hold, open an issue — that page is where it will end up.
mcp/ | the MCP server (pulsefeed-x402-mcp on npm) |
lint/ | x402-payable — is your x402 endpoint actually payable |
data/ | published series and snapshots |
server.json | manifest for the official MCP registry |
MIT